Table Accessibility

Community

Owl-Listener

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.

Overview

Publisher	Owl-Listener
Repository	`inclusive-design-skills`
Skill name	`table-accessibility`
Stars	108
Forks	28
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Table Accessibility AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/table-accessibility
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/table-accessibility

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git /tmp/inclusive-design-skills
mkdir -p .claude/skills
cp -r /tmp/inclusive-design-skills/accessible-content/skills/table-accessibility .claude/skills/table-accessibility

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Table Accessibility in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Table Accessibility on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Table Accessibility is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 with scope="col"
Row headers: use 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 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

Frequently asked questions

What does the Table Accessibility AI skill do?

Why use Table Accessibility on TypingMind?

Because you install it once and use it with any model. Table Accessibility is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Table Accessibility in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/table-accessibility. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Table Accessibility?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Table Accessibility?

As many as you like. As long as a model supports skills, you can use Table Accessibility with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Table Accessibility AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Pokemon Player

NousResearch

OrganizationPopular

Play Pokemon via headless emulator + RAM reads.

Docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document',…

Openclaw Docker E2e Authoring

openclaw

OrganizationPopular

Author OpenClaw Docker E2E and live provider Docker lanes.

Openclaw Parallels Smoke

openclaw

OrganizationPopular

Prepare, snapshot, run, rerun, debug, or interpret OpenClaw Parallels guest install, onboarding, gateway smoke, and upgrade checks across macOS, Windows, and Linux.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Table Accessibility

When to Use a Table

Core Requirements

Every Table Needs Headers

Every Table Needs a Caption or Label

Simple Tables Over Complex Tables

Cognitive Accessibility for Tables

Visual Design

Reduce Complexity

Responsive Tables

Assessment Checklist

Frequently asked questions

Related AI Skills

Set up your own AI workspace now