Our approach
We aim to follow WCAG 2.2 Level AA. We consider page structure, readable content, colour contrast, keyboard use, mobile layouts, visible focus, form labels and reduced motion. An accessibility widget can be helpful, but it does not replace an accessible website.
Accessibility tools
UserWay can be loaded from the button below, or it loads automatically after you allow preference cookies. The cookie button at the lower left only opens cookie settings; it does not load UserWay. The header also has a light and dark appearance switch. If your device is set to reduce motion, decorative movement is turned off.
What you should be able to do
- Navigate the site using a keyboard.
- Zoom or enlarge text without losing essential content or controls.
- Use clear headings, landmarks, labels and link descriptions.
- Reduce motion through your operating-system preference.
- Choose high contrast and more generous text spacing.
Known limitations
We do not claim that every page fully meets WCAG 2.2 AA. Manual testing with different keyboards, screen readers and devices is ongoing. Third-party websites linked from our project pages are outside our control.
Report a problem
Email [email protected] or call 020 456 91 456. Describe the page, the problem and the technology you were using if you are comfortable doing so.