data-table-grid-accessibility-audit

Audits data tables and ARIA grids for WCAG accessibility across keyboard, screen-reader, and responsive behavior.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/vmitsaras/Agent-Skills --skill data-table-grid-accessibility-audit-vmitsaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-table-grid-accessibility-audit
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/frontend-a11y/data-table-grid-accessibility-audit
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill data-table-grid-accessibility-audit-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Data tables and interactive grids often hide accessibility defects—broken header associations, missing sort state, keyboard traps, and silent result updates—that block screen-reader and keyboard users from working with tabular data. ## Core Features & Use Cases - Model classification: Distinguishes native tables, sortable tables, ARIA tables, grids, and treegrids before applying the correct interaction expectations. - Comprehensive audit workflow: Reviews captions, header associations, sorting, filtering, selection, row actions, virtualization, responsive alternatives, and status announcements. - Structured findings: Produces a shared finding contract with evidence, user impact, severity, WCAG 2.2 mappings, remediation, and verification steps. - Use Case: A design-system maintainer ships a virtualized data grid with sorting and row selection; this Skill audits keyboard navigation, aria-rowindex correctness, selection announcements, and responsive card fallbacks, then returns confirmed findings mapped to WCAG criteria. ## Quick Start Audit the orders table on the account page for accessibility, covering sorting, keyboard navigation, selection, and screen-reader announcements, and report findings mapped to WCAG 2.2.

Frequently Asked Questions about data-table-grid-accessibility-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a data table for WCAG accessibility?▼

Classify the table model first, then review captions, header associations, sort state, keyboard behavior, selection, and announcements against WCAG 2.2 criteria. Record each finding with evidence, user impact, severity, and verification steps rather than claiming conformance.

When should I use ARIA grid instead of a native HTML table?▼

Use a native table for static or sortable data, even when cells contain buttons, links, or checkboxes. Reserve role="grid" for composite widgets with managed arrow-key navigation, and only when you can implement the full focus and keyboard contract.

Does aria-sort support multi-column sorting?▼

No. aria-sort applies only to the single header currently controlling sort and cannot express multiple sort keys or their priority. Document multi-column sort precedence and direction in accessible text alongside aria-sort.

How do I make a virtualized grid accessible to screen readers?▼

Expose logical totals and positions with aria-rowcount, aria-colcount, aria-rowindex, and aria-colindex, and ensure recycled DOM rows do not duplicate IDs or stale states. Manual screen-reader testing across virtualization boundaries is required.

Can this audit certify WCAG conformance?▼

No. The audit reports confirmed, provisional, and needs-validation findings bound to the evidence inspected. It explicitly avoids complete-conformance, certification, or legal-compliance claims, and absence of evidence is never treated as a pass.