# Audit and Fix Web Accessibility Issues

Automated checks miss barriers that affect users navigating by keyboard or screen reader. Combine scanner findings with manual tests to prioritize fixes and verify them.

## Install

```bash
npx skillstore add addyosmani/accessibility-engineering
```

## Metadata

- Status: approved
- Slug: addyosmani-accessibility-engineering
- Skillstore revision: r1
- Version status: missing
- Tree hash: 6adfbaa2fe749674dbe40a89650a1ccf315430b5ffd11463d3c91c88e5631805
- Author: addyosmani
- GitHub username: addyosmani
- Repository: https://github.com/addyosmani/agent-skills/tree/8c99fa36d90068c82d547f7c12a9d67a3e95f4ee/skills/accessibility-engineering
- Ref: b801e7ae7b71c5eca7822ed69f7a16176f3b6ed1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem, network
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/addyosmani-accessibility-engineering
- Manifest: https://skillstore.pages.dev/api/skills/addyosmani-accessibility-engineering/manifest

## Capabilities

- Run axe-core and pa11y against a web page or pa11y alone against a local HTML file.
- Combine automated findings into text or JSON reports with tool versions, status, and severity totals.
- Flag incomplete scanner runs instead of reporting a zero-violation total.
- Guide manual checks for keyboard navigation, screen reader announcements, contrast, zoom, and reduced motion.
- Prioritize verified fixes using native HTML when possible, then repeat the checks to verify the changes.

## Use Cases

- Fix an inaccessible form: Verify missing labels and keyboard problems in an existing form. Make targeted fixes and retest the affected controls.
- Verify a release candidate: Pair scanner reports with manual checks on a staging page. Record the browser, assistive technology, and checks that could not be run.
- Prioritize accessibility findings: Review verified barriers and separate them from untested items. Use the impact on key user tasks to decide what should be fixed first.

## Prompt Templates

### Review a single form

```
Review this form for missing labels, unclear errors, and keyboard access. Explain each issue and list the manual checks I should run.
```

### Triage a scanner report

```
Review these axe-core and pa11y findings. Group reports of the same issue, identify the affected controls, and say how to verify each issue manually.
```

### Verify a checkout fix

```
Plan a keyboard and screen reader retest for this checkout modal. Check initial focus, Escape, focus return, and error announcements. Mark unavailable checks as untested.
```

### Audit a release candidate

```
Audit the approved staging page using existing local tools. Ask before installing anything. Compare scanner findings with manual results and separate verified failures from checks that were not run.
```

## Limitations

- Automated results do not prove WCAG 2.2 AA conformance.
- The wrapper requires Bash, Node.js, and npm. The toolchain may need network access to fetch packages or browser components.
- Local file mode runs only pa11y. Screen reader checks need a browser and assistive technology.
- The standalone bundle does not include the referenced checklist or companion resources.

## Best Practices

- Verify each automated finding in the browser before changing the interface.
- Use native HTML controls where possible and retest behavior after each fix.
- Record the browser, assistive technology, and checks that were not run.

## Anti Patterns

- Claiming conformance after a clean automated scan.
- Adding ARIA labels to custom controls without fixing their keyboard behavior.
- Running an audit on an unapproved target or sharing raw reports without checking for sensitive content.

## Security Audit

- Audited at: 2026-11-19T17:00:35.756\+00:00
- Summary: Most alerts describe Markdown formatting, documentation links, or routine report handling. The script embeds environment-derived paths in JavaScript, automatically runs npm packages, and opens user-supplied targets with no enforced audit scope. Page content enters the reports, but the reviewed files show no evidence of deliberate data exfiltration or embedded prompt injection.

## Stats

- Views: 0
- Downloads: 2
- Favorites: 0
- Popularity score: 0
