Skip to content
Back to skills

Accessibility Checklist

ASecurity

When building UI components, forms, or any user-facing interface. Check before every frontend PR.

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
developmentfrontend

Works with

  • cli

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add majiayu000/claude-skill-registry --skill accessibility-checklist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Accessibility Checklist?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Accessibility Checklist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-accessibility-checklist-claude-skill-registry/badge)](https://www.skillsdirectory.com/skills/majiayu000-accessibility-checklist-claude-skill-registry)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: accessibility-checklist
description: When building UI components, forms, or any user-facing interface. Check before every frontend PR.
version: 1.1.0
tokens: ~450
confidence: high
sources:
  - https://www.w3.org/WAI/WCAG22/quickref/
  - https://developer.mozilla.org/en-US/docs/Web/Accessibility
last_validated: 2025-12-10
next_review: 2025-12-24
tags: [accessibility, a11y, frontend, ux]
---

## When to Use
When building UI components, forms, or any user-facing interface. Check before every frontend PR.

## Patterns

### Keyboard Navigation
```html
<!-- All interactive elements focusable -->
<button>Click me</button>  <!-- ✅ Naturally focusable -->
<div role="button" tabindex="0">Click me</div>  <!-- ✅ Made focusable -->

<!-- Focus visible and not obscured (WCAG 2.2) -->
button:focus { outline: 2px solid blue; }
```

### Screen Reader Support
```html
<!-- Images -->
<img src="chart.png" alt="Sales increased 20% in Q4" />
<img src="decoration.png" alt="" />  <!-- Decorative: empty alt -->

<!-- Form labels -->
<label for="email">Email</label>
<input id="email" type="email" aria-required="true" />

<!-- Dynamic content -->
<div aria-live="polite" aria-busy="false">Loading complete</div>
```

### ARIA Essentials
```html
<!-- Button without text -->
<button aria-label="Close dialog"><svg>...</svg></button>

<!-- Expanded/collapsed -->
<button aria-expanded="false" aria-controls="menu">Menu</button>

<!-- Modal -->
<div role="dialog" aria-modal="true" aria-labelledby="title">
```

## Anti-Patterns
- Color-only indicators (add icons/text)
- Missing form labels (placeholder is NOT a label)
- Tiny touch targets (<44x44px)
- Keyboard traps (can't escape with Tab/Escape)
- Auto-playing media without controls
- Focus obscured by sticky headers/modals

## Verification Checklist
- [ ] All interactive elements reachable via Tab
- [ ] Focus indicator visible on all focusables
- [ ] Focus not obscured by sticky content (WCAG 2.2)
- [ ] Images have meaningful alt (or alt="" if decorative)
- [ ] Form inputs have associated labels
- [ ] Color contrast ≥4.5:1 (text) / ≥3:1 (large text)
- [ ] Touch targets ≥44x44px
- [ ] `prefers-reduced-motion` respected
- [ ] No cognitive tests for auth (avoid CAPTCHAs)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.