Skip to main content
skill CX Codex

accessibility · evanca — Claude Code skill: what it does, how to install

This skill walks an interface through a WCAG checklist — keyboard, screen reader, contrast, forms — and flags concrete accessibility gaps. It triggers on a11y, ARIA, alt text, focus order, contrast.

MIT ★ 674 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add evanca/flutter-ai-rules
/plugin install flutter-ai-skills@flutter-ai-rules
Open on GitHub

What accessibility does

The skill runs one test on every UI element: could someone finish the task without sight, without a mouse, or without reading quickly? A failure on any of those points to one of four WCAG principles — whether content can be perceived, operated, understood, or parsed correctly by assistive software.

The audit covers eight areas: keyboard flow and visible focus, names and roles that a screen reader announces, contrast and color used as the only signal, semantic headings and form structure, error messages tied to their field, tap target size, captions and support for prefers-reduced-motion, and layout behavior at 200% zoom. Two linked files, references/cognitive-accessibility.md and references/motion-and-sensory.md, add patterns for cognitive load and motion sensitivity.

Language, culture, and device type sit outside its scope; the same repository ships a separate inclusive-design skill for that, and the author keeps the two deliberately apart so neither loses focus.

What it helps with

  • audit an interface against WCAG checkpoints
  • check keyboard navigation and focus visibility
  • catch forms missing field labels or clear error text
  • check contrast and color-only meaning
  • add prefers-reduced-motion support and captions

Example prompts for the agent

  • Audit this form against WCAG accessibility criteria
  • Run an accessibility pass on this screen: keyboard, screen reader, contrast
  • Check this page for focus order and ARIA issues

How to install accessibility

1Plugin marketplace

/plugin marketplace add evanca/flutter-ai-rules
/plugin install flutter-ai-skills@flutter-ai-rules

This installs the whole flutter-ai-skills plugin with all its skills

2Skills CLI (Vercel)

npx skills add evanca/flutter-ai-rules --skill accessibility -a claude-code

3Manually: put the files in place

~/.claude/skills/accessibility/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/accessibility/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about accessibility

How do I install accessibility in Claude Code?

Run /plugin marketplace add evanca/flutter-ai-rules, then /plugin install flutter-ai-skills@flutter-ai-rules.

What does accessibility do?

It checks an interface against the four WCAG principles — what can be perceived, operated, understood, and correctly read by assistive tools — and points to specific gaps, from missing alt text to weak contrast.

How is accessibility different from inclusive-design?

Accessibility covers ability-based use — screen readers, keyboard input, contrast; inclusive-design covers context — language, culture, device, user confidence. Both skills live in the same repository but stay deliberately separate.

Source text

SKILL.md · MIT
---
name: accessibility
description: "Use when working on accessibility, a11y, WCAG, ARIA, screen readers, keyboard nav, focus order, contrast, alt text, captions, reduced motion, or target sizes; not language/culture/device (see inclusive-design)."
license: MIT
---

# Accessibility

Accessibility answers one question:

> **Can someone use this with assistive tools, a different input method, or a different ability?**

It is specifically about people with disabilities being able to **perceive, understand, navigate, and interact** with a product on equal terms — whether they use a screen reader, only a keyboard, a switch, voice control, magnification, or captions. This is the *ability* half of designing for everyone. The *context* half — language, culture, device, affordability, confidence — belongs to the sibling **inclusive-design** skill. They overlap but have different focuses; keep them distinct so neither gets diluted.

## When to use

Use this skill when the task involves any of: WCAG conformance, ARIA, semantic markup, screen-reader support, keyboard/focus management, color contrast, text alternatives (alt text, captions, transcripts), accessible forms and error messages, target sizes, timing/timeouts, motion sensitivity, or cognitive accessibility. Also use it whenever someone asks to "make this accessible," run an a11y audit, or check whether a disabled user can complete a task.

**When *not* to use it:** if the real concern is who gets *left out* by context — non-English speakers, people on cheap phones or slow networks, people who can't afford data, first-time or anxious users, or global name/address formats — that is inclusion, not accessibility. Switch to the **inclusive-design** skill.

## The mental model: POUR

WCAG organizes all of accessibility under four principles. Use them as your audit lens — every issue you find maps to one of them.

- **Perceivable** — users can sense the content through *some* channel. Don't rely on one sense alone. (Text alternatives for images, captions/transcripts for audio and video, sufficient color contrast, not using color alone to convey meaning, content that reflows and survives zoom.)
- **Operable** — users can drive the interface with *whatever input they have*. (Everything reachable and usable by keyboard, visible focus, no keyboard traps, adequate target sizes, generous or adjustable time limits, nothing that flashes in a seizure-inducing way.)
- **Understandable** — users can predict and comprehend behavior. (Clear labels, instructions, and error messages; consistent navigation; predictable interactions; readable language.)
- **Robust** — assistive tech can actually parse it. (Valid semantic structure; correct name/role/value on every control; native semantics first, ARIA only to fill gaps.)

