A clearer, more accessible experience.
WCAG 2.2 AA is the target. We do not claim a completed independent accessibility audit.
Designed for different ways of working
The interface uses semantic page regions, keyboard-operable links and form controls, visible focus indicators, labelled fields and responsive layouts. Light and dark appearance respect your system setting, with a manual toggle. Reduced-motion settings suppress transitions.
Forms and technical language
The reporting workflow has four parts: Start, Your report, Evidence, and Review & send. Optional details can stay collapsed. Validation explains errors in plain English, and Back preserves answers and selected evidence. Contact information is optional. We do not require an account, payment or wallet connection.
Known verification limits
Assistive technology, browser zoom, screen-reader announcements, focus movement, mobile devices and anti-abuse challenge accessibility need manual testing before production release. No automated score proves that every user can complete a task.
Tell us about a barrier
Use the general enquiry channel listed on the contact page. Describe the page, browser or assistive technology and the barrier using fictional information. Do not include confidential case evidence in an accessibility message.
We never request wallet access, private keys, recovery phrases or a recovery payment.
Confidential reporting availability