The standard we build to, the specific decisions behind it, how every build is checked before it is published, and how to tell us something is broken. A real contact route, read by the people who can change the code.
Buzzing Bees Playland, LLC · 203 West 111th Street #5B, New York, NY 10026 · hello@bbplayland.com · Effective 19 October 2026
Built to be read by everyone — true on every build
- Body type is Atkinson Hyperlegible, a face designed for low-vision readers; text is ink on chalk at 7:1 contrast or better, never grey.
- Touch targets are 44px or larger everywhere, and 48px anywhere a child taps; pinch-zoom is never switched off.
- Every animation stops under reduced motion, and the still version is a designed state, not a broken one.
- Every build is checked against WCAG 2.1 AA before it can be published; a build that fails does not ship.
The standard we build to
WCAG 2.2 AA as a floor, with two places we deliberately exceed it.
Contrast. Body text is at least 7:1 against its background rather than AA’s 4.5:1, and large text and controls at least 4.5:1 rather than 3:1. A meaningful share of our readers are on a shared school device with a scratched screen in a bright room, and AA is calibrated for better conditions than that. Where text sits on a painting, the painting under every line is measured too.
Target size. 44 pixels minimum on this site, and 48 anywhere a child touches. AA asks for 24.
Specific decisions
The body typeface is Atkinson Hyperlegible, designed by the Braille Institute with letterforms that are deliberately hard to confuse with one another. It was chosen for that and not for how it looks.
Grey text does not appear anywhere. Where text needs to recede it is the same ink at reduced strength, and the two levels that are allowed to carry words were picked because they still clear the contrast floor — not by eye.
Pinch-zoom is available on every page. It is switched off by default in a lot of mobile-first work, which is a WCAG failure that is easy to ship and hard to notice.
Every animation stops under prefers-reduced-motion, and the reduced version is a designed state rather than a switched-off one: the worlds hold still, the door on the front page stands open, and nothing a reader needs is carried by motion alone.
Every page has one heading at the top, a main landmark, a skip link that reaches it, and a focus order that follows the visual order. Every control has a name a screen reader can say, every form field is labelled, and nothing is given a positive tab index.
In Archie itself, a child can have the story and the intro read aloud, and Archie’s hints are on screen as text, so a reader who cannot hear is never behind.
How every build is checked
Before a build of this site can be published, an automated audit runs against the built pages: every document declares its language; every image has alt text; every button and link has an accessible name; every input is labelled; heading levels never skip; no id is duplicated; every page has a main landmark and a working skip link; zoom is not disabled; every piece of text meets the contrast floor, including text set over the paintings; and axe-core checks 18 routes against WCAG 2.1 AA. A build that fails any of these does not ship. The same is true of the automated privacy checks, so accessibility and privacy are held to the same standard: a property of the build, not a promise.
Testing by a person — with a screen reader, magnification and keyboard-only use — is scheduled before the first classroom pilot, with the sign-in flow and the course player first, because those are where an automated check can pass while a real reader is lost. What that testing finds is fixed before the pilot, and reported here.
Telling us something is broken
Email accessibility@bbplayland.com. It reaches the people who can change the code rather than a support queue, and we answer within five working days.
Useful things to include if you have them: the page, what you were trying to do, and what you are using to read it. None of them are required — “the schools page is unusable with a screen reader” is a perfectly good report and we would rather have it than nothing. This statement is effective from 19 October 2026 and is updated with each release.