A useful test for any element: *if I could not see it, hear it, use a mouse, or read quickly — could I still complete this task?* If the answer is no under any of those, you've found the principle that's failing.

## Who and what you are designing for

Design for the assistive tools and input methods people actually use, not an abstract "disabled user":

- **Screen readers** (VoiceOver, TalkBack, NVDA, JAWS) — need correct semantics, reading order, labels, and announcements of dynamic changes.
- **Keyboard-only and switch users** — need a logical focus order, visible focus, and no mouse-only interactions.
- **Voice control** — needs visible, speakable labels that match the accessible name.
- **Screen magnification and zoom** — needs layouts that reflow without horizontal scrolling or clipping at 200%+.
- **Captions / transcripts users** — Deaf and hard-of-hearing users, *and* anyone in a loud or silent environment.
- **People with cognitive and learning disabilities** — need clear language, low memory load, and forgiving flows (see below).

Note the recurring pattern: most of these help far more people than the group they target — the same insight that drives inclusive design.

## Fast audit checklist

Walk these in order; each line is a concrete thing to check or fix.

1. **Keyboard** — Tab through the whole flow. Is every control reachable and operable? Is focus visible? Is the order logical? Can you get trapped?
2. **Screen reader** — Does every control announce a meaningful name and role? Are images given text alternatives (or marked decorative)? Are dynamic updates (errors, loading, toasts) announced?
3. **Contrast & color** — Does text meet contrast minimums (4.5:1 body, 3:1 large)? Is any meaning carried by color alone (e.g., red = error with no icon/text)?
4. **Structure** — Are headings, lists, landmarks/regions, and labels semantic rather than visual-only? Does reading order match visual order?
5. **Forms & errors** — Is every field labeled (not placeholder-only)? Are errors identified in text, tied to their field, and explained with how to fix?
6. **Targets & timing** — Are tap targets large enough and spaced? Are time limits absent, generous, or adjustable? Is autosave used to prevent data loss?
7. **Media & motion** — Captions/transcripts for audio/video? Does the UI honor reduced-motion preferences? Nothing flashing more than ~3×/second?
8. **Zoom/reflow** — At 200% zoom (or large system font), does content reflow without clipping or horizontal scroll?

## Beyond conformance: cognitive accessibility

WCAG alone does not cover everything people with cognitive and learning disabilities (dyslexia, ADHD, autism, dementia, aphasia, memory or attention differences) need. The W3C COGA guidance is **supplemental, not required for WCAG conformance**, and it is where the highest-leverage improvements for the largest hidden population usually live: clear language, consistent design, single-step instructions, not relying on memory, forgiving error recovery, and minimizing distraction.

Read **[references/cognitive-accessibility.md](references/cognitive-accessibility.md)** for COGA's eight objectives and their concrete design patterns when the task touches readability, complex flows, forms, logins, or "this is confusing/overwhelming."

## Motion, sensory, and age-related needs

Animation and motion can cause real harm (nausea, dizziness, loss of focus) for people with vestibular disorders, and seizures for people with photosensitivity. Honor the user's `prefers-reduced-motion` setting — reduce or replace motion rather than removing all feedback.

Older users are a large group whose age-related changes in vision, dexterity, hearing, and memory overlap directly with disability needs — designing well here helps everyone age into your product. (Treat *age as a context/identity dimension* — first-time confidence, life stage — in the inclusive-design skill; treat *age-related ability change* here.)

Read **[references/motion-and-sensory.md](references/motion-and-sensory.md)** for `prefers-reduced-motion` patterns (with code), photosensitivity limits, and the older-user ability overlap.

## How to verify

Automated checkers (axe, Lighthouse, Accessibility Scanner, etc.) catch maybe a third of issues — necessary but never sufficient. Always add manual checks: navigate the real flow with the keyboard only, then again with a screen reader, then with the OS reduced-motion and large-text settings on. The bug a tool can't catch — a focus order that makes no sense, a label that lies — is usually the one that actually blocks someone.

## References

Load these only when the task calls for the depth:

- [references/cognitive-accessibility.md](references/cognitive-accessibility.md) — W3C COGA: the 8 objectives and their design patterns (beyond WCAG).
- [references/motion-and-sensory.md](references/motion-and-sensory.md) — reduced motion (with CSS example), photosensitivity, older-user ability overlap.

Primary sources:

