| Milestone 1a finding ID | M1a-036 |
|---|---|
| Backlog priority | High |
| Severity — carried from Milestone 1a | Serious |
| Implementation effort | Low |
| Target milestone(s) | MS2b — Core Forms and Validation; MS3b — Backend Template Build |
| WCAG 2.2 success criterion | 1.1.1 Non-text Content; 1.4.3 Contrast (Minimum); 2.5.3 Label in Name; 4.1.2 Name, Role, Value |
| Responsibility tag(s) from report | Development |
| Affected Joomla area/component | MFA Captive View — MFA method-selection link names — Milestone 1a finding #36 |
| Affected user journey(s) | 04 — MFA Captive View (FE + BE) |
When selecting an MFA method, users are presented with links such as Backup Codes, Code by Email, and Passkey.
Each link contains:
alt text matching the method nameBecause all three are inside the link, the accessible name repeats. For example, the report identifies “My Passkey Passkey Passkey” and “Code by Email Code by Email Code by Email”.
The report recommends making the image alt text empty and removing the duplicated hint text, so the link name is announced once.
Screen-reader users hear the same method name repeated multiple times when navigating normally or using a links list.
The repeated wording makes the MFA method list harder to scan and can be disorienting, particularly during sign-in when users need to choose a method quickly.
The verbose accessible names also make the links list less useful for navigation.
Provide one concise accessible name for each MFA method link
alt attribute to an empty string when the adjacent visible text already identifies the methodalt attribute, and any hint textalt attribute is empty when the visible text identifies the method6.2
Each MFA method link has a concise accessible name that identifies the method once.
The method image does not duplicate the visible method name, and duplicated hint text does not contribute to the accessible name.
Screen-reader users can scan and distinguish the available MFA methods in normal reading mode and links-list mode.
The MFA method links repeat the method name in their accessible names.
The image alt text and hint text duplicate the visible method name inside each link.
For example, the report identifies accessible names such as “My Passkey Passkey Passkey” and “Code by Email Code by Email Code by Email”.
The current Joomla 6.2 build needs to be checked to establish whether the issue persists and which MFA methods are affected.
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 also notes that the helper text did not meet contrast requirements. Because the recommended fix removes that duplicated text, this issue focuses on the accessible name; contrast should be checked separately if equivalent helper text is retained.
This issue concerns the accessible names of MFA method-selection links. It is distinct from #48373, which concerns the missing alternative text for the MFA setup QR code.
MS2b is proposed for the shared MFA method-selection component, with MS3b covering the documented Atum and Cassiopeia integrations.
| Labels |
Added:
No Code Attached Yet
a11y
|
||
| Labels |
Added:
a11y-priority-serious (High)
|
||
| Labels |
Added:
a11y-audit-backlog
|
||
| Title |
|
||||||
Where does that screen exist - its not what I am seeing
Apologies for not being more specific. It's in the "User: Edit Profile" screen within the "Multi-factor Authentication" tab.
However, the audit report screenshot of the issue seems to show a different screen than what I see, so perhaps the issue belongs to the initial MFA setup during a new user creation process and not the editing of existing preferences for existing users. Are those screens different depending if the user exists or not, and is the code different?
When I tested with a screen reader in the Edit Profile section, the output was correct. However, the report indicates that the output should be as follows:
These links contain the link name (Passkey, Code by Email, …) an image that represents that method, and a hint text that is the same text as the actual link name. As the images have alt attributes and all three elements are part of the link, the Passkey link’s accessible name is “My Passkey Passkey Passkey” while the “Code by Email” link’s accessible name is “Code by Email Code by Email Code by Email”.
...which makes me believe that the audit report specifies the creation of a new user account.
Sorry I have no idea which is why I asked
Me either. If we can mimic a new user creation process we'll be able to test the MFA setup in mobile view and determine if that's where the issue is, because it's definitely not in the backend setting sections of an existing user account.
| Labels |
Added:
a11y-ms1b-quickwins
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-11-05 22:54:14 |
| Closed_By | ⇒ | drmenzelit |
Where does that screen exist - its not what I am seeing