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-023 |
|---|---|
| Backlog priority | Medium |
| Severity — carried from Milestone 1a | Moderate |
| Implementation effort | Low |
| Target milestone(s) | MS7a, MS7b, MS8a, MS10 |
| WCAG 2.2 success criterion | 1.3.2 Meaningful Sequence; 2.4.3 Focus Order |
| Responsibility tag(s) from report | Development |
| Affected Joomla area/component | https://accessibility-project.joomla.org/results/Milestone-1a/milestone1/deliverable1/wcag-report#376441bb-6f3a-41c6-b80a-294521004e0d |
| Affected user journey(s) | 05 – MFA Setup - Method / Methods Views; 09 – Backend Edit Form Pattern |
| Source report/reference | Milestone 1a WCAG audit report |
| STF reporting reference | To be assigned |
| Issue owner | To be assigned |
| Status | Triage |
Audit finding
Button order confusing
User impact
The user will receive button information out of context.
Remediation plan
Implement a component-level and template-level fix that removes the barrier in all affected states and add verification coverage so the issue stays resolved.
Steps to reproduce (Articles: Edit example)
6.1
The Save & Close button has additional options which are signaled by a drop down arrow on the right of the button with the accessible label “Toggle Dropdown”. These would be read in sequence so that users have context as to which control the toggle activates.
In the keyboard focus order, the dropdown button comes first, meaning that a user comes across the secondary information first, before the primary one.
Desktop web
Chrome, Firefox, Edge, Safari
VoiceOver, JAWS, NVDA
No response
| Labels |
Added:
a11y
a11y-audit-backlog
a11y-priority-moderate (Medium)
|
||
| Labels |
Added:
No Code Attached Yet
|
||
| Title |
|
||||||