Agent skill · design visual · aiskillstore
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
Why this skill is useful
Provides detailed WCAG 2.2 compliance guidelines and specific code examples for improving web accessibility that the AI wouldn't reliably generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Accessibility (a11y) Comprehensive accessibility guidelines based on WCAG 2.2 and Lighthouse accessibility audits. Goal: make content usable by everyone, including people with disabilities. WCAG Principles: POUR Principle Description ----------- ------------- Perceivable Content can be perceived through different senses Operable Interface can be operated by all users Understandable Content and interface are understandable Robust Content works with assistive technologies Conformance levels Level Requirement Target ------- ------------- -------- A Minimum accessibility Must pass AA Standard compliance Should pass (legal requirement in many jurisdictions) AAA Enhanced accessibility Nice to have --- Perceivable Text alternatives (1.1) Images require alt text: Icon buttons need accessible names: Visually hidden class: Color contrast (1.4.3, 1.4.6) Text Size AA minimum AAA enhanced ----------- ------------ -------------- Normal text (< 18px / < 14px bold) 4.5:1 7:1 Large text (≥ 18px / ≥ 14px bold) 3:1 4.5:1 UI components & graphics 3:1 3:1 Don't rely on color alone: Media alternatives (1.2) --- Operable Keyboard accessible (2.1) All functionality must be keyboard accessible. Prefer native interactive elements — <button>, <a href>, and form controls handle Enter/Space activation, focus, and assistive-tech semantics for free. Only add manual keyboard handling when you cannot use a native element. No keyboard traps. Users must be able to Tab into and out of every component. Use the modal focus trap pattern for dialogs—the native <dialog> element handles this automatically. Focus visible (2.4.7) Focus not obscured (2.4.11) — new in 2.2 When an element receives keyboard focus, it must not be entirely hidden by other author-created content such as sticky headers, footers, or overlapping panels. At Level AAA (2.4.12), no part of the focused element may be hidden. Skip links (2.4.1) Provide a skip link so keyboard users can bypass repetitive navigation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/accessibility