Fixing Accessibility

Audit, fix, and validate accessibility issues. Use when adding or reviewing controls, forms, dialogs, keyboard behavior, focus management, ARIA labels, color contrast, or WCAG compliance.

9 stars 4 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jscraik/Agent-Skills --skill fixing-accessibility
Manual install
git clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Skills/frontend-ui/fixing-accessibility ~/.claude/skills/fixing-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

# Fixing Accessibility

Audit, fix, and validate accessibility issues. Use when adding or reviewing controls, forms, dialogs, keyboard behavior, focus management, ARIA labels, color contrast, or WCAG compliance.

## Philosophy
- Keep the workflow evidence-first and bounded to the requested scope.
- Prefer the smallest reversible step that proves or disproves the current assumption.
- Preserve user work and repo-native contracts before introducing new machinery.

## When To Use
- Reviewing interactive UI for accessibility regressions.
- Fixing keyboard, focus, ARIA, form, and contrast issues.
- Producing minimal code-level accessibility remediation.

## Avoid
- Unrelated work that belongs to a more specific skill.
- Broad rewrites before the first blocker or decision point is understood.
- Claiming success without command, artifact, or decision evidence.

## Inputs
- target files
- framework context
- interactive states
- known violations
- validation tooling

## Outputs
- accessibility findings
- minimal fixes
- validation evidence
- remaining gaps
- Schema-bound outputs include `schema_version`.

## Workflow
1. Classify the requested mode and collect only the missing critical inputs.
2. Inspect 2-3 focused surfaces before expanding scope.
3. Take the smallest action that advances the confirmed goal.
4. Stop at the first failed gate or blocker and report exact evidence.
5. Rerun the relevant validation after fixes before claiming completion.

## Security Constraints
Read the full skill on GitHub

Details

Skill name
fixing-accessibility
Path
Skills/frontend-ui/fixing-accessibility/SKILL.md
License
Apache-2.0
Repo updated
16 November 2026

FAQ

What does the Fixing Accessibility skill do?

Audit, fix, and validate accessibility issues. Use when adding or reviewing controls, forms, dialogs, keyboard behavior, focus management, ARIA labels, color contrast, or WCAG compliance.

How do I install the Fixing Accessibility skill?

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

Is Fixing Accessibility popular?

It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.

Related skills

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