Accessibility

This statement covers these public pages and the sign-in page. It says what we have done, and — more usefully — what we know is not yet good enough.

What we have done

• Every page can be used with a keyboard alone. The focus outline is deliberately heavy so it is visible on a cheap screen in daylight.
• Text and background colours were checked against the WCAG 2.2 AA contrast thresholds. The lightest grey used for text on white measures 6.0 : 1; the required minimum is 4.5 : 1.
• Headings are in order and describe the section they open, so a screen reader can be used to move around a page rather than read it end to end.
• Text reflows to a narrow screen without a sideways scrollbar, and stays readable when the browser text size is increased.
• No page moves, flashes or animates by itself. Where a browser would animate, the preference for reduced motion is respected.
• No font is downloaded and no script is loaded from another company, so the pages work on a slow connection and behave the same offline in a cache.
• Colour is never the only way something is indicated.

What is not good enough yet

Being specific here is more useful than a claim of full compliance.

• The training slide decks are not accessible. They are PowerPoint files produced for in-person sessions and they have not been checked for reading order, alternative text or contrast. If you need the content in another form, ask us and we will provide it.
• The integration guide is one very long page. It has a heading structure and it can be navigated with a keyboard, but its length makes it tiring with a screen reader. It is written for developers rather than for the officers this site mainly serves.
• The signed-in dashboard is not covered by this statement. It is a larger application and it has not yet been assessed. We are not going to claim otherwise.
• These pages have not been tested with assistive technology by disabled users. They have been built to the standard and checked automatically. That is not the same thing, and we would rather say so.

Telling us about a problem

If something here is unusable for you, tell us. Say which page and what happened. A short description of what you were trying to do is more useful than a technical diagnosis, and you do not need to know the name of anything.

We will reply, and we will say honestly whether we can fix it soon or not.

The standard we are working to

Web Content Accessibility Guidelines version 2.2, level AA. Where this site does not meet it, the gaps are the ones listed above.

Prepared 2026. This statement is revised when the site changes.