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

Frontend Accessibility

  • 1 installs
  • 3 repo stars
  • Updated July 8, 2026
  • ai-enhanced-engineer/aiee-team

frontend-accessibility is a Claude Code skill providing WCAG 2.1 AA accessibility patterns for web UIs, covering ARIA, keyboard navigation, screen readers, and contrast.

About

frontend-accessibility is a Claude Code skill covering web accessibility patterns for WCAG 2.1 AA compliance. It provides quick references for ARIA landmarks, keyboard navigation, color contrast, focus management, and common mistakes, plus an interactive-component checklist. A developer uses it during accessibility audits or when implementing accessible, framework-agnostic and Angular components.

  • WCAG 2.1 AA accessibility patterns: ARIA, keyboard nav, screen readers, contrast
  • Includes a contrast-fix color table and an interactive-component a11y checklist
  • Shows native <details> progressive disclosure and Angular accessible-component patterns

Frontend Accessibility by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #1,912 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Data as of Jul 9, 2026 (Skillselion catalog sync)
At a glance

frontend-accessibility capabilities & compatibility

Capabilities
accessibility audit · aria implementation · keyboard navigation
Use cases
frontend · ui design
From the docs

What frontend-accessibility says it does

Web accessibility patterns for WCAG 2.1 AA compliance including ARIA, keyboard navigation, screen reader support, and Angular and framework-agnostic implementations.
SKILL.md
Normal text: **4.5:1** minimum
SKILL.md
npx skills add https://github.com/ai-enhanced-engineer/aiee-team --skill frontend-accessibility

Add your badge

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

Listed on Skillselion
Installs1
repo stars3
Last updatedJuly 8, 2026
Repositoryai-enhanced-engineer/aiee-team

What it does

Implement or audit WCAG 2.1 AA accessible web UI using ARIA, keyboard navigation, contrast, and focus-management patterns.

Who is it for?

Accessibility audits and implementing WCAG 2.1 AA compliant, inclusive web components.

Skip if: Backend work or non-accessibility frontend architecture decisions.

When should I use this skill?

For accessibility audits, a11y implementation, or inclusive design.

What you get

Accessible components with correct ARIA, keyboard support, contrast, and focus management.

By the numbers

  • Contrast targets: 4.5:1 normal text, 3:1 large text and interactive elements
  • 5-item interactive-component accessibility checklist

Files

SKILL.mdMarkdownGitHub ↗

Frontend Accessibility Patterns

WCAG 2.1 AA compliance patterns for modern web applications.

Core Principles (POUR)

PrincipleDescription
PerceivableInformation presentable in ways users can perceive
OperableInterface components operable by all users
UnderstandableInformation and operation understandable
RobustWorks with current and future technologies

Quick Reference

Keyboard Navigation

  • Tab/Shift+Tab: Navigate interactive elements
  • Enter/Space: Activate buttons/links
  • Escape: Close modals/dropdowns
  • Arrow keys: Navigate lists/menus

Color Contrast (WCAG AA)

  • Normal text: 4.5:1 minimum
  • Large text (18pt+): 3:1 minimum
  • Interactive elements: 3:1 minimum

Common Adjustments (maintain hue, reduce HSL lightness ~20%):

OriginalFixedUse CaseContrast
#ef4444#c53030Error red4.5:1 ✅
#f59e0b#b45309Warning orange4.5:1 ✅
#10b981#047857Success green4.5:1 ✅
#3b82f6#1d4ed8Info blue4.5:1 ✅

Rule: For status colors on white background, check contrast at webaim.org/resources/contrastchecker

ARIA Essentials

<!-- Landmarks -->
<header role="banner">
<nav role="navigation" aria-label="Main">
<main role="main">
<footer role="contentinfo">

<!-- Live regions (for dynamic content like chat) -->
<div role="status" aria-live="polite" aria-atomic="true">
  <!-- Screen reader announces changes -->
</div>

<!-- Accessible buttons -->
<button aria-label="Close dialog" aria-pressed="false">

Focus Management

  • Visible focus indicators (never outline: none without alternative)
  • Trap focus in modals
  • Return focus on modal close
  • Manage focus on route changes

Common Mistakes

  • Missing alt on images
  • Form inputs without labels
  • Color as only indicator
  • Mouse-only interactions
  • Missing skip links
  • Auto-playing media
  • Conflicting visual states (e.g., "featured" and "selected" both using same visual indicator—use distinct patterns)

Interactive Component Accessibility Checklist

For custom interactive components (tabs, accordions, selectors, toggles):

  • [ ] ARIA markup - Correct role, aria-checked/selected/expanded
  • [ ] JavaScript announcements - aria-live regions for state changes
  • [ ] Keyboard navigation - Tab, Enter/Space, Arrow keys
  • [ ] Visual states - Clear focus/selected/disabled indicators
  • [ ] Focus management - Logical flow, no focus traps

Progressive Disclosure with Native HTML

Use native <details> elements instead of custom JavaScript accordions:

<details class="expandable-section">
  <summary>
    <h3>Section Title</h3>
    <span class="chevron" aria-hidden="true">▼</span>
  </summary>
  <div class="expanded-content">
    <!-- Content here -->
  </div>
</details>
details summary {
  cursor: pointer;
  list-style: none;
  user-select: none;
}

details summary::-webkit-details-marker {
  display: none;
}

details[open] .chevron {
  transform: rotate(180deg);
}

details summary:focus {
  outline: 2px solid var(--accent-primary);
  outline-offset: 2px;
}

Benefits:

  • Built-in keyboard navigation (Tab, Enter/Space to toggle)
  • Screen readers announce "collapsed/expanded" state automatically
  • Works without JavaScript
  • Less code to maintain

When to use: FAQs, expandable cards, skill lists, workflow phases, any progressive disclosure pattern

Decorative Elements with Text Alternatives

For visual flow indicators (arrows, connectors):

<!-- Visual arrows (hidden from screen readers) -->
<div class="flow-arrow" aria-hidden="true">...</div>

<!-- Text alternative for screen readers and mobile -->
<p class="flow-description">
  After Phase 5, teams iterate back to Phase 1 (max 3 cycles).
</p>

Responsive strategy:

  • Desktop (1024px+): Show visual arrows, hide text description
  • Mobile/tablet: Hide arrows, show text description

See reference.md for WCAG criteria and examples.md for Angular implementations.

Related skills

FAQ

What contrast ratios does it require?

4.5:1 minimum for normal text and 3:1 for large text (18pt+) and interactive elements under WCAG AA.

How does it recommend building accordions?

Use native <details>/<summary> elements instead of custom JavaScript accordions so keyboard navigation and expanded/collapsed announcements work automatically.

This week in AI coding

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

unsubscribe anytime.