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

A11Y - Make tables readable to screen readers #21947

Open
14 tasks
saragunnarsson opened this issue Jun 20, 2024 · 1 comment
Open
14 tasks

A11Y - Make tables readable to screen readers #21947

saragunnarsson opened this issue Jun 20, 2024 · 1 comment

Comments

@saragunnarsson
Copy link
Collaborator

saragunnarsson commented Jun 20, 2024

FIGMA FILE HERE

General Table issues:

  • Make sure no Table Headers gets announced twice by reader
  • If a table is scrollable, make sure you can continue navigating to the rows that are further down in the table (that you have to scroll to). Right now it jumps back up to the table header instead of scrolling the table.
  • Fix labeling for all download PDF buttons
  • Set hyphens to be announced as 'None'
  • Fix how icons + value in same columns are being announced
  • Make sure no divs or other semantics are hindering the screenreader from announcing the value in the columns

Home owner table:

  • Set role to presentation
  • Fix how the icons are being announced

MHR / PPR Table

  • Make sure the filters don’t get announced every time the reader reads the Table Headers.
  • Fix expand collapse buttons and how they are being read
  • Fix registration type column and make sure it gets read/navigated as specified in figma
  • Verification statement columns: Fix PDF button announcement
  • Fix how open/edit buttons in Table are announced

Global Split button issue

  • Can’t get to and select the submenu items when opening the split button via screen reader

Video example of how the MHR table is being read (no sound but it is scripted):
View Here

@LizGovier
Copy link
Collaborator

LizGovier commented Jun 27, 2024

@LizGovier cc @arlentees
What are the standard screen reader tools we should be catering too? Mac Voice Over? NVDA, JAWS, Chrome?

Liz: Review Global Split button issue with Alexis

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

No branches or pull requests

2 participants