Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
pablostanley avatar

Accessibility Specialist

  • 53 installs
  • 13 repo stars
  • Updated April 19, 2026
  • pablostanley/designteam-app

Accessibility Specialist is a Design Team agent skill that audits designs and markup for WCAG 2.1 AA so teams can catch barriers in contrast, keyboard access, and assistive-tech support.

About

Accessibility Specialist is a Design Team skill that audits interfaces for WCAG 2.1 AA across design and code, from contrast and keyboard paths to ARIA and motion preferences. Developers invoke it before shipping customer-facing UI or when fixing inclusive design gaps found in implementation. It expands repository accessibility rules with concrete audit and remediation procedures.

  • WCAG 2.1 AA perceivable, operable, understandable, robust checks
  • Keyboard, focus-visible, and 44px touch target requirements
  • Pairs with .claude/rules/accessibility.md baseline rules
  • Screen reader and reduced-motion considerations included

Accessibility Specialist by the numbers

  • 53 all-time installs (skills.sh)
  • +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #1,232 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pablostanley/designteam-app --skill accessibility-specialist

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs53
repo stars13
Last updatedApril 19, 2026
Repositorypablostanley/designteam-app

How do you systematically find and fix accessibility barriers before users encounter unusable contrast, focus, or screen reader issues?

Run WCAG 2.1 AA audits on designs and implementations covering contrast, keyboard flows, ARIA, focus, motion, and remediation guidance.

Who is it for?

Developers shipping web or product UI who need structured WCAG audits and remediation patterns across design and code.

Skip if: Teams seeking only visual brand exploration with no compliance requirements or native-only apps outside the skill's web-focused checks.

When should I use this skill?

You need an accessibility audit during design choices, implementation, or a final pre-release compliance pass.

What you get

Issue lists tied to WCAG criteria plus remediation guidance for contrast, semantics, keyboard, focus, and motion settings.

Files

SKILL.mdMarkdownGitHub ↗

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

1. Automated scan: Run axe-core or Lighthouse accessibility audit. Fix all flagged issues first. 2. Keyboard walkthrough: Tab through every page. Verify focus order, focus visibility, and that every action is completable without a mouse. 3. Screen reader pass: Navigate with VoiceOver. Check headings, landmarks, form labels, dynamic content, and error announcements. 4. Visual review: Contrast check every text/background pair. Verify touch target sizes. Check at 200% zoom. Test with simulated color blindness (protanopia, deuteranopia). 5. Motion check: Enable prefers-reduced-motion and verify all animations are disabled or reduced.

Deliverables

1. Accessibility audit report (pass/fail per WCAG criterion with evidence) 2. Issue list ranked by severity (critical > major > minor) 3. Remediation: Fix issues directly when possible. Batch complex decisions for the Creative Director. 4. 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-motion is 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

Related skills

FAQ

Which standard does the skill target?

SKILL.md centers WCAG 2.1 AA and references .claude/rules/accessibility.md as the baseline.

What contrast ratios are required?

Normal text needs 4.5:1, large text 3:1, and UI components 3:1 against adjacent colors per the skill.

When is the skill relevant?

It states every project at every phase, with emphasis on design choices, build-time markup, and a full audit before ship.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.