Legal
Accessibility statement
We want the 2026–27 season preview to be readable by everyone, on any device, with or without assistive technology.
Standard we aim for
nextstopbeacon.skin is built to align with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Accessibility is treated as part of the editorial build, not an afterthought.
Measures taken
- Semantic HTML landmarks: header, navigation, main and footer on every page.
- A visible “skip to main content” link as the first focusable element.
- One logical heading order per page, with no skipped levels.
- Keyboard operable navigation, tabs, accordions and cookie controls, with visible focus styles.
- Colour is never the only means of conveying a label: every tier is also stated in text.
- Text contrast checked against the navy, paper, green, amber and red palette.
- Decorative vector graphics are hidden from assistive technology; informative graphics carry accessible names.
- Fluid, responsive layout with no horizontal scrolling at 1200px, 768px and 480px breakpoints.
- Reveal animations are subtle and are suppressed when a reduced-motion preference is set.
- Content is text-based and can be zoomed to 200% without loss of function.
Known limitations
The power-ladder graphic uses bar length as a visual aid. Because bar length carries no data value, each row also states the ranking position and label in text, which is the authoritative version for screen reader users. Long tier tables are placed in a scrollable region on very narrow screens; the same information is available in the club profiles on the club index.
Assistive technology and browsers
The site is built with standard HTML, CSS and vanilla JavaScript and is intended to work with current versions of major browsers and screen readers. Core content remains readable if JavaScript is unavailable; only the mobile menu, tabs, accordions and cookie controls depend on it.
Reporting a barrier
If any part of this website prevents you from reading the season preview, please tell us. Include the page, the control involved and the browser or assistive technology you use. Reporting routes are described on the contact page. We treat accessibility reports as priority corrections.