Skip to content

A11y report fixes #14530

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

Merged
merged 15 commits into from
Jul 10, 2025
Merged

A11y report fixes #14530

merged 15 commits into from
Jul 10, 2025

Conversation

aalves08
Copy link
Member

@aalves08 aalves08 commented Jun 17, 2025

Summary

Fixes #14556

Work done was based on this report with 219 violations:
before

accessibility-report (5).zip

Current status after this PR is 64 violations, as per:
after

Occurred changes and/or fixed issues

  • Fixes "low-hanging" fruit from a11y test report, as per the following description:

item 2: All page content should be contained by landmarks

Commit: e281019

Changes:

  • page level content like SlideInPanel, PluginInfoPanel, SlideInPanelManager and AppModal wasn't being contained by landmark items

4. Elements must only use permitted ARIA attributes

Commit: 41bb10e

Changes:

  • fix missing or wrong roles in different pages/components

6. ARIA attributes must conform to valid values

Commit: b85b1f7

Changes:

  • Fix wrong usage of aria-controls and add missing role and id

7. "ul" and "ol" must only directly contain "li", "script" or "template" elements

Commit: a4b3a8d

Changes:

  • replace div for li as direct child of ul in Wizard component

8. Interactive controls must not be nested

Commit: f472572

Changes:

  • Change side nav Group component in order to have "chevron" tabbable item as sibling of router-link in order to comply with a11y specs

Before PR
light
dark

After PR (no visual or usability regresssions)
light_from_pr
dark_from_pr

10. ARIA toggle fields must have an accessible name

Commit: d1154ef

Changes:

  • Fix Checkbox component where using labelKey the translation tag <t> wasn't inherithing the id used for internal aria-labelledby

11. autocomplete attribute must be used correctly

Commit: 264c72f

Changes:

  • Fix wrongful usage of autocomplete attribute

12. Form elements must have labels

Commit: 0189291 + a1ab1d8

Changes:

  • add aria-hidden to "hidden" inputs so that assistive technologies and a11y tests won't pick them up

14. ARIA input fields must have an accessible name

Commit: 5796087

Changes:

  • Add missing aria-label on NamespaceFilter component

15. Buttons must have discernible text

Commit: 97d9003

Changes:

  • add missing aria-label to header actions (buttons) coming from extensions + plus and minus actions on Tabbed (Tabs) component

16. Images must have alternative text

Commit: b62608e

Changes:

  • add missing alt to header actions (buttons) icons coming from extensions

17. ARIA role should be appropriate for the element

Commit: 4df25b8 + ad80144

Changes:

  • Fix issue where input type="number" had wrongful role="textbox" (role is inherent) + label html elements cannot have role="columnheader"

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

Checklist

  • The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
  • The PR has a Milestone
  • The PR template has been filled out
  • The PR has been self reviewed
  • The PR has a reviewer assigned
  • The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
  • The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
  • The PR has been reviewed in terms of Accessibility

@aalves08 aalves08 added this to the v2.12.0 milestone Jun 23, 2025
@aalves08 aalves08 force-pushed the a11y-report-fixes branch 2 times, most recently from 1392a97 to 4df25b8 Compare June 25, 2025 12:40
@aalves08 aalves08 requested review from nwmac and rak-phillip June 26, 2025 13:41
@aalves08 aalves08 marked this pull request as ready for review June 26, 2025 13:41
@aalves08 aalves08 requested a review from rak-phillip June 27, 2025 10:42
@aalves08
Copy link
Member Author

@rak-phillip add pr comments addressed. Ready for another go

Copy link
Member

@nwmac nwmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me

@aalves08 aalves08 requested a review from richard-cox June 27, 2025 14:03
@aalves08 aalves08 force-pushed the a11y-report-fixes branch from 2ca2a78 to 8200e29 Compare July 7, 2025 09:28
Copy link
Member

@rak-phillip rak-phillip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@aalves08 aalves08 merged commit faa7fe3 into rancher:master Jul 10, 2025
36 checks passed
@torchiaf
Copy link
Member

We found a regression introduced by current PR, @aalves08 could you take a look ?

@aalves08
Copy link
Member Author

We found a regression introduced by current PR, @aalves08 could you take a look ?

On it @torchiaf 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Review a11y report and fix low-hanging fruit
4 participants