Tables Specialist

Audit and remediate HTML data table accessibility against WCAG AA standards.

387|42|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill tables-specialist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Tables Specialist
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/tables-data-specialist
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill tables-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the common accessibility issues found in data tables, ensuring screen reader users can effectively navigate and understand tabular information.

Core Features & Use Cases

  • Semantic Table Structure: Enforces correct use of <table>, <caption>, <thead>, <tbody>, <th>, and <td> elements.
  • Header Association: Ensures proper scope and headers attributes for clear data-to-header relationships.
  • Sortable Tables: Guides implementation of accessible sorting with aria-sort and keyboard support.
  • Interactive Grids: Provides guidance for ARIA role="grid" implementation for editable or interactive tables.
  • Responsive Design: Offers patterns for making tables accessible on various screen sizes.
  • Use Case: Reviewing a complex financial report table to ensure all column and row headers are correctly associated with their corresponding data cells, making it navigable for a visually impaired user.

Quick Start

Use the Tables Specialist skill to audit the accessibility of the provided HTML table code.

Frequently Asked Questions about Tables Specialist

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

FAQPage Schema
How do I make HTML data tables accessible for screen readers?▼

To make HTML data tables accessible, enforce correct semantic markup using `<table>`, `<caption>`, `<thead>`, and `<tbody>` to ensure screen readers can effectively navigate tabular information.

How do I properly associate data cells with headers using ARIA and scope?▼

Associate data cells with headers by applying proper `scope` and `headers` attributes, establishing clear data-to-header relationships that meet WCAG AA standards for screen reader navigation.

What is the best way to implement accessible sorting in data grids?▼

Implement accessible sorting in data grids by applying the `aria-sort` attribute to sortable columns and ensuring full keyboard support, allowing screen reader users to understand and trigger sorting actions.

When do I need to use ARIA grid roles for interactive tables?▼

Use ARIA `role="grid"` for interactive tables when implementing editable or dynamic data grids, ensuring the interface provides the necessary semantic structure for assistive technologies to navigate complex data.

How do I handle responsive table accessibility on mobile screens?▼

Handle responsive table accessibility by applying specific patterns for various screen sizes, ensuring that tabular data remains navigable and comprehensible for visually impaired users across different mobile devices.

Does this table accessibility audit enforce WCag AA compliance?▼

Yes, this table accessibility audit enforces WCAG AA compliance by remediating semantic table structure, header associations, sortable column implementation, and ARIA grid roles according to standard accessibility guidelines.