Where it stands

The target is WCAG 2.2 Level AA. I believe the site substantially meets it, with the caveats below. That's a self-assessment by one person, not a certified audit — treat it as a good-faith claim rather than a guarantee.

What's been done

• Every animation respects prefers-reduced-motion. If your OS says you don't want motion, the scanlines stop, the cursor trail disappears, and transitions collapse to nothing.
• The boot sequence, the command palette and the shortcuts overlay are real dialogs: they trap focus while open, close on Escape, and mark the rest of the page inert so a screen reader doesn't wander into it.
• Decorative effects are hidden from assistive tech rather than read aloud. The typewriter effect keeps the full sentence in a screen-reader-only element and only animates a copy marked aria-hidden, so you hear the finished text, not one letter at a time.
• Everything works from the keyboard, with visible focus rings that aren't removed. A skip link is the first thing you reach on every page.
• The whole site works without JavaScript for reading: content is server-rendered, and the boot overlay removes itself if JS never runs.
• Live regions announce things that change on their own — the copy button's confirmation, the projects filter's result count.

Where it falls short

An accessibility statement that only lists wins is marketing. These are the real ones:

The whole thing is monospace, green on black

That's the point of the design, but it's a real tradeoff. Monospace is harder to read at length for some people with dyslexia. The phosphor palette clears WCAG AA contrast for body text, but if a low-contrast theme is picked in display settings, that guarantee is gone — the picker lets you make it unreadable and I haven't clamped it.

The shell is not a great screen reader experience

It's a text input that prints output above itself. Output is announced, but it's a novelty interface, not a well-trodden pattern. Everything the shell can show you is also a normal page you can navigate to — nothing is shell-only.

The CRT overlay and cursor trail are cosmetic noise

Both can be turned off (display settings, or reduced-motion does it for you), but they're on by default, and a default that assumes nobody minds is a choice I made for aesthetics.

It hasn't been audited

No formal WCAG audit, no professional screen reader testing. I've done what I know how to do and tested with a keyboard and the tools I have. That's not the same as being verified, and I'd rather say so than imply a level of assurance that doesn't exist.

Turning the theatre off

The display panel (the [DISPLAY] control, or themein the shell) switches off the CRT overlay and changes the colour. Setting "reduce motion" in your operating system does most of it automatically, without touching anything here.

If something doesn't work

Please tell me — hello@mysuvo.com. If something here blocks you, that's a bug and I'd rather fix it than not know. Tell me what you were using and what happened; I'll reply and I'll actually fix it.

Changes

Last updated: 2026-07-16.