-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add Unique ARIA Label to Navigation Landmark #622
Comments
Hey @bbertucc, this is pretty cool. One note. The word "Navigation" inside the Thanks. |
Good catch @alexstine! I've adjusted it to just be "Main". |
FYI, I've moved this from the Learn repo to |
@ryelle The reference is in the new theme? Maybe not but thought it might be worth a check. |
The new Learn theme pulls in the global header, it's that first line I'm sure this issue is also happening on https://wordpress.org/plugins/ for example, since it's all the same navigation. |
I added an "Impact" section to motivate development
|
Updated with "How critical is this fix?", based on @ryelle's feedback in the Make WordPress slack |
Description:
The navigation landmark on the Learning Pathways page needs a unique ARIA label to improve accessibility. Currently, the aria-label attribute is empty, which does not distinguish the landmark for screen readers.
Current Code:
Proposed Fix:
Update the aria-label attribute to a unique, descriptive label.
Updated Code:
Steps to Reproduce:
Acceptance Criteria:
The aria-label attribute for the navigation landmark should be populated with a unique, descriptive label (e.g., "Main Navigation").
Ensure that the label accurately describes the purpose of the navigation landmark for screen readers.
How critical is this fix?
This change will help improve accessibility by making landmarks distinguishable for users relying on assistive technologies. Without this change, users may be frustrated and abandon non-critical workflows. Will get in the way of compliance if not fixed.
Affected Pages:
This issue is reported on 36,509 pages Equalify scanned. Solving this issue will solve the issue on those pages.
Additional Notes:
This ticket was automatically generated via Equalify and fact-checked by @bbertucc.
The text was updated successfully, but these errors were encountered: