Accessibility statement
We aim for a clear, keyboard-friendly and responsive service. Accessibility is treated as an ongoing product requirement, not a one-time claim.
Current support
The interface uses semantic headings, labelled form controls, visible focus states, responsive layouts, text alternatives for controls, status announcements, and contrast-aware light and dark themes.
Known limitations
A formal WCAG audit, screen-reader matrix, zoom and reflow audit, and testing with disabled participants remain required before public launch.
Report a barrier
Use the contact form and choose Trust and safety or Something else. Describe the page, device, browser, assistive technology, and the task you were trying to complete.