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-009 |
|---|---|
| Backlog priority | High |
| Severity — carried from Milestone 1a | Moderate |
| Implementation effort | Medium |
| Target milestone(s) | MS2b, MS3a, MS3b, MS5a, MS7b, MS8a, MS10 |
| WCAG 2.2 success criterion | 1.3.1 Info and Relationships; 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#767da205-0a92-4160-81fa-bb6eabe3dda9 |
| Affected user journey(s) | 01 – Backend Template (Atum) |
| Source report/reference | Milestone 1a WCAG audit report |
| STF reporting reference | To be assigned |
| Issue owner | To be assigned |
| Status | Triage |
Audit finding
Menu toggle button does not convey state, uses wrong role
User impact
Many assistive-technology users will not be able to determine the proper state of the control. As such, they may be blocked from operating the interface or completing the task with confidence.
Remediation plan
Refactor the interaction so it is fully keyboard operable, uses correct semantics and states, and preserves predictable focus movement.
Steps to reproduce
6.1
Proper button role on control, correct state conveyed.
Button is a link. Appropriate state of control not conveyed to assistive technology.
Desktop web
Chrome, Firefox, Edge, Safari
VoiceOver, JAWS, NVDA
No response
| Labels |
Added:
a11y
|
||
| Labels |
Added:
No Code Attached Yet
|
||
| Labels |
Added:
a11y-priority-serious (High)
|
||
| Labels |
Added:
a11y-audit-backlog
|
||
| Title |
|
||||||