Accessibility Statement

We want StreetReport to be usable by everyone, including people who use screen readers, zoom, voice control, or who don't use a mouse. This statement describes where we are and how to tell us when we fall short.

Standard we aim for

Our target is WCAG 2.1 Level AA. We're not fully there yet; StreetReport is early in its life and some features are still being refined.

What works well

• All interactive controls on the public site, legal pages, and ticket pages are keyboard-reachable and have visible focus states.
• Text contrast on the default light theme meets AA for normal-sized text.
• The mobile app uses your phone's system text-size setting. If you increase it in Settings, the app follows.
• We don't rely on colour alone to convey status; status pills pair colour with a label and a dot indicator.

Known issues

• Crew-view pages use a high-contrast dark theme optimised for outdoor readability; that theme has not yet been independently audited for AA compliance.
• Map embeds rely on an external provider; we can't guarantee their accessibility. Coordinates and a text address are always shown alongside the map so you don't need to interact with the map itself.
• The in-app camera preview does not yet offer voice-guided capture; you can attach a photo from your library as an alternative.

How to tell us about a problem

If something stops you using StreetReport, tell us via our contact form with what you were trying to do and what happened. We treat accessibility issues as bugs and prioritise them accordingly.

Enforcement

If you're not satisfied with our response, you can contact the Equality and Human Rights Commission (EHRC); they are the UK enforcement body for the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. Note that StreetReport itself is a private service, not a public-sector body; but we hold ourselves to the same standard because the people we serve need us to.