| Milestone 1a finding ID | M1a-009 |
|---|---|
| Backlog priority | High |
| Severity — carried from Milestone 1a | Moderate |
| Implementation effort | Medium |
| Target milestone(s) | MS2b — Core Forms and Validation; MS3b — Backend Template Build |
| 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 | Atum — main menu toggle button — Milestone 1a finding #9 |
| Affected user journey(s) | 01 — Backend Template (Atum) |
The Toggle Menu control is implemented as a link with href="#".
It does not convey whether the main menu is expanded or collapsed to assistive technology.
The report recommends replacing the link with a <button> element. It suggests using aria-pressed to expose the toggle state, or alternatively changing the visible button text between states.
The report also notes that an aria-label should generally not override visible text when that text can serve as the accessible name.
Screen-reader users hear a link named “Toggle Menu” but cannot determine whether the menu is currently expanded or collapsed.
Because the control is a link, it may not support the expected Space activation behaviour for a button. Users relying on keyboard interaction may find its behaviour unexpected.
Without state information, users may activate the control more than once or be uncertain whether their action changed the sidebar.
Use button semantics and expose the sidebar state
href="#" link with a <button> elementaria-pressed on the button, or changing its visible text between “Collapse Menu” and “Show Menu”aria-label unless needed/administrator/href, accessible name, and any ARIA state attributes<button>6.2
The main-menu toggle is a button and conveys whether the sidebar is expanded or collapsed to assistive technology.
It can be activated with both Enter and Space, and its state change is perceivable after activation.
The Toggle Menu control is implemented as a link with href="#".
It does not convey the current expanded or collapsed state to assistive technology.
The current Joomla 6.2 build needs to be checked to establish whether the issue persists.
Desktop web
Chrome, Firefox, Edge, Safari
VoiceOver, JAWS, NVDA
The browser and assistive-technology entries above are carried forward from the original issue and do not represent a new verification of every combination against Joomla 6.2.
Development is the responsibility tag in the original report.
The report presents both aria-pressed and changing visible button text as possible approaches. Choose and verify one consistent approach.
The report advises against using aria-label to override visible text unnecessarily. Use the visible text or aria-labelledby where possible.
This issue concerns the sidebar toggle's semantics and state. It is distinct from #48398, which concerns how the current menu item is indicated.
MS2b is proposed for the shared sidebar-toggle component, with MS3b covering the documented Atum integration.
| Labels |
Added:
a11y
|
||
| Labels |
Added:
No Code Attached Yet
|
||
| Labels |
Added:
a11y-priority-serious (High)
|
||
| Labels |
Added:
a11y-audit-backlog
|
||
| Title |
|
||||||
| Labels |
Added:
a11y-ms1b-quickwins
|
||
see #48696