Accessibility Statement

LottoWise is committed to making lottery analytics usable by everyone, including people who rely on assistive technology.

Last updated: April 2026

Our commitment

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines are the internationally recognized standard for accessible web content and are the basis for accessibility laws in the US, the EU, Israel, and many other jurisdictions.

What we do

  • Semantic HTML — headings, lists, tables, and landmarks are used according to their meaning, not just for visual styling.
  • Keyboard navigation — every interactive element can be reached and activated from the keyboard, with a visible focus outline.
  • Color contrast — body text and essential UI meet or exceed WCAG AA contrast ratios, tested against our design tokens.
  • Screen-reader labels — buttons, form fields, and icon-only controls carry accessible names viaaria-labelor visually hidden text.
  • Right-to-left support — Hebrew (he) and Arabic-script locales render in RTL with mirrored layouts, correctdirand logical text flow.
  • Reduced motion — animations respectprefers-reduced-motionand degrade gracefully when motion is disabled.
  • Responsive text — type scales are set in relative units so users can enlarge text in their browser without breaking the layout.

Tested with

We periodically test LottoWise with:

  • NVDA and JAWS on Windows, with Chrome and Firefox.
  • VoiceOver on macOS (Safari) and iOS (Safari).
  • TalkBack on Android (Chrome).
  • Keyboard-only navigation, no mouse.
  • Automated tooling: axe-core, Lighthouse accessibility audits.

Known limitations

We are honest about where we are not yet perfect:

  • Some interactive data visualizations currently expose summary numbers to screen readers but not the full dataset. A tabular “view the data” alternative is planned.
  • A handful of older blog posts may contain images without descriptive alt text. We are backfilling these.
  • Some third-party embeds (e.g., payment processor iframes on paid plans) follow the third party’s own accessibility practices, not ours.

Report an issue

If you encounter an accessibility barrier on LottoWise, please tell us. We treat accessibility bugs as first-class issues and aim to respond within 5 business days.

When you report an issue, a short description of:

  • the URL,
  • the browser and assistive technology you are using,
  • and what you expected to happen

helps us reproduce and fix the problem quickly.

Reach the accessibility team at accessibility@lottowise.com.