Accessibility in casino UI: contrast, motion, one-handed play and reading order
A slot is, by design, a screen full of motion, colour and small text — nearly every accessibility failure mode in one product. That is not a reason to give up on accessibility; it is a reason to be specific about which parts of the experience must work for everyone and which parts are the art.
Last reviewed: 21 September 2026 · Author: Rory Finch
Separate the frame from the game
The most useful distinction in casino accessibility is between the frame — lobby, bet panel, balance, info screens, deposit and withdrawal flows, responsible-gambling tools — and the game surface, the reels and animations themselves. The frame is a normal web interface and there is no excuse for it to fail basic standards. The game surface has genuine constraints, but far fewer than teams assume.
Everything a player must be able to do — read their balance, change the stake, stop, set a limit, withdraw, find help — lives in the frame. Start there.
The frame: a checklist that fits on one screen
- Text contrast of at least 4.5:1 for body text and 3:1 for large text (WCAG 2.x AA). Balances and stakes rendered in thin gold on dark blue routinely fail this; it is the first thing to fix because it is the money.
- Touch targets of at least 44×44 points for stake +/- buttons, spin, and the responsible-gambling controls. Tiny stake steppers cause mis-taps that cost real money.
- Focus order and labels. Every control reachable by keyboard and named for screen readers: "Increase stake to £2", not "button".
- One-handed reach. The spin control, stake and balance within thumb reach on a phone held in one hand; the menu can live at the top.
- Reduced motion respected for the frame: no parallax in the lobby, no pulsing promotion cards when the system setting asks for less motion.
- Live regions for balance changes so that a screen reader announces "balance £48.20" after a spin without the player hunting for it.
None of this touches the art.
The game surface: what can reasonably be done
- Win presentation in text, not only in colour and motion. "Won £3.20" as a readable line alongside the animation. This also happens to serve the GB rule that a return below the stake must not be celebrated as a win — text is easier to make honest than fireworks. See designing within RTS 14.
- A reduced-motion mode for the reels: shorter animations, no screen shake, no strobing on big wins. Strobing above three flashes per second is a seizure risk under WCAG and should not exist in any mode.
- Symbol legibility. Symbols distinguishable by shape and not only by colour; a paytable that names them.
- Audio independence. Nothing that matters conveyed only by sound — the mute majority already lives this way, so the design is usually there already.
Reading order and the info screen
Info screens are frequently images of text exported from the studio's design tool — invisible to screen readers and unscalable. Rules, paytable and the RTP disclosure should be real text. In Great Britain the disclosure is mandatory; an image of it arguably fails the "easily available" test as well as accessibility.
Cognitive load is an accessibility issue too
The product is used by tired people on small screens who may be anxious about money. Plain language in the bet panel ("Bet £1 per spin", not "Stake 1.00 · Lines 20 · Coin 0.05"), a visible net position, and limit-setting that is not hidden under three menus are accessibility features by any sensible definition — and in GB the net-position display is also a rule.
What to test with
Real devices with the system accessibility settings on: larger text, reduced motion, a screen reader, and one-handed use. Fifteen minutes of that on the deposit flow finds more than an hour of automated scanning.
Quick answers
Will accessibility make the game look worse? The frame will look better; clarity generally does. The game surface keeps its art and gains a reduced-motion option that many non-disabled players will also switch on.
Is there a legal requirement? There is no gambling-specific accessibility standard. The Equality Act 2010's duty on service providers to make reasonable adjustments applies to online services in general, and in Great Britain the mandatory game information has to be readable to count as "easily available" under RTS 3.
Where to start? Contrast on money figures, touch targets on stake controls, text alternatives for wins. One sprint.
Standards referenced: WCAG 2.x success criteria for contrast, target size, motion and flashing. Figures such as 4.5:1 and 44×44 are the standard's values; everything else is practice.