# Fix Accessibility Issues in Web Interfaces

Web interfaces often exclude users through missing labels, weak keyboard support, and incorrect focus behavior. This skill audits common accessibility failures and proposes minimal, targeted fixes.

## Install

```bash
npx skillstore add ibelick/fixing-accessibility
```

## Metadata

- Status: approved
- Slug: ibelick-fixing-accessibility
- Skillstore revision: r2
- Version status: missing
- Tree hash: 6eda848d4e0d5a28c66d9538c66df1dc599d8394c5a74a50985225081da4c10a
- Author: ibelick
- GitHub username: ibelick
- License: MIT
- Repository: https://github.com/ibelick/ui-skills/tree/main/skills/fixing-accessibility/
- Ref: c43861a65bb95efcae259cd161c9d6f4dc7eec6f
- 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: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/ibelick-fixing-accessibility
- Manifest: https://skillstore.pages.dev/api/skills/ibelick-fixing-accessibility/manifest

## Capabilities

- Reviews UI files for accessible names, semantic HTML, keyboard access, and visible focus.
- Identifies dialog requirements for initial focus, focus trapping, Escape handling, and trigger restoration.
- Checks form labels, helper text, required states, invalid states, and error associations.
- Evaluates announcements, contrast-dependent states, media alternatives, and reduced-motion support.
- Produces quoted violations, concise impact explanations, and targeted code-level fixes.

## Use Cases

- Repair a UI Component: Review a component for missing names, incorrect semantics, keyboard barriers, and focus issues before release.
- Review Form Accessibility: Check labels, required states, helper text, validation errors, and announcements across a user journey.
- Assess an Interaction Pattern: Evaluate a dialog, menu, or dropdown and identify requirements for keyboard access and focus management.

## Prompt Templates

### Check Accessible Names

```
Review {file} for missing accessible names and incorrect native semantics. Quote each issue and propose a minimal fix.
```

### Audit a Form

```
Audit the form in {file}. Check labels, helper text, required states, aria-invalid, error associations, and live announcements. Prioritize critical failures.
```

### Review Keyboard and Focus

```
Review {files} for keyboard and focus behavior. Check Tab access, visible focus, Escape handling, focus trapping, initial focus, and focus restoration.
```

### Run a Prioritized Audit

```
Perform a prioritized accessibility audit of {scope}. Cover every listed rule category, preserve the architecture, and provide targeted fixes for verified violations.
```

## Limitations

- Provides rule-based guidance but does not run automated accessibility scanners or browser tests.
- Cannot confirm rendered contrast, focus order, or assistive technology behavior without runtime evidence.
- Covers common HTML and ARIA concerns, not every WCAG success criterion.
- Complex widgets may require established accessible libraries and manual testing.

## Best Practices

- Test fixes with keyboard navigation, browser accessibility tools, and at least one screen reader.
- Prefer native HTML elements before adding ARIA roles or custom keyboard behavior.
- Make minimal changes and verify that each fix preserves existing interactions.

## Anti Patterns

- Do not add ARIA when native HTML already provides the required semantics.
- Do not remove focus outlines without a clear visible replacement.
- Do not refactor unrelated components during a focused accessibility repair.

## Security Audit

- Audited at: 2026-07-23T18:38:49.363\+00:00
- Summary: All seven static alerts are false positives. Backticks delimit Markdown commands or HTML examples, and the flagged prose contains accessibility guidance rather than system reconnaissance. No prompt injection, external execution, or malicious intent is present.

## Stats

- Views: 133
- Downloads: 6
- Favorites: 0
- Popularity score: 0