Skip to the main content
AUTORISAccessibility

Accessibility

Accessibility statement

This platform serves people’s rights. If a page stops you exercising yours, that is a defect in the platform and not in you — and there is an address to say so, and another way to file what you came to file.

Report a barrier

Describe the page and what did not work. A screenshot is not needed.

accessibility@example.test

An answer within fifteen working days, saying what was done or when it will be.

Any procedure can be filed at a counter by an officer who enters it with you; their name is recorded on the file.

The standard

WCAG 2.2 level AA, and the jurisdiction’s own accessibility standard where one applies.

Where we are

This table says what has been checked and by what means. It is written to be replaced by an audit result, not by a softer sentence.

  • Automated check on every public page

    Checked

    axe-core runs on every journey in continuous integration and blocks release. An automated check finds about a third of accessibility defects: it is a floor, never a proof.

  • Every journey by keyboard alone

    Checked

    Each primary journey can be completed by keyboard, with no focus trap, a skip link, and a tab order that follows the reading order.

  • Colour is never the only signal

    Checked

    Every status carries a word as well as a colour, and every error state carries text. The rule is held by a closed vocabulary of classes, checked at build time.

  • Light and dark audited separately

    Checked

    Contrast is measured in each theme. Conformance in light says nothing about dark.

  • Translation fallback is visible

    Checked

    A sentence not yet translated is shown in the official language, followed by its language tag. No technical key ever reaches a screen.

  • Assisted filing at a counter

    Checked

    For people with no digital access at all, filing through an officer is a first-class journey rather than a workaround.

  • External audit

    Not yet

    No external audit has been commissioned to date. While this line is here, nobody outside has checked this platform, and this statement rests on our own testing alone.

  • Journeys with a screen reader

    Partial

    The structures — headings, regions, tables, status messages — are conformant and automatically tested. Complete journeys with NVDA, JAWS and VoiceOver, by people who use them daily, remain to be done.

  • Right-to-left scripts

    Partial

    The layout is written in logical properties and flips with the document direction. No right-to-left language is configured in any deployment yet: the support is structural and untested.

Known limitations

What we know is imperfect today.

  • Sealed documents are produced as PDFs, and their internal structure is not yet tagged for a screen reader. The same information is always readable as HTML on the file’s own page.
  • Wide tables scroll horizontally inside their own container. On a very small screen, reading them is still laborious.
  • An officer’s session expires after twelve hours. A draft in progress is kept, but a long form may need a fresh sign-in.

Audit result

No external audit has taken place yet. What is published here is the result of our own testing: the automated gate described above, run on every change, and the manual keyboard reviews the team carries out. We would rather say so than let anybody believe otherwise — this page is read by the people a false claim would harm.

The external audit is scheduled as part of going live. Its findings, including those that will not be fixed immediately, will be published here with their dates.