accessible-data-tables-and-grids
Skill8 starsChanged 2 months agoMITView on GitHub
1. Identify the actual task and choose table or grid semantics using the table and grid review guide. Preserve valid native tables. 2. Inventory headers, sort state, selection, editing, row actions, pagination, and virtualization. Only assess behaviors the product implements. 3. Replay navigation and mutations using stable record identities. Check what happens to focus and selection when rows reorder, disappear, or leave the rendered window. 4. Repair the owning component, preserving data and supported interactions. Test navigation and the same…
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- accessibility-regression-testSkill
- accessible-authenticationSkill
- accessible-charts-and-dashboardsSkill
- accessible-combobox-and-autocompleteSkill
- accessible-component-reviewSkill
- accessible-dynamic-updatesSkill
- accessible-formsSkill
- dialog-accessibilitySkill
- fix-accessibility-issueSkill
- keyboard-navigation-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Do not assign role=grid merely because a table contains buttons or sortable headers.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Accessible data tables and grids
Workflow
- Identify the actual task and choose table or grid semantics using the table and grid review guide. Preserve valid native tables.
- Inventory headers, sort state, selection, editing, row actions, pagination, and virtualization. Only assess behaviors the product implements.
- Replay navigation and mutations using stable record identities. Check what happens to focus and selection when rows reorder, disappear, or leave the rendered window.
- Repair the owning component, preserving data and supported interactions. Test navigation and the same sort/edit/delete sequence against broken and repaired states.
- Apply the guide's manual reading and interaction checks, recording actual AT results separately from DOM and keyboard evidence.
Boundaries
Do not assign role=grid merely because a table contains buttons or sortable headers. APG is design guidance, not an independent conformance standard. Logical row indices do not establish that virtualized content can actually be reached with assistive technology.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

