Research paper
Accessibility Standards for Casino Interfaces
Casino and sportsbook products combine dense lobbies, fast-moving odds, payment forms and safer play tools, and each part brings its own accessibility risks. WCAG 2.2 is the reference standard; legal duties differ by market.
In brief
- WCAG 2.2 is a W3C Recommendation; its current edition is dated December 12, 2024. Level AA is the usual target.
- United States: Department of Justice guidance from March 2022 says businesses open to the public must make online goods and services accessible, and treats WCAG as helpful guidance rather than a set regulation.
- Ontario: businesses and non-profits with 50 or more employees must make public websites meet WCAG 2.0 Level AA, apart from two captioning and audio description criteria.
- The highest-risk areas in casino products are forms, the cashier, status messages, color-only signals, small targets and moving content.
The legal picture by market
In the United States, the Department of Justice published Guidance on Web Accessibility and the Americans with Disabilities Act (ADA) on March 18, 2022. It says businesses open to the public "still must ensure that the programs, services, and goods" they provide online "are accessible to people with disabilities", and that the Department "does not have a regulation setting out detailed standards"; it points to existing standards such as WCAG as "helpful guidance". That guidance addresses businesses open to the public (Title III); the page now notes that it does not reflect the Department's April 24, 2024 rule for state and local governments.
In Ontario, under the Accessibility for Ontarians with Disabilities Act (AODA), the province's guidance states that "As of January 1, 2021, the AODA requires you to make all public websites accessible" for designated public sector organizations and for "a business or non-profit organization with 50 or more employees". Public websites and content posted after January 1, 2012 must meet the "WCAG 2.0 Level AA success criteria", except 1.2.4 (live captions) and 1.2.5 (pre-recorded audio descriptions).
The United Kingdom and Australia have their own equality and disability discrimination laws, which we do not summarize here. Whatever the market, WCAG 2.2 at level AA is the practical design target, because it includes almost all of the 2.0 and 2.1 criteria and adds new ones such as target size and accessible authentication. This page is not legal advice; check duties with counsel. See WCAG in the glossary.
Criteria that matter most in casino products
| Criterion | Level | Where it bites in a casino product |
|---|---|---|
| 1.4.1 Use of Color | A | Win and loss states, odds moving up or down, status badges |
| 1.4.3 Contrast (Minimum) | AA | Gray terms text on promotions, text over game artwork |
| 1.4.11 Non-text Contrast | AA | Toggle switches for limits, input borders, focus indicators |
| 2.1.1 Keyboard | A | Game lobby filters, cashier provider windows, date pickers |
| 2.2.1 Timing Adjustable | A | Session time-outs during sign-up or cashier steps |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Sticky bet slips, chat buttons and cookie banners covering focus |
| 2.5.8 Target Size (Minimum) | AA | Odds buttons, stake steppers and close icons on phones |
| 3.2.6 Consistent Help | A | Help and safer play links that move between pages |
| 3.3.1 Error Identification | A | Sign-up and deposit forms |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logins that block paste or rely on puzzles |
| 4.1.3 Status Messages | AA | Bet placed, deposit received, verification and withdrawal status |
Contrast and color
Criterion 1.4.3 requires "a contrast ratio of at least 4.5:1" for text, with large-scale text at 3:1. The W3C explains that 14 and 18 point are equivalent to approximately 18.5px and 24px, and that ratios "should not be rounded (e.g., 4.499:1 would not meet the 4.5:1 threshold)." Criterion 1.4.11 asks for 3:1 for interface components and meaningful graphics against adjacent colors. Casino brands often use dark backgrounds with colored text; test every pairing with the contrast checker, and read the contrast and signals field note on status colors.
Focus, targets and moving parts
Criterion 2.4.11 at level AA says that when a component "receives keyboard focus, the component is not entirely hidden due to author-created content." Sticky bet slips, chat launchers and consent banners are common causes. The keyboard paths field note walks a cashier step by step. Criterion 2.5.8 sets a minimum target of 24 by 24 CSS pixels with exceptions; the touch targets paper covers sizing on phones. For live odds and jackpot counters, WCAG's rules on moving and auto-updating content apply, and players need a way to pause or reduce updates.
How to test
- Run an automated checker on each template, knowing it catches only part of the problems.
- Complete registration, deposit, a bet or game launch, a limit change and a withdrawal using only a keyboard.
- Repeat with a screen reader on desktop and on a phone, listening for status messages.
- Zoom to 400% and check that content reflows without scrolling in two directions (criterion 1.4.10).
- Check every color pairing in the design system, including hover, focus and disabled states.
- Record each finding against a criterion with the accessibility observation log.
Questions
Is WCAG 2.2 a legal requirement for casino sites?
It depends on the market and the law. Ontario's AODA names WCAG 2.0 Level AA for larger organizations, while US Department of Justice guidance treats WCAG as helpful guidance under the ADA. WCAG 2.2 AA is the practical target because it covers the older versions and more.
Does an accessibility overlay make a casino site compliant?
An overlay script cannot fix inaccessible markup, missing labels or keyboard traps in the product itself. The fixes belong in the code and design system.
What should we fix first?
Start where barriers block money or safety: sign-up, verification, the cashier, safer play tools and withdrawals. A barrier there stops a player completely, while a barrier in a promotional banner is an inconvenience.
Sources
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, December 12, 2024.
- W3C WAI, Understanding Success Criterion 1.4.3: Contrast (Minimum), updated September 6, 2026.
- W3C WAI, Understanding Success Criterion 2.5.8: Target Size (Minimum), updated May 11, 2026.
- W3C WAI, Understanding Success Criterion 3.3.8: Accessible Authentication (Minimum), updated September 6, 2026.
- W3C WAI, Understanding Success Criterion 3.2.6: Consistent Help, updated March 9, 2026.
- W3C WAI, Understanding Success Criterion 4.1.3: Status Messages, updated May 11, 2026.
- U.S. Department of Justice, Guidance on Web Accessibility and the ADA (businesses, Title III), March 18, 2022.
- Government of Ontario, How to make websites accessible, updated September 21, 2026.
Every source was read on October 27, 2026. How we choose and date sources: data sources.