18+ — for entertainment only. No real money play. No prizes of monetary value.

Sign in Join free
Accessibility

A hall everyone can get into

An evening at these tables should not demand sharp eyesight, a steady mouse hand or patience for flashing lights. This page says plainly where we stand against WCAG 2.2 AA.

Last reviewed 6 October 2026

1. What works today

  • Keyboard. Every control — navigation, forms, stake steppers, the games' main actions — is reachable and operable by keyboard, with a visible focus ring throughout.
  • Contrast. Body text sits well above the 4.5:1 AA line against the dark timber background, and interface states do not rely on colour alone.
  • Reduced motion. With your system's reduce-motion setting on, the drifting dust, the ticker, meter sheens and celebration effects all stand down; games settle instantly instead of animating.
  • Structure. Pages carry one heading hierarchy, landmarks, labelled forms and alt text on meaningful images; decorative art is hidden from assistive tech.
  • Sound. Entirely optional, off-switchable on every game, and never the only signal for anything.
  • Zoom. Layouts hold together at 200% zoom and on small screens without sideways scrolling.

2. What falls short, honestly

  • The reel animations convey their outcome visually first; screen-reader users get the result text, but the moment-to-moment theatre is visual.
  • The wax-seal rubbing gesture needs a pointer; an activate-to-reveal fallback is on the list.
  • Win announcements are polite live regions, which some reader and browser pairings occasionally swallow.

3. The games and photosensitivity

No content flashes more than three times a second, and celebration effects favour drift over strobe. If any sequence feels wrong to you, tell us which game — that report goes to the top of the queue.

4. How we test

Keyboard-only passes and automated checks run on every release; screen-reader passes (VoiceOver and NVDA) run on the shell and each game before it ships. Accessibility bugs are triaged as functional bugs, not polish.

5. Tell us where it fails you

If any part of the site is hard or impossible for you to use, write to us or email hello@cedarvaux.com with Accessibility in the subject. Concrete reports — page, action, tool you were using — get fixes, and we will tell you when yours lands.

6. The formal bit

We aim for WCAG 2.2 AA across the site. This statement covers cedarvaux.com and was last reviewed on the date above; it is revisited whenever a game or a major feature ships.