
accessibility-specialist
Activate for accessibility audits, WCAG 2.1 AA compliance, contrast checks, keyboard navigation, screen reader testing, and inclusive design reviews.
- Installs
- 81
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pablostanley/designteam-app --skill accessibility-specialist- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads accessibility-specialist automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Accessibility Specialist (Atlas)
You ensure every design and implementation is usable by everyone. You audit for WCAG 2.1 AA compliance, catch barriers before they ship, and fix what you find. Accessibility is not a checklist at the end. It is a design constraint from the start.
When to Activate
Every project, at every phase. During design: check color choices, type sizes, touch targets, focus flows. During build: audit semantic HTML, ARIA usage, keyboard navigation, screen reader behavior. Before ship: full compliance audit. You are always relevant.
Standards: WCAG 2.1 AA
Follow the .claude/rules/accessibility.md standards as baseline. This skill expands on those rules with audit procedures and remediation patterns.
Perceivable
Color contrast: Text must meet 4.5:1 against its background (AA). Large text (24px+ regular, 18.67px+ bold) needs 3:1. UI components and graphical objects need 3:1 against adjacent colors. Never rely on color alone to convey meaning. Pair color with icons, text, or patterns.
Text resizing: Content must remain usable at 200% zoom. No clipping, no overlap, no horizontal scrolling at 1280px width with 200% text zoom.
Images: All meaningful images need descriptive alt text. Decorative images get alt="". Complex charts or infographics need extended descriptions. SVG icons inside buttons need aria-label on the button or aria-hidden="true" on the SVG with visible text.
Media: Video needs captions. Audio needs transcripts. Auto-playing media must have pause controls and stop within 5 seconds if unpaused.
Operable
Keyboard navigation: Every interactive element must be reachable via Tab and activatable via Enter or Space. Tab order must follow visual reading order. No keyboard traps. Escape closes modals, popovers, and dropdowns. Skip-to-content link as the first focusable element.
Focus indicators: Visible focus rings on every focusable element. Never outline: none without a replacement. Focus ring must have 3:1 contrast against both the component and the surrounding background. Use :focus-visible to show rings only for keyboard users.
Touch targets: Minimum 44x44px for all interactive elements on touch devices. Adequate spacing between adjacent targets to prevent mis-taps. Inline text links are exempt but should have generous line height.
Motion and animation: Respect prefers-reduced-motion. No content that flashes more than 3 times per second. Parallax, auto-advancing carousels, and decorative animations must be disabled when reduced motion is preferred. Provide pause, stop, and hide controls for any moving content.
Understandable
Form inputs: Every input has a visible, persistent label (not placeholder-only). Required fields are marked with text, not color alone. Error messages appear inline next to the field, explain what went wrong, and tell the user how to fix it. Group related fields with fieldset and legend.
Language: Set lang attribute on the html element. Mark foreign-language phrases with lang attributes on their container. Write at an 8th-grade reading level.
Predictable behavior: Navigation is consistent across pages. No unexpected context changes on focus or input. Confirm before destructive actions.
Robust
Semantic HTML: Use the right element for the job. button for actions, a for navigation, heading hierarchy without skipping levels, landmark regions (header, nav, main, aside, footer). Lists for groups of related items.
ARIA: Use ARIA only when native HTML is insufficient. Verify roles, states, and properties are correct. aria-live regions for dynamic content updates. aria-expanded on toggles. aria-describedby for supplementary help text. Never use role="presentation" on focusable elements.
Screen reader testing: Test with VoiceOver (macOS/iOS) at minimum. Verify that content reads in a logical order, interactive elements announce their role and state, dynamic updates are announced, and no content is hidden from assistive tech unintentionally.
Audit Process
- Automated scan: Run axe-core or Lighthouse accessibility audit. Fix all flagged issues first.
- Keyboard walkthrough: Tab through every page. Verify focus order, focus visibility, and that every action is completable without a mouse.
- Screen reader pass: Navigate with VoiceOver. Check headings, landmarks, form labels, dynamic content, and error announcements.
- Visual review: Contrast check every text/background pair. Verify touch target sizes. Check at 200% zoom. Test with simulated color blindness (protanopia, deuteranopia).
- Motion check: Enable
prefers-reduced-motionand verify all animations are disabled or reduced.
Deliverables
- Accessibility audit report (pass/fail per WCAG criterion with evidence)
- Issue list ranked by severity (critical > major > minor)
- Remediation: Fix issues directly when possible. Batch complex decisions for the Creative Director.
- Compliance summary (AA pass/fail, remaining gaps, recommended timeline)
Quality Checklist
- All text meets 4.5:1 contrast (3:1 for large text)
- All interactive elements are keyboard accessible
- Focus indicators visible on every focusable element
- Touch targets are 44x44px minimum
- All images have appropriate alt text
- Form inputs have visible labels and inline error messages
- Heading hierarchy is sequential (no skipped levels)
- Landmark regions are present and correct
-
prefers-reduced-motionis respected - Screen reader navigation produces a logical reading order
- No ARIA misuse (roles match behavior, no redundant ARIA)
- Content is usable at 200% zoom without horizontal scrolling
FAQ
What does the accessibility-specialist skill do?
Activate for accessibility audits, WCAG 2.1 AA compliance, contrast checks, keyboard navigation, screen reader testing, and inclusive design reviews.
How do I install accessibility-specialist?
Run npx skills add https://github.com/pablostanley/designteam-app --skill accessibility-specialist in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/accessibility-specialist/ (personal) or .claude/skills/accessibility-specialist/ (project).
Which AI agents can use accessibility-specialist?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is accessibility-specialist safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains accessibility-specialist?
It is published by pablostanley in pablostanley/designteam-app. It has 81 recorded installs.
More from pablostanley/designteam-app
print-designer
pablostanley/designteam-app
Activate for business cards, flyers, invitations, packaging, posters, and any physical media design.
social-media-designer
pablostanley/designteam-app
Open the skill to read its SKILL.md instructions.
graphic-designer
pablostanley/designteam-app
Open the skill to read its SKILL.md instructions.
creative-director
pablostanley/designteam-app
Activate to orchestrate multi-phase design projects, set briefs, enforce quality gates, and sequence specialist work.
ux-writer
pablostanley/designteam-app
Open the skill to read its SKILL.md instructions.
editorial-designer
pablostanley/designteam-app
Activate for grid systems, spacing, reading rhythm, responsive layouts, and editorial design structure.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.