This site targets WCAG 2.2 Level AA. A script checks it on every build, and the build fails if any of these slip.
MeasuredThe gates
-
0
axe-core violations
across /, /about, /research, /vibeset/cue
-
100
Lighthouse accessibility
mobile, production build
-
100
Lighthouse best practices
mobile, production build
-
0
Cumulative layout shift
not "good" — zero
-
≤ 200 ms
Total blocking time
measured on throttled mobile
tooling: playwright + @axe-core/playwright · lighthouse · last full pass August 2026
Built inWhat that means in practice
- Keyboard first. Every control works without a mouse, and focus is always visible.
- Motion is optional. Turn it off and the page is complete and fully drawn — just still. Nothing hides, nothing collapses.
- Nothing needs JavaScript to be read. Without it, everything renders immediately instead of staying invisible.
- Type is chosen for legibility. Body copy is Atkinson Hyperlegible, built to keep characters distinct for low-vision readers.
- Contrast is built in. Accents that fail AA at small sizes have text-safe variants, so the accessible colour is the easy one to reach for.
- No spinners. Progress is a labelled status region with a text caption.
GapsWhere it falls short
A statement with no problems in it isn't a statement. So here are mine.
- The audio workbench is visual-first. Results are announced as text, but the live spectrum has no non-visual equivalent.
- Automated testing has limits. Axe catches maybe half of real problems; the rest need people. No screen-reader user other than me has tested this yet.
- Third-party content isn't covered. The Vibeset products are separate applications with their own posture.
ContactFound a barrier?
Tell me and I'll fix it. These go to the front of the queue. It's the one place where "works for most people" isn't good enough.
last reviewed August 2026 against wcag 2.2 aa