Help us improve
Share bugs, ideas, or general feedback.
From accessible-content
Builds content structure that assistive technology can parse and navigate. Covers heading hierarchy, landmarks, alt text, table/forms specs, and reading order.
npx claudepluginhub owl-listener/inclusive-design-skills --plugin accessible-contentHow this skill is triggered — by the user, by Claude, or both
Slash command
/accessible-content:structureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build content structure that assistive technology can parse, navigate,
Guides creation of accessible user-facing content including labels, headings, error messages, alt text, links, and form instructions for screen reader compatibility and clarity.
Guides designing accessible heading hierarchies (H1-H6) for screen readers and cognitive accessibility. Use when structuring pages, articles, dashboards, or forms.
Guides building and reviewing web page HTML structure with proper heading hierarchy, landmark regions, and semantic elements for screen reader accessibility.
Share bugs, ideas, or general feedback.
Build content structure that assistive technology can parse, navigate, and present meaningfully — so the structure you designed is the structure every user experiences.
Using heading-structure, design the heading hierarchy:
Map the page regions that assistive technology uses for navigation:
Every page should have at minimum: banner, navigation, main, contentinfo.
Using alt-text-design, assign alt text strategy for every image:
Using table-accessibility, for every table:
Using form-labelling, for every form:
Deliver a structural specification that includes: