[#48391] - Atum Global Configuration / Atum Joomla Editor / Cassiopeia Forms: Tag selectors very difficult to use
- New
- Medium
- Build: 5.4-dev
- # 48391
Steps to reproduce the issue
NOTE: Accessibility backlog issue and work-in-progress. This issue has been opened to account for all the issues flagged in the initial Milestone 1a Audit Report. If this is a duplicate issue, it will be closed by the end of September 2026.
| Milestone 1a finding ID | M1a-022 |
|---|---|
| Backlog priority | Medium |
| Severity — carried from Milestone 1a | Moderate |
| Implementation effort | High |
| Target milestone(s) | MS2b, MS3b, MS5a, MS5b, MS8a, MS10 |
| WCAG 2.2 success criterion | 1.3.1 Info and Relationships; 1.3.2 Meaningful Sequence; 2.4.3 Focus Order; 2.4.6 Headings and Labels; 2.5.8 Target Size (Minimum); 3.3.2 Labels or Instructions; 4.1.2 Name, Role, Value |
| Responsibility tag(s) from report | Development |
| Affected Joomla area/component | https://accessibility-project.joomla.org/results/Milestone-1a/milestone1/deliverable1/wcag-report#3134a63b-b616-4cb1-833f-a523c82df001 |
| Affected user journey(s) | 09 – Backend Edit Form Pattern; 10 – Frontend User Forms; 11 – Backend Options including Permissions |
| Source report/reference | Milestone 1a WCAG audit report |
| STF reporting reference | To be assigned |
| Issue owner | To be assigned |
| Status | Triage |
Audit finding
Tag selectors very difficult to use
User impact
The issue creates an accessibility barrier in the affected screens.
Remediation plan
Implement a component-level and template-level fix that removes the barrier in all affected states.
Steps to reproduce (Global Configuration screen example)
- Open Atum’s Global Configuration > Logging section.
- Focus the tag selector within “Log Priorities”.
- Search, select, review, and remove tags using only the keyboard.
- Repeat with a screen reader.
- Observe unclear announcements, focus, or operation.
Version
6.1
Expected result
Selected tags would be read after the dropdown. Refer to the selected tags using aria-describedby and by marking them selected in the dropdown. Do not mark unselected but focused options as selected.
Actual result
The tag selection interface is working poorly with the keyboard and when using screen readers. The user first has to move past the existing tags with the keyboard. Screen reader users focus on the “Remove item” buttons, which means they can only review which tags are selected by repeatedly hearing ”Remove item” again and again.
In addition, the remove buttons come before the “Type or select some tags” text field and while the visual “Tags” label communicates the purpose of the next UI elements well, this is not really available for users of assistive technologies.
In addition, focused but not selected options in the combobox are announced as selected. Removing a tag makes the page lose track of the focus and puts the focus to the top of the page. The “Remove” buttons are too small (less than 24×24 pixels).
What device were you using? (eg, phone, laptop)
Desktop web
What web browser were you using? (eg, Chrome, Safari)
Chrome, Firefox, Edge, Safari
Assistive Technology?
VoiceOver, JAWS, NVDA
Additional Comments
No response
| Labels |
Added:
a11y
a11y-audit-backlog
a11y-priority-moderate (Medium)
|
||
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
| Title |
|
||||||