Bug 39472

Summary: WCAG 2.1: 2.5.3 - Label in Name (Level A)
Product: Koha Reporter: Martin Renvoize (ashimema) <martin.renvoize>
Component: AccessibilityAssignee: Bugs List <koha-bugs>
Status: CONFIRMED --- QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: martin.renvoize, matt.blenkinsop, oleonard
Version: unspecifiedKeywords: Hackfest
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Martin Renvoize (ashimema) 2025-03-27 15:37:44 UTC
https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html


Issue
• The ‘Sign in’ button has been given the aria-label ‘Log into your account’
• Although this is a clear label, it does not match the visible label
• This may prevent speech-input users from being able to interact effectively
with this button as the label they can see and that they will speak, does not
match the programmatic label required to activate the control

Solution
• Ensure that the accessible name matches or contains the text that is
presented visually
• Where possible, the accessible name should be assigned through native
elements and semantics. That helps ensure an exact match between the
visible label and name
• Note: aria-label and arialabelled-by overrides any other information
associated with the element so make sure it matches the visible text

https://webaim.org/articles/label-name/
Comment 1 Martin Renvoize (ashimema) 2025-03-27 15:39:46 UTC
I have a feeling this may be translation related.  Do we make sure that the aria-label/labeledby text matches the link/button text during translation?