# Audit Web Accessibility for WCAG Compliance

Accessibility gaps can block users and create compliance risk. This skill guides WCAG audits, screen reader checks, keyboard testing, and remediation planning.

## Install

```bash
npx skillstore add joseph obrien/89jobrien-web-accessibility
```

## Metadata

- Status: approved
- Slug: 89jobrien-web-accessibility
- Version: 1.0.1
- Author version: 1.0.1
- Skillstore revision: r1
- Version status: valid
- Tree hash: 77c9a0ed3a576fef30362c5397a2798cb75269fdd7f0087e27cf7dd7665b81a2
- Author: Joseph OBrien
- GitHub username: 89jobrien
- License: MIT
- Repository: https://github.com/89jobrien/steve/tree/main/steve/skills/web-accessibility
- Ref: c4037264bbd363c572662d6154a3ab28f5ca4f53
- 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
- Quality score: 82
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/89jobrien-web-accessibility
- Manifest: https://skillstore.pages.dev/api/skills/89jobrien-web-accessibility/manifest

## Capabilities

- Assess WCAG 2.1 and 2.2 conformance levels for web pages.
- Review semantic HTML, headings, landmarks, and ARIA usage.
- Check keyboard navigation paths, focus order, and focus visibility.
- Identify color contrast issues against Level AA and AAA targets.
- Evaluate image text alternatives, form labels, and error messaging.
- Produce prioritized accessibility fixes with clear user impact.

## Use Cases

- Audit a Release Candidate: Review key pages before launch and list WCAG issues by severity and user impact.
- Improve Inclusive Interaction Design: Check focus states, keyboard flows, labels, and contrast before design handoff.
- Prepare Compliance Evidence: Create a structured issue summary for accessibility tracking and stakeholder review.

## Prompt Templates

### Quick WCAG Check

```
Audit this page for WCAG 2.2 Level AA issues. Focus on headings, links, images, forms, and color contrast.
```

### Keyboard Navigation Review

```
Review this flow for keyboard accessibility. Check tab order, focus visibility, skip links, traps, and operable controls.
```

### Component Remediation Plan

```
Analyze this component for accessibility issues. Provide prioritized fixes for semantics, ARIA, focus management, and error messaging.
```

### Full Release Audit

```
Perform a WCAG 2.2 audit for these screens. Group findings by severity, criterion, affected users, and recommended remediation.
```

## Limitations

- Does not run automated browser tests unless the host agent provides tools.
- Cannot verify screen reader output without access to assistive technology.
- Requires page source, screenshots, or a live site for precise findings.
- WCAG interpretations may need legal or organizational review for formal compliance.

## Best Practices

- Provide the page URL, affected components, and target WCAG level before requesting an audit.
- Include screenshots or source snippets when visual contrast or semantic structure matters.
- Validate recommendations with keyboard testing and assistive technology when possible.

## Anti Patterns

- Do not rely only on automated scores for accessibility approval.
- Do not add ARIA when native HTML already provides the correct semantics.
- Do not treat color alone as the only way to communicate state or errors.

## Security Audit

- Audited at: 2026-07-05T14:20:04.58\+00:00
- Summary: Static analysis flagged 11 external command findings, but each cited line is a Markdown code fence or documentation example in SKILL.md. No executable command invocation, prompt injection, data exfiltration intent, or unsafe automation was found.

## Stats

- Views: 187
- Downloads: 17
- Favorites: 0
- Popularity score: 0