# Audit and Build Accessible Interfaces

Teams often miss WCAG, keyboard, and screen reader requirements during interface work. This skill provides practical patterns, audit checklists, and remediation guidance for accessible web and mobile experiences.

## Install

```bash
npx skillstore add wshobson/accessibility-compliance
```

## Metadata

- Status: approved
- Slug: wshobson-accessibility-compliance
- Skillstore revision: r1
- Version status: missing
- Tree hash: 1d1e6b2981e2537ca27ca1bb5bef1d0f5badae871603f3d09d25921781ad9c05
- Author: wshobson
- GitHub username: wshobson
- License: MIT
- Repository: https://github.com/wshobson/agents/tree/main/plugins/ui-design/skills/accessibility-compliance/
- Ref: 36e07d5e13068e5be64447e8f20b427cf2cbd21a
- 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, network
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/wshobson-accessibility-compliance
- Manifest: https://skillstore.pages.dev/api/skills/wshobson-accessibility-compliance/manifest

## Capabilities

- Maps interface issues to WCAG 2.2 principles and success criteria.
- Provides ARIA patterns for accordions, tabs, dialogs, menus, comboboxes, and live regions.
- Guides keyboard navigation, focus management, skip links, and visible focus states.
- Explains screen reader support for semantic HTML, labels, headings, and announcements.
- Covers mobile accessibility for iOS VoiceOver, Android TalkBack, touch targets, and text scaling.
- Lists testing tools, checklists, and common accessibility failures.

## Use Cases

- Fix WCAG violations before release: Inspect forms, dialogs, navigation, and dynamic updates, then apply accessible code patterns.
- Design accessible interactions: Set touch targets, focus behavior, labels, and contrast requirements before design handoff.
- Plan manual accessibility testing: Build coverage for keyboard, screen reader, mobile, zoom, contrast, and reduced motion checks.

## Prompt Templates

### Check a page for basics

```
Review this interface for WCAG 2.2 AA basics. Focus on labels, contrast, keyboard access, headings, and alt text. Return prioritized fixes.
```

### Improve an interactive component

```
Make this component accessible. Add semantics, keyboard behavior, focus handling, labels, and live announcements. Explain each change.
```

### Create a mobile accessibility plan

```
Build an accessibility plan for this mobile flow. Cover VoiceOver, TalkBack, touch targets, gestures, text scaling, and dynamic announcements.
```

### Run a release readiness review

```
Review this release for accessibility readiness. Map risks to WCAG 2.2, identify blockers, suggest tests, and define acceptance criteria.
```

## Limitations

- Does not replace audits by disabled users or certified accessibility specialists.
- Cannot prove compliance without testing the real product in target browsers and devices.
- Examples may need adaptation for each framework, component library, and design system.
- Does not run automated accessibility scanners by itself.

## Best Practices

- Prefer semantic HTML before adding ARIA roles, states, or properties.
- Test keyboard, screen reader, zoom, contrast, and reduced motion behavior on real interfaces.
- Document accessibility acceptance criteria before implementation and verify them before release.

## Anti Patterns

- Replacing native controls with custom widgets without matching keyboard and screen reader behavior.
- Treating automated scanner results as complete proof of accessibility compliance.
- Removing focus indicators or hiding dynamic changes from assistive technologies.

## Security Audit

- Audited at: 2026-07-07T07:12:40.04\+00:00
- Summary: I did not find evidence that the static analyzer hits represent real security issues. The flagged backticks, key references, URLs, Android terms, and checklist text are accessibility documentation or code examples, not command execution, secrets, or reconnaissance.

## Stats

- Views: 143
- Downloads: 10
- Favorites: 0
- Popularity score: 0