Library-wide minimum accessibility standard for all components

[kabaros]

This issue is to add accessibility improvements for the DHIS2 UI library. More details about the components and work involved are available on Jira.

There are tickets for the individual components which should be tackled individually and a separate PR raised for each component.

Important

Please indicate in the discussion here if you're working on improving a component, in order to avoid people picking up the same task.

Components

• Chip
• Menu/MenuItem
• TabBar/Tab
• Tooltip
• Select
• Loader
• Dropdownbutton
• FileInput
• FlyoutMenu
• HeaderBar
• Button
• SplitButton
• Modal
• SegmentedControl
• Icon
• SelectionBar
• SharingDialog
• Switch
• UserAvatar
• Transfer

[pranjalkuhikar]

Hi, can I work on improving accessibility for the Tooltip component?

[kabaros]

@pranjalkuhikar most of these accessiblity enhancements were already done now , including the Tooltip - are you interested in accessibility work specifically, or any work in the UI (or other libraries and projects) - I can help identify other good first issues

[pranjalkuhikar]

Hi @kabaros , thanks for the update! Yes, I’m open to working on other areas too, not just accessibility. I’d really appreciate it if you could suggest some other good first issues in the UI library or related projects. Looking forward to contributing!

[khalilurrrahmanridoykhan]

Hi @kabaros — I would like to work on the remaining Switch accessibility task (LIBS-572).

I checked the repository and could not find an open PR currently addressing Switch accessibility. I plan to inspect the component semantics, keyboard/focus behavior, accessible naming, disabled state, and existing test/story coverage, then submit a focused PR for this component only, as requested in the issue.

Could you please confirm that Switch is still unclaimed and ready to be worked on? If the Jira ticket contains acceptance criteria beyond what is visible publicly, I would appreciate those details before implementation.

[khalilurrrahmanridoykhan]

Picking up the Switch component (LIBS-572) — will raise a PR shortly.

[sankorla315]

Hi @kabaros Can I work on FlyoutMenu. Could you kindly confirm that it is still unclaimed & ready to be worked on? If any Jira ticket info about acceptance criteria in addition to what is visible publicly, I would appreciate those details before implementation.

[sankorla315]

Picking up FlyoutMenu component(LIBS-563), incoming PR shortly!

[koiralajay-ui]

Hi, I’d like to work on LIBS-850 (StatusIcon accessibility) if it’s still available. I checked for an assignee or overlapping PR and didn’t find any current work.

Before starting, could you confirm the intended API? My reading of the ticket is:

• hide the icon from assistive technology when adjacent validation text already communicates the state
• provide an accessible label when StatusIcon is used standalone

Should valid and loading follow the same behavior as error and warning, and do you have a preferred API for this (aria-hidden / aria-label or an existing project convention)?

Happy to take this on once confirmed.