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

structure

/structure

Structure content for screen reader and assistive technology use. Chains: heading-structure, alt-text-design, table-accessibility, form-labelling. Use when building a new page, document, or content template and you want to get the structural accessibility right from the start.

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

Structure content for screen reader and assistive technology use. Chains: heading-structure, alt-text-design, table-accessibility, form-labelling. Use when building a new page, document, or content template and you want to get the structural accessibility right from the start.

Original author description

Structure content for screen reader and assistive technology use. Chains: heading-structure, alt-text-design, table-accessibility, form-labelling. Use when building a new page, document, or content template and you want to get the structural accessibility right from the start.

How it works

  1. Process
  2. Output
Original SKILL.md headings · 64 lines, 330 words
SKILL.md preview
---
name: structure
description: "Structure content for screen reader and assistive technology use. Chains: heading-structure, alt-text-design, table-accessibility, form-labelling. Use when building a new page, document, or content template and you want to get the structural accessibility right from the start."
---

# Structure for Assistive Technology

Build content structure that assistive technology can parse, navigate,
and present meaningfully — so the structure you designed is the
structure every user experiences.

## Process

### Step 1: Define the Document Outline
Using **heading-structure**, design the heading hierarchy:
- One H1 describing the page purpose
- H2s for major sections
- H3s for subsections within those
- Verify: does reading only the headings tell the full story?

### Step 2: Identify Landmarks
Map the page regions that assistive technology uses for navigation:
- banner — site header and branding
- navigation — primary and secondary nav
- main — the primary content area
- complementary — sidebars and related content
- contentinfo — footer
- search — search functionality
- form — significant forms (use aria-label to distinguish multiples)

Every page should have at minimum: banner, navigation, main, contentinfo.

### Step 3: Structure Images and Media
Using **alt-text-design**, assign alt text strategy for every image:
- Decorative: empty alt
- Functional: alt describes the action
- Informative: alt describes the information
- Complex: short alt plus extended description

### Step 4: Structure Data
Using **table-accessibility**, for every table:
- Assign headers with proper scope
- Add caption describing the table's content
- Plan responsive behaviour for small screens

### Step 5: Structure Forms
Using **form-labelling**, for every form:
- Associate every input with a visible label
- Group related fields with fieldset/legend
- Plan error message association
- Define required field indication strategy

### Step 6: Define Reading Order
- Verify that the DOM order matches the visual order
- Content should make sense when read linearly top to bottom
- Avoid CSS that visually rearranges content away from DOM order
- Tab order should follow reading order

## Output

Deliver a structural specification that includes:
- Document outline (heading hierarchy)
- Landmark map
- Image alt text strategy per image type
- Table structure specification
- Form labelling specification
- Reading order confirmation

Versions

RepositoryScoreLicence
This page · owl-listener/inclusive-design-skills90MIT
alirezarezvani/gaios100MIT
zengtianli/cc-configs96MIT
melodic-software/claude-code-plugins84MIT

Database snapshot: 13.11.2026 · package version 0b655dcaf24a (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

  • 100heading-structure
    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…
  • 90review
    Review content for accessibility across cognitive and literacy levels. Chains: readable-content, alt-text-design, heading-structure, link-text-design, table-accessibility, form-labelling, multimedia-accessibility. Use when auditing existing content for accessibility.
  • 100screen-reader-testing
    Use when performing accessibility audits of web pages, components, or full user flows. Applies to all web content accessed via assistive technology. Particularly important for custom JavaScript widgets, single-page applications, dynamically updated content, modal dialogs, and forms with validation.
  • 100include
    Design for everyone by treating accessibility as a first-class design discipline, not a compliance checklist. Part of the Intent design strategy system. Covers WCAG 2.2 for designers, screen reader experience design, keyboard navigation, cognitive accessibility, motor…
  • 100frontend-a11y
    Accessibility patterns for React and Next.js — semantic HTML, ARIA attributes, form labeling, keyboard navigation, focus management, and screen reader support. Use when building any interactive UI component or form.
  • 100accessible-content
    Use when writing or structuring any user-facing content — interface copy, labels, error messages, help text, headings, alt text, link text, or form instructions — ensures content is readable, navigable, and meaningful for everyone

Feedback and reports

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