Building Accessible Interfaces

Makes web and app UIs usable by keyboard, screen-reader, low-vision and motion-sensitive users — semantic HTML before ARIA, labelled controls, visible focus, WCAG AA contrast measured rather than eyeballed, touch targets, reduced motion, and automated axe checks plus a manual keyboard pass in CI or before every UI PR. Use when building or restyling a screen, adding a form, modal, menu or custom control, choosing colors, or reviewing a UI change.

115 stars 18 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add wdm0006/python-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add wdm0006/python-skills --skill building-accessible-interfaces
Manual install
git clone --depth 1 https://github.com/wdm0006/python-skills.git /tmp/python-skills
mkdir -p ~/.claude/skills
cp -r /tmp/python-skills/skills/common/accessible-interfaces ~/.claude/skills/building-accessible-interfaces

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Building Accessible Interfaces

Accessibility failures are concentrated in a few places: custom controls built from
`div`s, inputs without labels, invisible focus, low-contrast "subtle" text, and
modals that trap nothing or everything. Check those first; they cover most real
users' problems and most automated findings.

## Contents
- Step 1 — Semantic HTML first
- Step 2 — Every control has a name
- Step 3 — Keyboard and focus
- Step 4 — Contrast, measured
- Step 5 — Motion, zoom and touch
- Step 6 — Automated checks plus a manual pass
- Native apps
- Anti-patterns

## Step 1 — Semantic HTML first

The right element gives keyboard support, focus and screen-reader semantics for free.

| Need | Use | Not |
|------|-----|-----|
| Action | `<button type="button">` | `<div onclick>`, `<a href="#">` |
| Navigation | `<a href="/path">` | `<button onclick="location=…">` |
| Page regions | `<header> <nav> <main> <footer>` | anonymous `div`s |
| Headings | one `<h1>`, then `<h2>`… in order | bold `div`s, skipped levels |
| Lists | `<ul>/<ol>` | stacked `div`s |
| Data | `<table>` with `<th scope>` | grids of `div`s |
| Toggle | `<input type="checkbox">` / `<button aria-pressed>` | a styled `span` |

ARIA is for the gaps HTML cannot fill (tabs, comboboxes, live regions). "No ARIA is
better than bad ARIA": a wrong `role` actively misinforms assistive tech.

## Step 2 — Every control has a name

- Inputs: a visible `<label for>`; placeholder text is not a label (it disappears and
Read the full skill on GitHub

Details

Skill name
building-accessible-interfaces
Path
skills/common/accessible-interfaces/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Building Accessible Interfaces skill do?

Makes web and app UIs usable by keyboard, screen-reader, low-vision and motion-sensitive users — semantic HTML before ARIA, labelled controls, visible focus, WCAG AA contrast measured rather than eyeballed, touch targets, reduced motion, and automated axe checks plus a manual keyboard pass in CI or before every UI PR. Use when building or restyling a screen, adding a form, modal, menu or custom control, choosing colors, or reviewing a UI change.

How do I install the Building Accessible Interfaces skill?

Claude Code plugin: /plugin marketplace add wdm0006/python-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Building Accessible Interfaces popular?

It lives in wdm0006/python-skills, which has 115 GitHub stars and 18 forks.

Related skills

Auditing Python Security

115

wdm0006/python-skills

Audits Python libraries for security vulnerabilities using Bandit, pip-audit, Semgrep, and detect-secrets. Identifies SQL injection, command injection, hardcoded credentials, secrets exposed through tracebacks, weak cryptography, and insecure deserialization. Use when reviewing library security, setting up security scanning in CI, or implementing secure coding patterns.

Security18

Building Browser Extensions

115

wdm0006/python-skills

Builds and tests Manifest V3 browser extensions — service-worker message channels that survive teardown, chrome.storage read-modify-write safety, settings validation in the popup, and a Jest chrome mock that can actually fail. Use when writing or reviewing a background service worker, a popup that reads/writes chrome.storage, an extension's Jest suite, or debugging an extension whose UI silently stops responding.

Software Development18

Building Go Projects

115

wdm0006/python-skills

Sets up and maintains Go projects with a CI gate that actually gates — module-path correctness, golangci-lint config that matches the installed major version, deterministic gofmt, a pinned toolchain, and meaningful test/lint jobs. Use when creating a Go module, wiring GitHub Actions for Go, debugging a golangci-lint or gofmt CI failure on an unrelated PR, or reviewing a Go CLI that shells out to git/gh.

Software Development18

Designing Interaction States

115

wdm0006/python-skills

Designs the states screens actually spend their time in — first-run and empty states, loading and skeletons, inline validation and error messages, success feedback, destructive confirmations, and the microcopy for each — so a product feels finished instead of only working on the happy path. Use when building a form, list, dashboard, upload, checkout or settings screen, adding an async action, writing error or empty-state copy, or reviewing a UI that shows blank pages, raw errors or spinners forever.

Frontend & Design18

New Project

75

sneg55/agent-starter

Full project bootstrap - interviews the developer (name, description, stack, components), then scaffolds directory structure, CLAUDE.md, config files, hooks, skills, and first commit.

Frontend & DesignIn 1 list

Designing Interfaces

115

wdm0006/python-skills

Makes a product's UI look deliberate and current instead of dated or improvised — auditing a screen against hierarchy, type scale, spacing scale, color tokens, layout and component consistency; introducing design tokens before restyling anything; and verifying every change visually with before/after screenshots. Use when building or restyling any web or app screen, reviewing a UI that looks old, cluttered or inconsistent, starting a design system for an existing app, or planning a design-improvement issue.

Frontend & Design18

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.