Lily Design System™

Whit “targets WCAG 2.2 AAA” means here

The wird targets is deliberate. This page says precisely whit is verified, bi whit, whit is no verified bi onything, an whit we intend tae dae aboot the gap. Lily never claims WCAG “compliance” — nae audit supports it.

Verified, continuously

  • Ilka component's canonical semantic element, ARIA attributes, an class hooks — asserted bi per-framework unit suites (15,000+ cases athort seiven frameworks).
  • Ilka ane o the 571 component demo pages in the SvelteKit example app is axe-clean (WCAG 2.0/2.1 A+AA an 2.2 AA rule sets) — the full-catalog sweep, first baselined 2026-08-27 an re-run 2026-10-06 — plus per-app baselines on hame, catalog, an composed routes in aw seiven example apps.
  • Keyboard contracts per interactive component, documentit in ilka component's canonical metadata an exercised bi the suites; the helper packages additionally rin real-browser Playwright specs.
  • WCAG 2.2 target-size flairs an overflow guairds in aw 57 themes; skip-link, landmarks, an nae horizontal overflow at fower viewports per app; lang/dir application an the RTL flip.

No verified bi onything

  • Nae conformance audit haes ever been performed. Nae VPAT, nae certification. Automatit tooling covers a minority o WCAG success criteria.
  • AAA-specific criteria (enhanced contrast, an ithers) are design intents, no verified properties; the axe rule sets rin A/AA. There is nae dedicatit high-contrast theme yet.
  • Screen-reader behaviour is lairgely untestit. The suites assert ARIA attributes, no whit VoiceOver, NVDA, or JAWS announce — an this project haes shipped green suites ower real defects mair than anes, ilkane scrievit up in the changelog juist because the suites couldnae see them.

Whit we intend tae dae aboot it

An independent accessibility audit is the first namit uiss o onie project funding, an the scope an auditor needs is aareadies prepared. Till then, screen-reader reports are the contribution this project wants maist: “component X announces Y, which is wrang because Z” is directly actionable.

Report a problem

Open an issue at github.com/LilyDesignSystem/lily-design-system or email joel@joelparkerhenderson.com. Namin a WCAG criterion helps but isnae required — “I couldnae operate X wi the keyboard” is a complete report.

The full statement, wi the verification table an its review history, lives in the repository: docs/accessibility-statement.md.