All products

Review table accessibility with AI

Check whether users can read, sort and edit the intended records and whether focus still points somewhere meaningful after rows move or disappear.

Review table accessibility with AI when somebody selects an order, sorts by amount and unexpectedly ends up working on a different customer’s row. The accessible-data-tables-and-grids skill follows a real task through the component. It checks how table semantics, keyboard focus and selection behave as the underlying data changes.

A read-only table with a button in each row does not necessarily need spreadsheet-style navigation. An editable grid has different expectations. Starting with what users should be able to do helps the team choose the right interaction model before changing roles or adding keyboard handlers.

What it does

  • Check that a screen reader identifies the relevant headers for a value.
  • Follow keyboard movement into and out of row actions.
  • Verify that sorting keeps selection associated with the intended record.
  • Test where focus lands after an edit, deletion or page change.
  • Try to reach an off-screen row in a virtualised grid using assistive technology.

Install and use

  1. Provide a working test table and representative fictional rows. Keyboard and screen-reader access are needed for the corresponding manual checks.
  2. Ask, “Select an order, sort by amount and check whether both selection and focus still refer to that order.”
  3. Repeat the same sequence after the fix and distinguish observed assistive-technology results from markup inspection.

FAQ

Source

Made by smukh / a11y-agent-skills contributors. Original skill: accessible-data-tables-and-grids, published on GitHub under the MIT licence.

View on GitHub