Accessibility
Requirements extracted from Figma node 4265:20659. These rules guide tokens, documentation, and components.
Target
Use WCAG 2.2 AA as the target where it applies to static CSS, documentation, and component examples. This repository does not claim a full accessibility audit yet.
Rules
| Requirement | Implementation rule | Validation |
|---|---|---|
| Text and background contrast | Examples and component states must keep readable foreground/background combinations. | Manual visual review for now; add automated contrast checks when tooling exists. |
| Readable font sizes | Docs and component examples must use typography tokens or readable fallback sizes. | Review generated pages at desktop and mobile widths. |
| Do not rely on color alone | Status, feedback, and destructive states need text, labels, icons, or another non-color cue. | Check every component state table and example before commit. |
Component Checklist
| Check | Applies to |
|---|---|
| Visible focus state is defined and documented. | Interactive components |
| Disabled state does not depend only on color. | Buttons, inputs, list actions |
| Error and success states include a text or structural cue. | Form controls and feedback |
| Icon-only controls require an accessible name. | Buttons and compact actions |
| Examples avoid using color as the only information channel. | All docs pages |