Frontend Accessibility

Use when the user asks to make a page pass WCAG 2.2 AA in code, fix ARIA, keyboard navigation, focus management, accessible forms and modals, screen reader bugs or add axe tests in CI. Produces accessible component code and automated a11y checks for any framework. Not for design-side audits, contrast reviews or VPATs (use design-accessibility).

45 stars 6 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill frontend-accessibility
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/frontend/universal/accessibility ~/.claude/skills/frontend-accessibility

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Frontend Accessibility

## Purpose
Meet WCAG 2.2 AA standards. Semantic HTML first. ARIA only when necessary. Every interactive element is keyboard accessible. Color contrast meets 4.5:1 minimum. Dynamic content changes announced via live regions. Automated testing enforced in CI.

## Agent Protocol

### Trigger
Exact user phrases: "accessibility", "a11y", "WCAG", "screen reader", "ARIA", "keyboard navigation", "color contrast", "focus management", "semantic HTML", "accessible".

### Input Context
Before activating, verify:
- The component or page being reviewed is specified.
- The WCAG level required (AA by default, AAA for specific requirements) is known.
- Target audience (consumer, enterprise, government) to determine WCAG level.

### Output Artifact
No file output. Produces accessibility review or implementation guidance as text.

### Response Format
Issue:
```
Element: {selector}
Issue: {description}
WCAG: {success criterion}
Severity: {critical/major/minor}
Fix: {specific code change}
```

Implementation:
```
Pattern: {name}
HTML: {semantic element}
ARIA: {aria attributes if needed}
Keyboard: {focus behavior}
```

No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output.

### Completion Criteria
- [ ] Semantic HTML elements used instead of div/span with ARIA roles.
- [ ] ARIA used only when native HTML semantics do not cover the pattern.
- [ ] All interactive elements keyboard accessible (Tab, Enter, Escape).
Read the full skill on GitHub

Details

Skill name
frontend-accessibility
Path
skills/frontend/universal/accessibility/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Frontend Accessibility skill do?

Use when the user asks to make a page pass WCAG 2.2 AA in code, fix ARIA, keyboard navigation, focus management, accessible forms and modals, screen reader bugs or add axe tests in CI. Produces accessible component code and automated a11y checks for any framework. Not for design-side audits, contrast reviews or VPATs (use design-accessibility).

How do I install the Frontend Accessibility skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill frontend-accessibility. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Frontend Accessibility popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Frontend Animation

45

j4flmao/agent-skills

Use when the user asks about Motion (Framer Motion), GSAP, CSS keyframes and transitions, the View Transitions API, page transitions, enter/exit or spring animations and prefers-reduced-motion. Produces performant, accessible web animation code. Not for motion principles and specs (use design-motion-design) or 3D scenes (use web3d-webgl).

Frontend & Design

Ember

45

j4flmao/agent-skills

Use when the user asks about Ember.js, Ember CLI, Ember Octane, Glimmer components, tracked properties, Ember routes and services, or Ember Data / WarpDrive. Produces convention-driven Ember code and data-layer setup. Not for React, Vue or Angular apps (use react-architecture, vue-architecture or angular-architecture).

Frontend & Design

Frontend Astro Patterns

45

j4flmao/agent-skills

Use when the user asks about Astro island patterns, client:load / client:visible / client:idle, server islands, view transitions, Astro integrations, content collection queries or per-route prerendering. Produces hydration and rendering patterns for an existing Astro site. Not for initial Astro project setup (use frontend-astro-architecture).

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.