agentleFS
botirkhaltaevbotirkhaltaev/botir-skills/skills/a11y-accessibility-design/SKILL.md

a11y-accessibility-design

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Web accessibility (a11y) design fundamentals based on WCAG 2.2 AA. Covers the POUR principles (Perceivable, Operable, Understandable, Robust), color contrast requirements, keyboard navigation, focus management, screen reader support, and a practical pre-ship checklist. Use when designing accessible interfaces, auditing for a11y compliance, or building inclusive products. Triggers on: "accessibility", "a11y", "WCAG", "screen reader", "keyboard navigation", "contrast ratio", "inclusive design", "accessible UI".

Files
SKILL.md

Accessibility (a11y) Design

WCAG 2.2 AA–oriented design fundamentals. Depth in references/. Official spec: WCAG 2.2.

"The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect." — Tim Berners-Lee

POUR (one line each)

PerceivableContrast, alternatives, not color-only, zoom/reflow
OperableKeyboard, focus, targets, no traps
UnderstandableLabels, clear errors, consistent nav
RobustSemantic HTML; ARIA only when needed

Pre-ship (short)

Automated (~30%): axe / Lighthouse / WAVE clean enough to proceed.
Manual (~70%): keyboard-only path; one screen reader pass; contrast; 200% zoom; prefers-reduced-motion; real-device targets.

Content: alt text, input labels, actionable errors, lang, unique titles.

Reference Map

  • references/pour-principles.md — POUR with design asks
  • references/contrast-keyboard-checklist.md — contrast + keyboard + focus CSS
  • references/wcag-22-aa-quick-map.md — designer-facing criterion IDs

Related Skills

  • For visual contrast/type → use ui-visual-design
  • For touch targets → use mobile-touch-design
  • For form labels/validation a11y → use form-ux
  • For error messaging patterns → use error-empty-states
  • For interaction patterns → use interaction-design-patterns

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.