Color Audit
rome-os/rome
Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Install Accessible Heading Structure
$ npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills heading-structure --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/accessible-content/skills/heading-structure .claude/skills/heading-structure && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "heading-structure" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structure into .claude/skills/heading-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "heading-structure", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills heading-structure --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/accessible-content/skills/heading-structure .agents/skills/heading-structure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "heading-structure" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structure into .agents/skills/heading-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "heading-structure", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills heading-structure --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/accessible-content/skills/heading-structure .cursor/skills/heading-structure && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "heading-structure" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structure into .cursor/skills/heading-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "heading-structure", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path accessible-content/skills/heading-structure--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills heading-structure --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/accessible-content/skills/heading-structure .gemini/skills/heading-structure && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "heading-structure" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structure into .gemini/skills/heading-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "heading-structure", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills heading-structureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/accessible-content/skills/heading-structure .github/skills/heading-structure && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "heading-structure" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structure into .github/skills/heading-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "heading-structure", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills heading-structure --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/accessible-content/skills/heading-structure .opencode/skills/heading-structure && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "heading-structure" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structure into .opencode/skills/heading-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "heading-structure", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
heading-structure- GitHub stars
- 103
- Token cost
- ~763 tokens
- SKILL.md length
- 341 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
- Structuring headings on a new page, article or dashboard
- SKILL.md covers Why This Matters, Rules, Recommended Depth and Patterns, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Auditing a page for skipped levels or multiple H1s
What it does
Headings act as navigation for screen reader users, who jump between them, and as signposts for people with cognitive disabilities. The skill sets rules: one H1 per page that matches the page title, no skipped levels such as H1 to H3, headings that describe their content rather than carrying labels like Section 2, and heading tags used for structure while CSS handles appearance.
It recommends H1 through H3 for most pages and H4 at most for complex ones, treating a need for H5 or H6 as a sign the page should be split. Example outlines are given for articles, dashboards, forms and settings pages, and an assessment checklist covers exactly one H1, no skipped levels, descriptive headings and structural use of tags.
When your agent uses it
- Structuring headings on a new page, article or dashboard
- Auditing a page for skipped levels or multiple H1s
- Making a form's sections navigable for screen reader users
Example prompts
- “Review the heading levels on our pricing page for screen reader navigation.”
- “Outline a heading hierarchy for a settings page with profile and notification sections.”
- “Fix the pages where headings were chosen for size instead of structure.”
What it can do on your machine
Read from SKILL.md and the folder at commit 6e0740f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Accessible Heading Structure loads about 763 tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 341 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 341 words, ~763 tokens.
Download SKILL.mdSave it as
.claude/skills/heading-structure/SKILL.md (or your agent's skills folder).- name
- heading-structure
- description
- Design heading hierarchies and content structure that work for screen readers and cognitive accessibility. Use when structuring pages, articles, dashboards, forms, or any content-heavy interface. Triggers on: headings, heading hierarchy, h1 h2 h3, content structure, page structure, screen reader navigation, document outline, semantic structure, heading levels.
Heading Structure
Headings are navigation for screen reader users and cognitive signposts for everyone. A clear heading structure is the difference between content people can find and content people abandon.
Why This Matters
Screen reader users navigate by headings — they press a key to jump between headings the way sighted users scan a page visually. If your heading structure is broken, screen reader users are lost in a wall of undifferentiated text.
For people with cognitive disabilities, headings are the primary way they understand what content a page contains and where to find what they need.
Rules
One H1 Per Page
- The H1 is the page title — what this page is about
- It should match or closely relate to the page's title tag and the link that brought the user here
- Never use more than one H1 on a page
No Skipped Levels
- Go H1 → H2 → H3, never H1 → H3
- Skipping levels breaks screen reader navigation and confuses the document outline
- You can go back up: H3 → H2 is fine (starting a new section)
Headings Describe Content
- Headings are signposts, not decoration
- "Your Account Settings" not "Section 2"
- "Choose a Delivery Date" not "Step 3"
- A user should understand the page's content by reading only the headings
Headings Are Not Visual Styling
- Don't use a heading tag just to make text big or bold
- Don't skip heading tags and just style text to look like a heading
- The tag determines the structure; CSS determines the appearance
- If it looks like a heading but isn't one, screen reader users can't find it
Recommended Depth
- Most pages: H1 through H3 is sufficient
- Complex pages: H1 through H4 maximum
- If you need H5 or H6: the page is probably too complex — consider splitting it
Patterns
Article or Blog Post
H1: Article Title
H2: First Major Section
H3: Subsection
H3: Subsection
H2: Second Major Section
H3: Subsection
H2: ConclusionDashboard
H1: Dashboard Name
H2: Summary / Key Metrics
H2: Recent Activity
H2: Tasks
H2: NotificationsForm
H1: Form Title (e.g., "Apply for an Account")
H2: Personal Information
H2: Contact Details
H2: Preferences
H2: Review and SubmitSettings Page
H1: Settings
H2: Profile
H2: Notifications
H2: Privacy
H2: BillingAssessment Checklist
- Exactly one H1 per page
- No skipped heading levels
- Headings describe the content beneath them
- Heading tags are used for structure, not visual styling
- A user reading only headings would understand the page
- Heading depth does not exceed H4
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in accessible-content/skills/heading-structure of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Accessible Heading Structure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Accessible Heading Structure this skillOwl-Listener/inclusive-design-skills | 103 | — | ~763 | Automated safety check: Pass | MIT | |
| Color Auditrome-os/rome | 717 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Dont Make Me Thinkluongnv89/skills | 131 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Super UI UX Designsyahiidkamil/Software-Engineer-AI-Agent-Atlas | 397 | — | ~9k | Automated safety check: Pass | None | |
| Design Critiquegetcrew44/crew44 | 356 | — | ~691 | Automated safety check: Pass | MIT | |
| UI Automation Workflowsconorluddy/xclaude-plugin | 183 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Dont Make Me Think
luongnv89/skills
Review UI usability using Steve Krug's principles and produce a scannable report.
Super UI UX Design
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete UI/UX design capability — a wiki-style knowledge map of design theory (UX laws, Nielsen heuristics, usability, visual hierarchy, typography, contrast/WCAG, design systems…
Design Critique
getcrew44/crew44
Walks an agent through five review passes on a screen, flow or mockup, then returns ranked findings with a severity and a suggested fix for each one.
UI Automation Workflows
conorluddy/xclaude-plugin
Accessibility-first UI automation using IDB. An agent skill from conorluddy/xclaude-plugin.
Lamina UX
aryaniyaps/lamina
Design understandable and accessible product interactions. An agent skill from aryaniyaps/lamina.
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoAssistive Technology Scenarios
Owl-Listener/inclusive-design-skills
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
Error Prevention and Recovery
Owl-Listener/inclusive-design-skills
Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.
Ability Spectrum Mapping
Owl-Listener/inclusive-design-skills
Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Accessibility Testing Strategy
Owl-Listener/inclusive-design-skills
Plan what to test, how to test, and who should test for accessibility.
Alt Text Design
Owl-Listener/inclusive-design-skills
Write meaningful alternative text for images, charts, diagrams, and visual content.
Related
Categories
Questions about Accessible Heading Structure
What does Accessible Heading Structure do?
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms. Headings act as navigation for screen reader users, who jump between them, and as signposts for people with cognitive disabilities. The skill sets rules: one H1 per page that matches the page title, no skipped levels such as H1 to H3, headings that describe their content rather than carrying labels like Section 2, and heading tags used for structure while CSS handles appearance.
When should I use Accessible Heading Structure?
Accessible Heading Structure fits situations like: structuring headings on a new page, article or dashboard; auditing a page for skipped levels or multiple H1s; making a form's sections navigable for screen reader users.
How do I install Accessible Heading Structure in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a claude-code`. Or copy the skill folder (accessible-content/skills/heading-structure in Owl-Listener/inclusive-design-skills) into .claude/skills/heading-structure in your project. Claude Code loads it when a task matches its description.
How do I install Accessible Heading Structure in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a codex`. Or copy the skill folder (accessible-content/skills/heading-structure in Owl-Listener/inclusive-design-skills) into .agents/skills/heading-structure in your project. Codex loads it when a task matches its description.
Can I use Accessible Heading Structure in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/inclusive-design-skills --skill heading-structure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/heading-structure, .gemini/skills/heading-structure, .github/skills/heading-structure and .opencode/skills/heading-structure in your project.
What does Accessible Heading Structure need to run?
SKILL.md names no scripts, command-line tools or credentials: Accessible Heading Structure is instructions for the agent only.
Does Accessible Heading Structure access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Accessible Heading Structure safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Accessible Heading Structure use?
Accessible Heading Structure is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Accessible Heading Structure use?
About 763 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Accessible Heading Structure?
Skills that share tags, products or a category with Accessible Heading Structure: Color Audit (rome-os/rome, 717 stars), Dont Make Me Think (luongnv89/skills, 131 stars), Super UI UX Design (syahiidkamil/Software-Engineer-AI-Agent-Atlas, 397 stars) and Design Critique (getcrew44/crew44, 356 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Accessible Heading Structure?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 103 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.