Skip to content
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

Members table: Change tab order for expand button and make the additional permissions text accessible to screenreaders #3365

Open
2 tasks
zandercymatics opened this issue Jan 17, 2025 · 0 comments
Labels
accessibility pertains to Section 508 compliance or other accessibility needs dev issue is for the dev team

Comments

@zandercymatics
Copy link
Contributor

zandercymatics commented Jan 17, 2025

Issue description

Currently, the members table has some accessibility issues regarding the "Expand" button - as well as for its content.
Of note, the tab order "jumps" back up to the manage and action buttons when it is opened, rather than the domain links.
Additionally, the "additional permissions" text is not presently accessible for screenreaders.

Acceptance criteria

  • The tabindex for the expand button is changed such that when expanded, it navigates through the "domains assigned" domain list, if it exists
  • Make the "additional permissions" text block accessible to screenreaders
    • This can be done with aria-describedby, or potentially by using tabindex as before

Additional context

These two items are the result of our design review for the member pages.
For more context, see these slack threads:

Prioritization Comments

WCAG Conformance Level: AA
WCAG Standard that applies: 2.4.3 Focus Order, 1.3.1 Info and Relationships
Critical Failure if Not Met?: Yes
Prioritization: High/Must Do
Reason: Improper focus order and inaccessible content create significant usability barriers for keyboard and screen reader users, making it difficult to navigate and understand key information. Ensuring logical focus order and screen reader accessibility is critical to compliance and user experience. This issue is not linked to a current remediation plan, however it will likely be called out in upcoming compliance testing.

Links to other issues

@zandercymatics zandercymatics added accessibility pertains to Section 508 compliance or other accessibility needs dev issue is for the dev team labels Jan 17, 2025
@zandercymatics zandercymatics moved this from 👶 New to ⚙ Dev Parking Lot in .gov Product Board Jan 17, 2025
@zandercymatics zandercymatics changed the title [draft] Members table: Change tab order for expand button and make the additional permissions text accessible to screenreaders Members table: Change tab order for expand button and make the additional permissions text accessible to screenreaders Jan 17, 2025
@abroddrick abroddrick moved this from ⚙ Dev Parking Lot to 🎯 Ready in .gov Product Board Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility pertains to Section 508 compliance or other accessibility needs dev issue is for the dev team
Projects
Status: 🎯 Ready
Development

No branches or pull requests

1 participant