skills.rest
lord-vinayak
lord-vinayakCOMMUNITY
Explore all skills by this author →
Website𝕏@lord_vinayak_GitHub

accessible-tables

Audit HTML tables for WCAG 2.2 and Section 508 accessibility.

Updated May 19, 2026
Search Tags:#accessibility#screen reader#WCAG#HTML#table design
One-click install
npx skills add https://github.com/lord-vinayak/orive-reqcap --skill accessible-tables
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessible-tables
Source: https://github.com/lord-vinayak/orive-reqcap/tree/main/.claude/skills/audit/accessible-tables_
Command: npx skills add https://github.com/lord-vinayak/orive-reqcap --skill accessible-tables

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that your HTML tables are accessible to all users, adhering to WCAG 2.2 standards and Section 508 requirements.

Core Features & Use Cases

  • Accessible Table Design: Offers guidance on creating tables that are navigable and understandable with screen readers.
  • Code Review: Provides best practices for table headers, scope attributes, colspan/rowspan handling, and responsive design.
  • Use Case: When you need to audit or build tables for a website or application, use this Skill to ensure compliance and usability for users with disabilities.

Quick Start

Run the accessible-tables skill to audit your table for accessibility issues.

Frequently Asked Questions about accessible-tables

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

FAQPage Schema
How do I make HTML tables accessible and compliant with WCAG 2.2?▼

To make HTML tables accessible and WCAG 2.2 compliant, use proper table structure, header handling, and scope attributes. This ensures tables are navigable and understandable for screen reader users.

How do I handle colspan and rowspan in accessible table design?▼

For accessible table design, handle colspan and rowspan carefully by ensuring headers remain clearly associated with data cells. Proper scope attributes and structural markup maintain screen reader navigation.

Do I need NVDA, JAWS, or VoiceOver to test table accessibility?▼

Yes, you need NVDA, JAWS, and VoiceOver for real screen reader testing. These tools validate that your accessible table design works correctly across different platforms for visually impaired users.

What is the best way to create responsive data grids that pass Section 508 requirements?▼

The best way to create responsive data grids passing Section 508 requirements is applying proper table structure and responsive patterns. This ensures interactive tables remain accessible across device sizes.

Why does my screen reader not announce table headers properly?▼

Your screen reader may not announce table headers properly due to missing scope attributes or incorrect header handling. Auditing your HTML table structure ensures proper screen reader navigation.

Can I use accessible-tables for auditing existing website tables?▼

Yes, you can use this skill to audit existing website tables for accessibility issues. It reviews table headers, scope attributes, and colspan/rowspan handling against WCAG 2.2 and Section 508 standards.

Related Skills

Explore More Software Engineering Skills→
zenobi-uszenobi-us
68

accessibility-tester

Audit digital interfaces for WCAG 2.1 compliance and accessibility gaps.

Official
Advanced
lord-vinayaklord-vinayak

accessibility-audit

Audit design files and UI descriptions for WCAG 2.2 AAA, Section 508, and ARIA APG compliance.

Community
Advanced
anouar1991anouar1991
1

responsive-design-tester

Audit web pages across six viewports for responsive design issues.

Community
Advanced
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate