AugmentClaude

Accessibility Patterns

Build WCAG 2.2 AA compliant interfaces with ARIA patterns and keyboard navigation.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/accessibility-patterns-vibeeval/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Works for every skill.

    What this command does
    1. Makes a new, empty temporary folder.
    2. Downloads the skill's folder, skills/accessibility-patterns, from github.com/vibeeval/vibecosystem (branch main), the GitHub repository it's listed from. You get the version that is there now, not a copy we keep.
    3. Copies that folder to ~/.claude/skills/accessibility-patterns-vibeeval/.
    4. Deletes the temporary folder.

    Installing runs none of the skill's files; it only downloads and copies them. When you later use the skill, Claude follows its SKILL.md and may run scripts that come with it. Read them first.

    How we check skills, and what we don't · Report this skill

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

WCAG 2.2 AA compliance, ARIA patterns, keyboard navigation, screen reader optimization

What this skill does

Accessibility Patterns

WCAG 2.2 AA Requirements

Perceivable

KriterKuralKontrol
1.1.1Non-text content alt text<img alt="description">
1.3.1Semantic HTMLHeadings, landmarks, lists
1.4.3Color contrast4.5:1 normal text, 3:1 large
1.4.11UI component contrast3:1 borders, icons

Operable

KriterKuralKontrol
2.1.1Keyboard accessibleTab, Enter, Space, Escape
2.4.3Focus orderLogical tab sequence
2.4.7Focus visibleVisible focus indicator
2.5.8Target sizeMin 24x24px (44x44px önerilir)

Understandable

KriterKuralKontrol
3.1.1Language of page<html lang="tr">
3.2.1On focusNo unexpected context change
3.3.1Error identificationClear error messages
3.3.2Labels or instructionsForm labels visible

ARIA Patterns

<!-- Dialog -->
<div role="dialog" aria-modal="true" aria-labelledby="title">
  <h2 id="title">Confirm</h2>
  <button aria-label="Close dialog">×</button>
</div>

<!-- Tabs -->
<div role="tablist">
  <button role="tab" aria-selected="true" aria-controls="panel1">Tab 1</button>
  <button role="tab" aria-selected="false" aria-controls="panel2">Tab 2</button>
</div>
<div role="tabpanel" id="panel1">Content 1</div>

<!-- Live region (dynamic updates) -->
<div aria-live="polite" aria-atomic="true">
  3 new messages
</div>

Keyboard Navigation

// Focus trap (modal/dialog)
function useFocusTrap(ref: RefObject<HTMLElement>) {
  useEffect(() => {
    const focusable = ref.current?.querySelectorAll(
      'button, [href], input, select, textarea, [tabindex]:not([tabindex="-1"])'
    )
    const first = focusable?.[0] as HTMLElement
    const last = focusable?.[focusable.length - 1] as HTMLElement

    function handleKeyDown(e: KeyboardEvent) {
      if (e.key !== 'Tab') return
      if (e.shiftKey && document.activeElement === first) {
        e.preventDefault(); last.focus()
      } else if (!e.shiftKey && document.activeElement === last) {
        e.preventDefault(); first.focus()
      }
    }
    ref.current?.addEventListener('keydown', handleKeyDown)
    first?.focus()
    return () => ref.current?.removeEventListener('keydown', handleKeyDown)
  }, [ref])
}

Skip Links

<a href="#main-content" class="skip-link">Skip to main content</a>
<!-- ... navigation ... -->
<main id="main-content">...</main>

<style>
.skip-link {
  position: absolute;
  top: -40px;
  left: 0;
  z-index: 100;
}
.skip-link:focus { top: 0; }
</style>

Motion Preferences

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    transition-duration: 0.01ms !important;
  }
}

Testing

# axe-core (automated)
npx @axe-core/cli https://localhost:3000

# Lighthouse accessibility audit
lighthouse --only-categories=accessibility https://localhost:3000

Checklist

  • Semantic HTML (headings, landmarks, lists)
  • Alt text on all images
  • Color contrast 4.5:1 (text), 3:1 (UI)
  • Keyboard navigable (tab order logical)
  • Focus visible indicator
  • Skip link to main content
  • Form labels and error messages
  • ARIA roles where needed
  • prefers-reduced-motion respected
  • axe-core test pass

Anti-Patterns

  • <div onclick> instead of <button>
  • Color-only information (add icon/text)
  • Auto-playing video/audio
  • Removing focus outline without replacement
  • Using ARIA when native HTML suffices

Related skills