Accessibility
RAMONET Ltd is committed to making liveslates.com usable by as many people as possible, including people who use assistive technology.
1. Conformance status
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. LiveSlates is currently partially conformant — most of the standard is met, but some parts are not. "Partially conformant" is the honest description; we have not claimed full conformance because the known gaps in section 4 would make that untrue.
2. How we've built it
Keyboard
- A skip-to-content link is the first thing you reach on every page, so you can jump past the navigation.
- A visible focus ring follows keyboard focus across buttons, links, inputs and custom controls. This is enforced by an automated test, because the underlying styling framework suppresses outlines by default.
- Menus and tab strips support arrow keys, Home/End, and Escape to return to the trigger.
- Sortable table headers are reachable and operable by keyboard, not mouse-only.
- Dialogs trap focus while open, close on Escape, and return focus to whatever opened them.
Screen readers
- Live-updating areas — scores, points totals, status changes — are marked as live regions so updates are announced rather than silently changing on screen.
- Tabs, sortable columns and expandable sections expose their state (selected, sort direction, expanded) programmatically, not just visually.
- Pages declare their language, and decorative images are hidden from assistive technology rather than read aloud.
Seeing and reading
- Body and muted text in light mode meets the AA contrast ratio. An automated test fails the build if a new low-contrast text colour is introduced.
- The interface has a dark mode, and respects your operating-system preference.
- Layouts are responsive and reflow rather than requiring horizontal scrolling when you zoom in.
Movement
- Animations — score flashes, transitions, the live ticker — are reduced or removed when your device is set to "reduce motion".
- Nothing on the site flashes more than three times a second.
3. How we test
Accessibility checks run as part of our automated test suite on every change, covering focus visibility, live regions, dialog behaviour, keyboard-operable controls and text contrast. These are backed up by manual keyboard testing.
This statement is based on a self-assessment. LiveSlates has not been audited by an independent third party, and we do not currently publish a VPAT.
4. Known limitations
We'd rather tell you where we fall short than let you discover it mid-slate. As of 21 August 2026 we know about the following.
- Some muted text is still below AA contrast. Colours set directly in stylesheets — as opposed to via our design system — have not all been corrected yet. This is in progress.
- Player-search dropdowns lack full combobox semantics. They are keyboard-operable, but a screen reader won't announce them as richly as it should.
- The live dashboard is dense and updates continuously. This is inherently demanding with a screen reader. It remains usable, but we don't claim it's a comfortable experience, and improving it is an ongoing piece of work rather than a solved one.
- JavaScript is required. The live-scoring interface can't function without it, so there is no non-JavaScript fallback.
- The mobile and tablet interface is in beta and has had less accessibility testing than the desktop one.
- Broadcast overlays and the TV channel view are excluded. These are designed to be captured by streaming software and displayed as video, so they are not intended for use with assistive technology. Every piece of information they show is also available in the main dashboard.
- Third-party content. Where we display data or media from other providers, we don't control its accessibility.
5. Tell us about a problem
If you hit a barrier anywhere on liveslates.com — something you can't reach with a keyboard, something your screen reader doesn't announce, text you can't read — please tell us:
- Email support@liveslates.com
- Or use the Feedback link in the footer when you're signed in
It helps if you can tell us the page, what you were trying to do, and what assistive technology or settings you were using — but report it even if you can't. We aim to respond within 5 working days.
If we can't fix something quickly, we'll tell you what the workaround is and when we expect to have it sorted.
6. Technical information
The accessibility of LiveSlates relies on HTML, CSS, WAI-ARIA and JavaScript. The site is designed to work with current versions of major browsers and, in combination with them, common assistive technologies.
7. Keeping this statement honest
This statement describes what is true today, not what we intend. It is reviewed when we make significant interface changes, and the known-limitations list is updated as items are fixed or new ones are found. If you find something here that no longer matches reality, that's a bug — please tell us.