Accessibility

Accessibility

Checks keyboard navigation, screen-reader semantics, colour contrast and focus handling across any interface.

What it does

Checks keyboard navigation, screen-reader semantics, colour contrast and focus handling across any interface.

When to use it

Use as a default check on any UI-building task, not only when accessibility is explicitly requested.

Problems it prevents

Stops interfaces that look complete but are unusable without a mouse, or invisible to a screen reader.

Typical workflow

  1. Start from semantic HTML
  2. Verify full keyboard reachability
  3. Check screen-reader announcements
  4. Test colour contrast and motion

Example output

A UI that passes a real keyboard-only and screen-reader pass, not just an automated contrast checker.

What's included

  1. 01
    The complete prompt

    The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

  2. 02
    Install walkthrough

    Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

  3. 03
    Use notes

    How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Installation

Save the manual as SKILL.md in ~/.claude/skills/accessibility/ to use it on every project, or in .claude/skills/accessibility/ to scope it to one repository. Then invoke it directly:

/accessibility

Read the official Claude Code skills guide

Works well with