Why this page exists
Most sites treat accessibility as a widget you drop in after launch — a floating menu that promises everything and delivers a lawsuit. We don't do that here. Accessibility is infrastructure: it gets checked before anything ships, the same way the code does.
This page is the public face of that work. It's also a working example of it — keyboard-navigable, screen-reader friendly, and honest about what's live now versus what's still coming.
The rollout
Three phases, in order. Each one has to hold before the next goes up.
Automated testing in the build
LiveEvery page runs through axe-core — an open-source engine that audits against WCAG 2.2 AA — before it can ship. It catches the code-level failures that break screen readers: missing labels, bad contrast, broken heading structure, unlabeled controls. If a page fails, it doesn't go live.
Manual review & this hub
LiveAutomation catches roughly half the real issues. The rest — keyboard traps, custom controls, whether content actually makes sense out loud — gets a human spot-check. This hub, and the feedback channel below, are the visible half of that layer.
Signed & narrated video
NextThe long-term goal: Brody Wolf on camera, signing and narrating the content directly — starting with The Den — so the accessible layer is our own brand, not a generic avatar. It's a pre-rendered video that plays alongside the text, so there's no server translating on the fly. Coming once the video pipeline is running.
How content gets checked
Three layers, because no single one is enough on its own.
Automated
axe-core flags the machine-detectable failures on every build. Fast, consistent, and it never gets tired — but it can only see about 57% of real issues.
Manual
The other 43% needs a person: real keyboard runs, screen-reader passes on NVDA and VoiceOver, and a check that custom tools actually work.
Real users
People who use assistive tech every day tell us what actually breaks. That feedback drives the monthly review and the next release.
Audio, everywhere
Novels and blogs ship with audiobook versions, and video carries captions and transcripts — so the content works whether you're reading, listening, or both.
Three languages, equal priority
We're building for North America, South America, and Japan from day one — not English-first with translations bolted on later. Each language gets its own screen-reader testing and semantic checks.
What we treat as urgent
One simple rule decides how fast we move.
You can't access the content at all — a page unreadable on a screen reader, a tool with no keyboard path, a video with no captions or transcript. This gets escalated the same day and blocks publication until it's fixed.
You can get to the content, but the experience isn't as smooth as it should be. This goes into the queue and gets handled in the next release.
Tell us what's not working
If something blocked you, we want to know now — not two weeks from now. Every report is read by a person.
Become an accessibility champion
Use assistive tech and want to help shape this directly? Say yes below. Champions get asked to test specific flows, are credited (with permission), and are looped in before each release.