Stood up accessibility as a governed discipline: audits, standards, and enablement built directly into the design system and delivery process, not a one-time compliance sweep.
WCAG 2.2 spans 86 success criteria across three conformance levels. Without a system behind it, "accessible" becomes a claim nobody can actually verify.
Fixes were made screen by screen, with no shared standard to check against
Teams could tell if a component looked fine, not whether it was actually compliant
86 criteria across three conformance levels is too much to track without a system
Accessibility was a QA pass at the end, not a decision made upfront
Every audit and every component decision was checked against the same four principles WCAG is built on.
Content must be presentable in ways users can perceive.
All UI components must be fully navigable by any input.
Information and UI behavior must be clear and predictable.
Content must work reliably across tools and technologies.
Every one of WCAG 2.2's 86 success criteria assessed against the system, not spot-checked, not sampled.
WCAG 2.2 audit results across conformance levels
| Level | Pass | Partial | Yet to Do | N/A | Total | Score |
|---|---|---|---|---|---|---|
| Level A | 23 | 5 | 0 | 3 | 31 | 82% |
| ★Level AA | 20 | 1 | 0 | 3 | 24 | 95% |
| Level AAA | 17 | 1 | 2 | 11 | 31 | 85% |
| Total / Overall | 60 | 7 | 2 | 17 | 86 | 87% |
All 86 WCAG 2.2 success criteria across Level A, AA, and AAA were scored, pass, partial, yet to do, or not applicable, so the actual state of the system was known, not assumed.
Contrast, semantics, and keyboard navigation were fixed at the component level in Floret, so teams inherited compliance by default instead of re-solving it screen by screen.
An accessibility plugin let people preview and adjust for real conditions, contrast, motion, cursor, reading aids, across profiles like low vision, cognitive, and motor-impaired use.
Level AA is the practical standard behind most legal and product requirements. Keeping the audit current, rather than running it once, made compliance a visible, ongoing state.
The real unlock wasn't fixing more screens. It was making the default state accessible, so teams no longer had to remember to check.
Six curated profiles combine the settings that matter most for each kind of need, so the experience adapts without asking anyone to configure it themselves.