Skip to content
Skills Library
Design & UX · Building & coding

table-accessibility

/table-accessibility

Design data tables that work for screen readers and cognitive accessibility. Use when creating or reviewing tables, data grids, comparison tables, pricing tables, or any tabular data. Triggers on: table, data table, grid, spreadsheet, comparison table, pricing table, screen reader table, table headers, scope, caption, complex table.

Licence
MIT
Last repository change
09.06.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Design data tables that work for screen readers and cognitive accessibility. Use when creating or reviewing tables, data grids, comparison tables, pricing tables, or any tabular data. Triggers on: table, data table, grid, spreadsheet, comparison table, pricing table, screen reader table, table headers, scope, caption, complex table.

Original author description

Design data tables that work for screen readers and cognitive accessibility. Use when creating or reviewing tables, data grids, comparison tables, pricing tables, or any tabular data. Triggers on: table, data table, grid, spreadsheet, comparison table, pricing table, screen reader table, table headers, scope, caption, complex table.

How it works

  1. When to Use a Table
  2. Core Requirements
  3. Cognitive Accessibility for Tables
  4. Assessment Checklist
Original SKILL.md headings · 74 lines, 463 words
SKILL.md preview
---
name: table-accessibility
description: "Design data tables that work for screen readers and cognitive accessibility. Use when creating or reviewing tables, data grids, comparison tables, pricing tables, or any tabular data. Triggers on: table, data table, grid, spreadsheet, comparison table, pricing table, screen reader table, table headers, scope, caption, complex table."
---

# Table Accessibility

Design tables that communicate structure and relationships — not just
to sighted users scanning rows and columns, but to screen reader users
who navigate one cell at a time.

## When to Use a Table

Tables are for data that has relationships across two dimensions (rows
and columns). Don't use tables for layout.

- Use a table: comparing features across products, showing schedules,
  displaying data with consistent categories
- Don't use a table: laying out a form, arranging cards, creating
  visual columns of unrelated content

## Core Requirements

### Every Table Needs Headers
- Column headers: use <th> with scope="col"
- Row headers: use <th> with scope="row"
- Screen readers announce headers before each cell, so users always
  know which column and row they're in
- Without headers, a screen reader user hears a stream of disconnected
  values with no context

### Every Table Needs a Caption or Label
- Use <caption> element for HTML tables
- Or use aria-labelledby pointing to a visible heading
- The caption describes what the table contains:
  "Pricing comparison for Standard, Pro, and Enterprise plans"
- Not just "Table 1" or "Data"

### Simple Tables Over Complex Tables
- Prefer simple tables with one row of column headers
- Avoid merged cells (colspan, rowspan) wherever possible
- If merged cells are necessary, use proper headers/id/scope
  associations
- If a table needs merged cells to make sense, consider whether
  it should be split into multiple simpler tables

## Cognitive Accessibility for Tables

### Visual Design
- Zebra striping (alternating row colours) aids row tracking
- Adequate cell padding (at least 8px) prevents crowding
- Align numbers right, text left for readability
- Highlight the header row with stronger contrast

### Reduce Complexity
- Maximum 5–7 columns for comfortable scanning
- If more columns are needed, consider a different format
  or allow users to show/hide columns
- Provide a summary or key takeaway above complex tables
- Don't require horizontal scrolling — make tables responsive

### Responsive Tables
- On small screens: convert to card/list view where each row
  becomes a labelled card
- Or allow horizontal scroll with a sticky first column
- Never hide data on smaller screens without a way to access it
- Test: can a mobile user access every piece of data?

## Assessment Checklist

- [ ] All tables have column and/or row headers with proper scope
- [ ] All tables have a caption or accessible label
- [ ] No merged cells (or properly associated headers if unavoidable)
- [ ] Tables are responsive on small screens
- [ ] Tables are not used for visual layout
- [ ] Complex tables have a text summary of key findings
- [ ] Cell padding and spacing support readability

Versions

The database has no other skills named table-accessibility.

Database snapshot: 13.11.2026 · package version fb6ae54de281 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100fe-a11y-tables
    Builds data tables that screen readers can navigate and small screens can show (WCAG 2.2 AA as a target) - th with scope, captions, sortable headers with aria-sort, responsive scroll containers, and when a table should be a list or a grid. Use when rendering tabular data, a…
  • 91using-frontend-data-table
    Creates frontend table views. Use whenever creating any type of table UI on the frontend. Use when doing ANYHTHING that involves tables (using tables to display data).
  • 90accessible-data-tables-and-grids
    Reviews native data tables and interactive grids, including sorting, editing, selection, pagination, and virtualized rows. Use for tabular-data accessibility rather than CSS layout grids.
  • 85ux-tables
    Design or critique data tables and lists — scannable structure, alignment rules (left for text, right for numbers), sorting/filtering, row interactions, and the right list type for the content. Trigger when the user asks to design or review a data table, data grid, admin table,…
  • 100table-headers
    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Define proper table headers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
  • 100table-duplicate-name
    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure tables have unique accessible names. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.