- [Accessibility, Usability, and Inclusion — W3C WAI](https://www.w3.org/WAI/fundamentals/accessibility-usability-inclusion/)
- [Making Content Usable for People with Cognitive and Learning Disabilities (COGA) — W3C](https://www.w3.org/TR/coga-usable/)
- [Older Users and Web Accessibility — W3C WAI](https://www.w3.org/WAI/older-users/)
- [prefers-reduced-motion — MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion)

© Ivanna Kaceviča · MIT · evanca/flutter-ai-rules

Similar skills

All skills for Frontend and UI →

accessibility by other authors comes first.

accessibility web-quality-skills This skill audits a rendered page for accessibility and points to the components behind each failure. Useful when a site has to meet WCAG 2.2 or survive a keyboard and screen reader pass. CX Codex +1 72,600installs accessibility affaan-m accessibility is a Claude Code skill for building and auditing interfaces against WCAG 2.2 Level AA. It applies to UI work involving keyboard navigation or screen-reader support. CX Codex +1 6,900installs accessibility OrchestKit accessibility — a Claude Code skill for building accessible web interfaces. It activates for work on screen reader support, keyboard navigation, focus handling, and ARIA components. CX Codex +1 246installs accessibility oakoss accessibility is a Claude Code skill for building and reviewing web interfaces against WCAG 2.2 AA, including semantic HTML, keyboard use, focus handling, and screen reader support. CX Codex +1 164installs accessibility microsoft A reference hub for WCAG 2.2, ARIA APG, Section 508 and EN 301 549 that also drives a six-phase Accessibility Planner from discovery to backlog handoff. CX Codex +1 ★ 1,627repo stars tailwindcss-accessibility JosiahSiegel tailwindcss-accessibility is a Claude Code skill for building accessible interfaces with Tailwind CSS. It activates for WCAG work, focus styling, contrast, and ARIA patterns. CX Codex +1 302installs accessibility-compliance aj-geddes The accessibility-compliance skill guides accessibility work for WCAG 2.1/2.2, keyboard navigation, screen readers and a11y checks in web interfaces. CX Codex +1 490installs accessibility-auditor OneWave-AI accessibility-auditor audits web pages for accessibility defects and guides compliance with WCAG 2.1 AA. It runs automated checks, inspects keyboard navigation, and suggests markup fixes. CX Codex +1 346installs accessibility-a11y travisjneuman accessibility-a11y — a skill for Claude Code and Codex guides WCAG 2.2 compliance and interface accessibility checks. Activates during UI component development, accessibility reviews, or CI/CD test integration. CX Codex +1 161installs accessibility-agents Community Access (Jeff Bishop and Taylor Arndt) The accessibility-agents GitHub Copilot plugin routes accessibility work to specialist skills. It checks interfaces and documents against WCAG 2.2 AA and blocks edits to user-facing files until review. ★ 453repo stars a11y-audit plugin87 a11y-audit — a skill for Claude Code that inspects user interfaces against WCAG 2.2 AA/AAA criteria and ARIA patterns. Runs when testing contrast, keyboard navigation, or screen-reader tags. CX Codex +1 641installs

From the same set39

The whole set →
inclusive-design inclusive-design guides agent workflows on low-end hardware, metered 2G connections, global name formats, and novice stress. Distinct from WCAG audits. CX Codex +1 ★ 674repo stars firebase-database The firebase-database skill guides Flutter work with Firebase Realtime Database, from JSON structure and queries to live updates, offline support, and access rules. CX Codex +1 ★ 674repo stars dart-3-updates dart-3-updates — a skill for Claude Code and Codex that teaches the AI to write switch expressions, patterns, records, and modern Dart instead of old if-else chains. Helps when refactoring to Dart 3 and choosing between records and classes. CX Codex +1 ★ 674repo stars effective-dart effective-dart guides AI agents to produce idiomatic Dart and Flutter code following official style, naming, and typing conventions. CX Codex +1 ★ 674repo stars firebase-cloud-firestore The firebase-cloud-firestore skill guides an agent through setting up Cloud Firestore in a Flutter app: schema design, queries, real-time listeners and security rules. CX Codex +1 ★ 674repo stars generate-images-with-firebase-ai generate-images-with-firebase-ai guides image generation and editing in Flutter via Firebase AI Logic and Gemini, troubleshooting quota errors, App Check, and blank responses. CX Codex +1 ★ 674repo stars code-review code-review reviews Flutter and Dart changes against a structured checklist, including tests, security, and code quality. Use it before merging a PR or branch. CX Codex +1 ★ 674repo stars bloc A Flutter skill for building Cubits and Blocs, choosing how state is modelled, and wiring bloc widgets into the tree. Useful when state management in a project needs one consistent shape. CX Codex +1 ★ 674repo stars

Project sponsors

Companies that keep this analytics open