Lily Design System™

Wetin “targets WCAG 2.2 AAA” mean here

Di word targets na on purpose. Dis page talk exactly wetin dem verify, with wetin, wetin nothing verify, and wetin we plan to do about di gap. Lily no dey ever claim WCAG “compliance” — no audit support am.

Verified, continuously

  • Every component canonical semantic element, ARIA attributes, and class hooks — dem assert am with per-framework unit suites (15,000+ cases across seven frameworks).
  • Every one of di 571 component demo pages for di SvelteKit example app dey axe-clean (WCAG 2.0/2.1 A+AA and 2.2 AA rule sets) — di full-catalog sweep, first baselined 2026-08-27 and run again 2026-10-06 — plus per-app baselines for home, catalog, and composed routes for all seven example apps.
  • Keyboard contracts for every interactive component, wey dem document for each component canonical metadata and wey di suites dey test; di helper packages still dey run real-browser Playwright specs too.
  • WCAG 2.2 target-size floors and overflow guards for all 57 themes; skip-link, landmarks, and no horizontal overflow for four viewports per app; lang/dir application and di RTL flip.

Nothing verify am

  • Dem never ever perform conformance audit. No VPAT, no certification. Automated tooling cover small part of WCAG success criteria.
  • AAA-specific criteria (enhanced contrast, and others) na design intents, no be verified properties; di axe rule sets dey run A/AA. High-contrast theme still no dey.
  • Screen-reader behaviour mostly no test. Di suites dey assert ARIA attributes, no be wetin VoiceOver, NVDA, or JAWS go announce — and dis project don ship green suites over real defects more than once, each one dem write am for di changelog just because di suites no fit see dem.

Wetin we plan to do about am

Independent accessibility audit na di first named use of any project funding, and di scope wey auditor need don ready already. Until dat time, screen-reader reports na di contribution wey dis project want pass: “component X announce Y, wey wrong because Z” dey directly actionable.

Report problem

Open issue for github.com/LilyDesignSystem/lily-design-system or email joel@joelparkerhenderson.com. To name WCAG criterion dey help but e no compulsory — “I no fit operate X with keyboard” na complete report.

Di full statement, with di verification table and im review history, dey for di repository: docs/accessibility-statement.md.