Skip to main content
2026 Championship · Round 2: Aragon on 5 July
24H ESPORTS2026
24H Series Esports — home24H SERIES ESPORTS2026 CHAMPIONSHIP
2026 SeasonPre-QR1 MOTEGIR2 ARAGON · LIVE in 5dR3 COTAR4 PORTIMÃOR5 ADELAIDER6 SILVERSTONE
Legal · Accessibility

Accessibility Statement

How we design and test 24hseriesesports.com for users of assistive technology — and how to tell us when something does not work.

Reviewed
30 Jun 2026
Standard
WCAG 2.2 AA
Audit
axe + Lighthouse

Our commitment

WSR Group Ltd. wants 24hseriesesports.com to be usable by everyone, regardless of how they access the web. We design and build this site with accessibility as a first-class concern, not an afterthought.

This statement is published under the European Accessibility Act (in effect since 28 June 2025) and as a record of our compliance posture under WCAG 2.2 AA.

Conformance status

This website is designed to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 AA is also the standard referenced by the EU Web Accessibility Directive and the European Accessibility Act.

We say "designed to meet" rather than "fully conforms with" because no public website is ever finished: new content goes live every race weekend and there is always a window between a regression slipping in and us spotting it. The compliance posture below describes the controls we run to keep that window short.

How we test

  • Automated: every routable page on the site is covered by an axe-core test that runs in our continuous-integration pipeline. Pull requests cannot be merged if these tests fail.
  • Lighthouse: the same routes are audited by Lighthouse CI on every pull request, on both mobile and desktop. The accessibility category is gated at a score of 0.85 or higher; below that, the build fails.
  • Manual review: keyboard navigation, focus order, and screen- reader landmarks are reviewed during design reviews and at each milestone.
  • Annual audit: we plan to commission a third-party accessibility audit annually. The first one is scheduled for 2027.

What we have done

  • The site uses semantic HTML landmarks (<header>, <nav>, <main>, <footer>), a "skip to main content" link, and a clear heading hierarchy on every page.
  • Interactive elements have visible focus states and are operable from the keyboard.
  • Modal dialogs (the recap lightbox) trap focus, close on Escape, and lock background scroll while open.
  • Carousels expose tablist semantics, support keyboard navigation, and fall back to a static view when prefers-reduced-motion is set.
  • Animations respect prefers-reduced-motion. The Lenis smooth- scroll module is not loaded at all when reduced motion is preferred — the browser's native scroll is used instead.
  • Standings and results tables use proper <th scope> markup. The mobile card-grid view preserves the underlying table semantics for assistive technology.
  • Flag icons next to driver names are marked as decorative when the country name is already visible alongside; otherwise they expose an aria-label with the country name.

Known limitations

We are aware of the following areas where the experience may not be ideal. We do not believe they constitute WCAG 2.2 AA failures, but we want to be transparent about them.

  • Embedded YouTube broadcasts use the standard YouTube embed player. Its accessibility is provided by YouTube and is outside our control. Captions are available where the broadcast team has published them.
  • Third-party content (the Google Form for driver registration) follows Google's accessibility design, not ours.
  • Class-colour pills (GT3 green, PCUP blue, GT4 amber) are used decoratively alongside text labels. Colour is never the only channel conveying information, but the colour-to-class mapping is also documented on /rules for users who want a textual reference.

Tell us if something does not work

If you find a barrier — a control you cannot operate, content you cannot read, a flow that breaks with assistive technology — please write to us at info@worldsimracing.com and include:

  • the page or feature that did not work,
  • what you expected to happen,
  • what actually happened,
  • your assistive technology and browser, if you know them.

We aim to acknowledge feedback within five working days and to fix clear accessibility issues within 30 days where it is technically possible to do so.

Enforcement

If you are not satisfied with our response, you can contact your national enforcement body. In the United Kingdom, that is the Equality and Human Rights Commission (equalityhumanrights.com). In the EU, the relevant body is the equivalent in your member state.

Standards we follow

Updated

This statement was last reviewed on 30 June 2026.