Accessibility Statement

Last reviewed: April 11, 2026

StatsCentral is committed to making its website and platform accessible to everyone, including people with disabilities. We continually work to improve the user experience for all visitors and aim to conform to recognised accessibility standards.

1. Our Commitment

We believe that everyone deserves equal access to sports data and team management tools, regardless of ability. Our goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, as published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, and neurological disabilities.

2. Measures We Take

To support accessibility, StatsCentral takes the following measures:

  • Include accessibility as part of our design and development process.
  • Use semantic HTML to ensure content is meaningful to assistive technologies.
  • Provide sufficient colour contrast between text and background elements.
  • Ensure all interactive elements are operable via keyboard alone.
  • Use ARIA labels and roles where native HTML semantics are insufficient.
  • Provide visible focus indicators for keyboard navigation.
  • Avoid content that flashes more than three times per second to reduce seizure risk.
  • Write descriptive alt text for meaningful images; mark decorative images with empty alt attributes.
  • Ensure form fields have associated labels and clear error messaging.
  • Test with screen readers and keyboard-only navigation during development.

3. Conformance Status

We are working towards full conformance with WCAG 2.1 Level AA. Some areas of the platform are partially conformant, meaning some content does not yet fully conform to the standard. We are actively addressing these gaps and prioritise fixes based on user impact.

4. Known Limitations

While we strive for full accessibility, we are aware of the following limitations. We are actively working to resolve them:

  • Data tables — some statistics tables may lack complete row and column header associations for complex data sets. We are adding appropriate scope and headers attributes across these tables.
  • Third-party embedded content — certain widgets or media embedded from third-party providers may not fully meet WCAG 2.1 AA. We have limited control over third-party code but advocate for accessible alternatives where possible.
  • PDF documents — any downloadable PDF reports may not be fully tagged for screen reader compatibility. We are moving towards accessible, tagged PDF generation.
  • Interactive charts — data visualisations currently rely on colour to convey information. We are adding text-based alternatives and ARIA descriptions for chart data.

5. Supported Assistive Technologies

StatsCentral has been tested with the following assistive technologies. Other assistive technologies may also work, but have not been formally tested:

  • Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS and iOS)
  • Keyboard-only navigation
  • Browser zoom up to 200% without loss of content or functionality
  • High contrast mode (Windows and browser-level)

6. Technical Specifications

Accessibility of StatsCentral relies on the following technologies working in combination with your browser:

  • HTML5
  • CSS (including Tailwind CSS)
  • JavaScript (Stimulus / Hotwire)
  • WAI-ARIA

These technologies are relied upon for conformance with the accessibility standards applied.

7. Feedback and Contact

We welcome feedback on the accessibility of StatsCentral. If you encounter a barrier or have difficulty accessing any content or feature, please let us know so we can address it.

  • Contact form: Contact Us
  • Response time: We aim to respond to accessibility-related enquiries within 5 business days.

If you are not satisfied with our response, you have the right to contact the relevant enforcement body in your jurisdiction, such as the Equality and Human Rights Commission (EHRC) in the UK or the relevant national authority in your country.

8. Formal Assessment Approach

StatsCentral assesses the accessibility of the Service through the following approaches:

  • Self-evaluation by our development team against WCAG 2.1 AA success criteria.
  • Automated testing using accessibility scanning tools during development.
  • Manual testing with keyboard navigation and screen readers.
  • Periodic third-party accessibility audits as the platform evolves.

9. Formal Complaints

We are committed to resolving accessibility issues in good faith. If you are dissatisfied with our response to your accessibility concern, please contact us again and request escalation. We will engage constructively to find a resolution.