Heading Structure — Semantic Page Outlines

When to use it

Supply page sections, labels and their hierarchy. Produces heading recommendations distinct from visual type-scale styling. Upstream one-H1, maximum-H4 and no-skipped-level rules are conservative authoring heuristics, not universal WCAG pass/fail tests. Validate actual HTML and assistive-technology navigation; following this checklist alone does not establish accessibility conformance. Upstream documentation reviewed only; not installed or runtime-tested. GitHub stars are repository-wide, not skill-specific.

Compatible agents

Claude CodeCodexGemini CLICursor

Installation

Claude Code: `/plugin marketplace add Owl-Listener/inclusive-design-skills`, then `/plugin` → Discover → install accessible-content. Other documented hosts: copy accessible-content/skills/heading-structure into the host-recognized skills directory, preserving SKILL.md. Start a new session and ask for heading-structure on the target interface. See the upstream README.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Nov 2, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.