Bug 33764

Summary: Accessibility: Fix ambiguous form-field in masthead.inc
Product: Koha Reporter: Matt Blenkinsop <matt.blenkinsop>
Component: TemplatesAssignee: Matt Blenkinsop <matt.blenkinsop>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: Laura.escamilla, m.de.rooy
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33765
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33766
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Bug Depends on:    
Bug Blocks: 23003    
Attachments: Bug 33764: Fix ambiguous "Login" field
Bug 33764: Fix ambiguous "Login" field

Description Matt Blenkinsop 2023-05-18 12:51:25 UTC
The form field for "muserid" is called Login. This is confusing for screen readers and has been flagged as non-compliant in an accessibility report carried out for the British Museum.
Comment 1 Matt Blenkinsop 2023-05-18 12:55:31 UTC
Created attachment 151412 [details] [review]
Bug 33764: Fix ambiguous "Login" field

This patch changes the use of "Login" to "Username" to assist with screen reading

Test plan:
1) In the masthead, click Log in to your account
2) On the modal, the first input should be labelled Username
Comment 2 ByWater Sandboxes 2023-05-18 15:18:19 UTC
Created attachment 151424 [details] [review]
Bug 33764: Fix ambiguous "Login" field

This patch changes the use of "Login" to "Username" to assist with screen reading

Test plan:
1) In the masthead, click Log in to your account
2) On the modal, the first input should be labelled Username

Signed-off-by: Laura Escamilla <laura.escamilla@bywatersolutions.com>
Comment 3 Marcel de Rooy 2023-05-19 09:24:42 UTC
Please fix on the other report too. 33765
Comment 4 Matt Blenkinsop 2023-05-19 13:52:57 UTC
In light of the ongoing discussion on bug 33766 I think its best to close this bug and bug 33765 and wrap all instances of this issue into bug 33766 when the discussion is concluded
Comment 5 Matt Blenkinsop 2023-05-19 13:53:44 UTC

*** This bug has been marked as a duplicate of bug 33766 ***