Accessibility
Last updated October 17, 2026
ClassCake is played on a shared screen by a whole class, so it has to work for every student: the back row, early readers, students who use assistive technology, and students who see color differently. Our goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA.
What we do
- Readable type. Body text uses Atkinson Hyperlegible, a typeface designed by the Braille Institute so letters like I, l and 1 are easy to tell apart. Puzzle tiles are large enough to read from across a classroom.
- Strong contrast. Text is near-black on white or light tints, and every colored element has a thick black outline.
- Color is never the only signal. Right answers also show check marks, words and position changes, not just green.
- Keyboard friendly. Every button, tile and control can be reached and used with a keyboard, with a visible focus ring.
- Screen readers. Buttons have text labels, results are announced, and icons are hidden from screen readers when they are only decoration.
- No time pressure. No timers, no countdowns and unlimited tries.
- Less motion. If your device is set to reduce motion, ClassCake turns its animations off.
Known limitations
- Code Path shows its maze as a picture. Screen-reader users can still build and run programs, but the maze layout is easiest to follow visually; a teacher describing the grid works well.
Tell us
If something on ClassCake is hard to use for you or your students, please email david@classcake.com. We take every report seriously.