universal-accessibility-wcaglisted

# Universal Accessibility (WCAG Conformance) ## Why this exists Roughly one in six people lives with a disability. Every UI you ship is used by people who are blind or low-vision, who can't use a mouse, who are deaf or hard of hearing, who have limited dexterity or tremor, who have cognitive or attention differences, or who are simply in a hard situation (bright sun, one hand full, a noisy room). Accessibility isn't a feature for a minority — it's the difference between "everyone can use this" and "some people are locked out." It is also, in most jurisdictions, a **legal requirement** (ADA, Section 508, EN 301 549, the European Accessibility Act), and it is far cheaper to build in than to retrofit. This skill's bar is **WCAG 2.2 Level AA conformance, verified** — not "we tried to make it accessible." Accessibility is a property you *build and test*, the same way you build and test correctness. ## The core principle **Semantic HTML first; ARIA only to fill genuine gaps; then verify with automation, the keyboard, and a screen reader.** The vast majority of accessibility comes free from using the right native element. ARIA is a supplement for custom widgets, and *bad ARIA is worse than none*. Nothing is "accessible" until it has been operated without a mouse and heard through a screen reader. Organize everything around WCAG's four principles — **POUR**: Perceivable, Operable, Understandable, Robust. If content fails any one, someone is excluded. ## The workflow ### Step