Access

Accessibility

JackpotDesk should be usable with a keyboard, a phone, and assistive technology. We have not claimed a full WCAG audit. If something blocks you, we want the specific page and what you were trying to do.

What is in place

• Semantic headings, labels on form fields, and a named primary nav.
• FAQ uses native details/summary controls.
• Map state tiles are keyboard-focusable buttons with text names.
• Color is not the only signal on expected value (plus/minus amounts are labeled in text).
• On a phone, primary tabs sit in a bottom bar with larger tap targets.
• Form fields use 16px type so iOS does not zoom the page on focus.

Known limits

The US cartogram is an SVG of abbreviations. A screen reader gets each state’s name and value, but the spatial layout is visual. Pool member rows on a wide screen are a table; on a phone they stack as cards.

Report a barrier

Open an issue on the project’s GitHub repository and describe the page, the device or assistive tech, and what failed. Legal pages on this site are static HTML so they remain readable with JavaScript off.