Accessibility Statement

Someone using RoadResQ may be standing at the roadside at night, on a cracked phone screen, in a hurry. Accessibility is not a separate feature here; it is most of what makes the site usable at all.

The standard being aimed at#

RoadResQ targets WCAG 2.2 Level AA.

What has actually been built#

Keyboard#

Everything you can do with a pointer, you can do with a keyboard. Focus is always visible — the focus outline is never removed anywhere in the codebase — and the tab order follows the order of the page. A skip link jumps straight to the main content.

Forms#

Every input has a real label attached to it, not placeholder text pretending to be one. Error messages are tied to their field and announced rather than only appearing in red. Inputs are sized so that iOS Safari does not zoom the viewport when you tap into one and strand you mid-form.

Status and colour#

Status is never carried by colour alone. Every status pill, freshness label and alert includes its meaning in words, so it reads the same whether you are colour blind, in direct sunlight, or using a screen reader.

Contrast#

The colour palette is checked by an automated contrast test that runs against the design tokens in the codebase. Two colours were darkened and one lightened during the build specifically because they failed it.

Motion#

Motion is minimal and every animation respects prefers-reduced-motion. Nothing autoplays, nothing loops forever, and there is no video that starts on its own.

Zoom and small screens#

The site works down to a 320px-wide screen with no horizontal scrolling, and survives text zoomed to 200%. Pinch-to-zoom is never disabled — that is an accessibility feature, and a roadside customer may well need it.

Touch targets#

Interactive controls clear a 44px target, and the emergency action is deliberately larger than everything else on the page.

Maps#

There is a manual alternative to every map interaction. You can type an address instead of dropping a pin, and a ResQ can be created from typed information with no map involved at all. When map tiles are not configured, the map is absent and the page says so rather than showing an empty grey box.

Known limits#

Being honest about the gaps:

• A map is inherently visual. The supported alternative is the manual address path, which is a complete path — but it is an alternative, not an equivalent experience.
• Live location freshness is conveyed in words as well as colour, but the underlying idea — a position that is a few minutes old — is harder to convey briefly than a coloured dot.
• Not every combination of screen reader, browser and operating system has been tested. Testing has been done, but "we tested everything" would not be true.

Telling RoadResQ about a problem#

If something on this site does not work for you, report it using the contact details at the foot of this page. Useful things to include:

• The page you were on.
• What you were trying to do.
• What happened instead.
• The browser and any assistive technology you were using.

Accessibility reports are not treated as complaints to be managed. They are bug reports, and they get fixed.

Another way in#

You can always call instead. If the website is not working for you for any reason, a phone call reaches a person who can take the details directly.

Standard referenced#

Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C.

When this statement changes#

Changes are published as a new version with its own date, and the old version stays readable.