Accessibility

• Use semantic page structure, headings, labels, and keyboard-operable controls where practical.
• Check colour contrast, focus visibility, responsive layout, and reduced-motion behaviour during development.
• Keep forms labelled and show validation errors near the relevant fields.
• Review public pages on desktop and phone-sized screens before release.
• Treat accessibility defects as product defects and record them for remediation.

The site changes often, and some pages, embedded services, authentication flows, or experimental product areas may not yet meet every WCAG 2.2 AA success criterion. We will update this page as audits, fixes, and known limitations become more specific.

If you encounter an accessibility issue on this site, please report it through the contact form. Include the page URL, what you were trying to do, your browser or assistive technology if relevant, and a short description of the problem.

We welcome accessibility feedback from users, accessibility consultants, and members of the community. We read accessibility reports and prioritise fixes based on severity, reach, and available engineering capacity.