Legal file
Accessibility Statement
The transfer desk is built to be readable and operable without a mouse, without colour perception and without animation.
Our approach
Spotlioopentral aims to meet the intent of WCAG 2.1 Level AA. Accessibility is treated as part of the editorial layout, not an add-on: dense dashboard views on desktop and a stacked transfer feed on mobile are both built from the same semantic structure.
What is implemented
- Semantic HTML landmarks: header, nav, main, section, footer, plus headings in logical order.
- A skip link to main content as the first focusable element on every page.
- Keyboard operation for the mobile menu, status tabs, rumor accordions, cookie controls and the correction form.
- Visible focus outlines that are never removed.
- Status meaning is carried by text as well as colour — every chip spells out confirmed, rumored, monitoring, advanced or rejected.
- Transfer direction is stated in words as well as arrows, so an arrow glyph is never the only cue.
- Data tables use captions, scope attributes and row headers.
- Images carry descriptive alternative text; decorative marks are hidden from assistive technology.
- Layout reflows at 1200px, 768px and 480px with no horizontal overflow, and wide tables scroll inside their own container.
- Reveal animations are subtle and are disabled automatically when a visitor requests reduced motion.
- Text sizing uses relative units so browser zoom and font-size preferences are respected.
Colour and contrast
The palette pairs deep navy with a paper background for body text, and reserves signal green, alert amber and deadline red for status emphasis. Chips place dark text on light fills or light text on dark fills so labels stay legible, and no information depends on distinguishing green from red.
Known limitations
- Very long club-and-player rows may need horizontal scrolling inside the confirmed-deals table on the narrowest screens.
- Some rendering differences may appear in older browsers that do not support modern CSS grid features.
Feedback
If a page blocks you, describe the page and the barrier through the correction form on the contact page. Accessibility reports are treated as priority editorial fixes.