World B-3The Beacon
Accessibility
Accessibility statement
I want everyone to be able to use this site, including the game. This page says what I have done, what I know is not perfect yet, and how to tell me when something is in your way.
Last updated 2026-09-24
The target is WCAG 2.1 level AA, the same standard used by the ADA and by most public bodies. The site is checked against it with automated tools on every build and by hand when pages change.
What is in place
- Every page and every door in the level is also a plain link, so nothing depends on playing the game.
- The whole site works with a keyboard: a skip link to the content, visible focus, arrow keys on the service and lab rosters, and Escape to close every menu.
- Text sizes use relative units and the layout reflows down to phone width with no horizontal scrolling.
- Color is never the only signal; every world's palette keeps body text above the AA contrast ratio.
- Animation, cutscenes and the walking character all switch off under the operating system's reduce-motion setting, and can be turned off in Settings too. Nothing flashes faster than three times a second.
- Images carry text descriptions, form fields have visible labels, and errors are announced next to the field.
- No content is locked behind sound; sound is off until you turn it on.
- The Davi chat bubble is a labelled button, the chat is a dialog that Escape closes, replies are announced to screen readers as they arrive, and everything it offers is also available on the contact page.
Known limitations
- The level itself is a canvas game and is not readable by a screen reader. Every destination is available as a link on the same page and in the menu, and the game can be skipped with one button.
- The pixel font used for small labels is stylised. Body text and anything longer than a few words use a standard typeface.
- The accounts feature depends on Google's sign-in pages, whose accessibility I do not control.
Tell me what is in your way
If any part of this site is hard to use, email me and say which page and what happened. I read every message and aim to fix accessibility problems within ten working days, usually sooner. Requests for content in another format are welcome too.
Email [email protected], or use the contact page.
How the site handles your data is in the privacy notice.