Accessibility

Quick Guide: Most of accessibility is settled by choosing the right element: a <button> arrives with focus, keyboard activation and a role that a <div> needs a dozen lines to fake. What the element cannot give you is the rest — a name for every control, a visible focus indicator, 4.5:1 contrast on text, an announcement when content changes, and information never carried by colour alone. Target WCAG 2.2 Level AA. Automated checks find roughly half the failures, so a keyboard pass is not optional.

Detailed Resources:

• examples/core.md — skip links, landmarks, semantic structure, button versus link
• examples/forms.md — labels, error handling, required fields, the listbox contract
• examples/focus.md — dialogs, focus trapping and restoration, focus indicators
• examples/color.md — contrast, colour-independent status, link styling
• examples/tables.md — headers, captions, sortable columns
• examples/touch-targets.md — target size and spacing
• examples/screen-reader.md — visually hidden text, decorative content
• examples/testing.md — automated auditing, role-based queries, the manual pass
• reference.md — WCAG 2.2 criteria, accessible-name rules, audit rule IDs, screen readers

<critical_requirements>