-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WCAG 4.1.2 A: Back to top button has no accessible name (Issue 34) #359
Labels
A11y
Issue is related to accessibility
Core CivicTheme
Core CivicTheme issue
State: Done
The issue is complete and waiting for a release
Type: Defect
Issue is a defect
Comments
@jcloys https://www.drupal.org/project/civictheme/issues/3466016 Amey provided this patch to address the above issue - could you review the fix and let me know if it resolves the above. |
alan-cole
added a commit
that referenced
this issue
Sep 25, 2024
7 tasks
richardgaunt
pushed a commit
that referenced
this issue
Oct 1, 2024
@sonamchaturvedi28 Fix has been merged and is ready for testing. |
@CJE001 this issue is pending release. I'm closing this ticket as work was done in https://www.drupal.org/project/civictheme/issues/3466016. |
Fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A11y
Issue is related to accessibility
Core CivicTheme
Core CivicTheme issue
State: Done
The issue is complete and waiting for a release
Type: Defect
Issue is a defect
Summary
Via Vision Australia assessment: August 2024
Impact: medium
Note: DTA have a 90 day remediation period to address the identified issues within the audit, all issues must be resolved to obtain WCAG 2.2 certification for digital.gov.au
Steps to reproduce
Global issue – Back to top button
digital.gov.au beta | digital.gov.au (https://www.digital.gov.au)
Observed outcome
The back to top button uses an arrow icon to visually communicate its purpose; however, the button has no accessible name.
Code used
Why this matters
When a button lacks an accessible name, screen readers cannot communicate its purpose or functionality to users. As a result, users may have difficulty determining what the button does or how to interact with it.
Users who navigate with speech recognition technologies may encounter difficulties activating interactive elements without an accessible name. They may be forced to use alternative navigation methods, such as the mouse grid, which can be considerably more time consuming.
Expected outcome
Preferably, provide an accessible name for the button via HTML text content. This will be visible for all users and ensure that the button purpose is clear.
Alternatively, provide an accessible name for the button via visually hidden text or the aria-label attribute.
Ideally, adjust the border colour of the element so that it is more visible when the link appears over a darker background (for example, as has been done with the feedback widget). While this is not required for WCAG conformance, it will improve the discoverability of the link.
Code example – text content
Code example – visually hidden text
Code example – aria label
The text was updated successfully, but these errors were encountered: