TryCasino.info

Accessibility statement

This page describes the accessibility work already in place, what is still imperfect, and how to tell us about a problem.

We aim for WCAG 2.1 Level AA across the site. Where we fall short, tell us and we will fix it.

Our commitment

TryCasino.info should be usable by as many people as possible, including people who navigate by keyboard, use a screen reader, need larger text, or cannot tolerate motion. We treat accessibility as part of the build, not as a later patch.

What we have implemented

  • Structure: one H1 per page, headings in a logical order, landmark regions, and a skip link as the first focusable element.
  • Contrast: body text and interface controls meet or exceed 4.5:1; large headings exceed 3:1 against the felt-green and brass palette.
  • Keyboard: all links, buttons, form fields and disclosure widgets are reachable and operable without a mouse, with visible focus outlines.
  • Images and icons: decorative SVG is marked aria-hidden; informative images carry text alternatives.
  • Forms: every input has a programmatically associated label, and errors are described in text rather than by colour alone.
  • Motion: animations respect prefers-reduced-motion.
  • Zoom: the layout reflows at 200% zoom and at 320px width without horizontal scrolling or loss of content.
  • Tables: data tables use real <th> headers with scope attributes and a caption.

Known limitations

  • Ad slots, when enabled, are supplied by third parties whose markup we cannot fully control. We constrain their dimensions to prevent layout shift, but we cannot guarantee the accessibility of third-party creative.
  • Operator product screenshots are not embedded; where a visual would help we describe it in text instead, because we cannot guarantee the alt text of a captured interface.
  • Older archived pages that we have migrated may still carry legacy markup. We are working through those.

Assistive technology we test with

We check pages with keyboard-only navigation, a screen reader on current Windows and macOS builds, browser zoom to 200%, and automated contrast checks. Testing is manual and periodic rather than continuous, so gaps can appear between reviews.

Feedback

If you hit a barrier, contact us through the contact page and describe the page, the assistive technology you were using, and what went wrong. We aim to respond within five working days and to ship a fix in the next content cycle.