Accessibility and ADA Statement

Last updated 8 August 2026.

Operated by Contra Holdings LLC, a Utah limited liability company. Drafted for attorney review and not legal advice.

We want PokerNight to be usable by everyone, including people who use screen readers, keyboard navigation, magnification, or reduced motion. A card game is a harder target than a text site, and we would rather tell you exactly where we are than claim more than we have earned.

Our target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We say aim to conform deliberately: no independent audit has been carried out, so we do not claim conformance. Where this statement and the actual site disagree, the site is the fact and we want to hear about it.

What we have actually done

All of the following was measured on the live site rather than assumed:

• Contrast is measured, not eyeballed. We sample rendered pixels and compute the ratio against WCAG 1.4.3. This matters more than it sounds: automated tooling cannot score text drawn as SVG and reports it as "incomplete", so the site passed automated checks for months while the four buttons on the home screen carried text as low as 2.02:1 against a 3.0 requirement. That is fixed, and the method that found it is now the method we use.
• The game is announced to screen readers. Live regions carry the running state of the hand: whose turn it is, what came down on each street, and who won. The your-turn message is assertive and interrupts, because it is the one message with a countdown attached to it and a queued notice behind three opponent actions is a folded hand.
• You are warned before the clock runs out. At 10 seconds and again at 5, the turn countdown is spoken. This is deliberately independent of the sound settings, because the audible countdown that already existed was doubly gated behind them, so anyone playing with site sound off got no warning at all before being folded.
• Cards have names. A card reads as "Ace of hearts", not as a bare letter with the suit rendered in a graphic the screen reader skips.
• Everything is reachable by keyboard, with a visible focus indicator, and every interactive control has an accessible name. Verified across the in-game surface, not just the home screen.
• Reduced motion is honoured. If your system asks for less animation, the boot sequence, chip effects, pot pulses and board transitions stand down.
• The statistics tables are real tables. Every figure is tied to its player and its column, so it reads as "Connor, net, plus 1,200" rather than as a bare number adrift from both. Sorting a column is a real button in the heading: it works from the keyboard, it says which column is sorted and in which direction, and it no longer throws away your place in the table when the figures refresh at the end of a hand.
• The charts say what they show. A chart is worth nothing to a screen reader if the only description names the axes, which is exactly what ours did. The chip-stack chart and the playing-style scatter each carry a written summary of the real data now: where every player started and finished, their high and low, and which style quadrant they landed in.
• Layouts reflow to 320px and to increased text size without horizontal scrolling or loss of content.
• Automated WCAG checks run at several viewport sizes, including the narrowest, as a floor under the manual work rather than a substitute for it.

Known gaps

These are real and we are not hiding them:

• The turn clock can only be switched off when you are the only person at the table. If every other seat is a bot, you can turn your own clock off in Settings, under Room, and nothing will fold you; it comes back by itself the moment another player sits down. At a table with other people in it, the clock is still the host's to set, and a player who needs longer depends on them. We think that is the right trade, because there the clock is the only thing stopping one player holding up everyone else, but it is still a limit and we would rather name it. You are warned at 10 and 5 seconds, and time banks extend the clock automatically. Separately, a table where no hand has been dealt for two hours is reclaimed either way.
• The bottom of a phone screen is crowded. The hero plate, the action dock, the button column and the powers block share roughly the bottom 150 pixels. It is legible and every control is reachable, but it is tight.
• In short landscape, a bet chip can overlap the action dock's header label. Measured, known, and not yet fixed because the fix risks more than the defect costs.
• Long nicknames are still visually shortened on the smallest screens. Assistive technology is unaffected, because the shortening is done with CSS and the full name is always present in the page and on hover.
• No independent audit has been done.

Legal framework

We treat the Americans with Disabilities Act, and Section 508 of the Rehabilitation Act where it applies, as the standard we are held to, and WCAG 2.2 AA as the practical measure of it. We are not claiming a certification, and we are not aware of any body that issues one for a site like this.

Telling us about a barrier

If something on this site stopped you, please tell us at accessibility@pokernight.win. Useful detail: what you were trying to do, what assistive technology and browser you were using, and the table code if it happened at a table.

We read every one of these, and a report that names a specific barrier is worth more to us than an audit. We will acknowledge within a few days and tell you honestly whether it is something we can fix quickly, something that needs rework, or something we have decided we cannot change and why.