Accessibility statement

How the application is built

• Semantic headings, one h1 per page, and labelled form fields.
• A skip link to the main content, and visible keyboard focus styles throughout.
• Every image carries alternative text.
• Text inputs render at 16px or larger, so mobile browsers do not zoom unexpectedly when a field is focused.
• Responsive from 390px upwards with no horizontal scrolling, checked automatically on every release.
• Project selection uses a native radio group, operable by keyboard.
• The journey works without JavaScript-driven AI: no stage depends on a model response.

What has been tested

Automated checks run on every release and cover heading structure, image alternatives, page metadata and mobile layout overflow. The full participant journey is exercised end to end in a real browser.

Known gaps

We would rather name these than imply a level of conformance we have not verified:

• No formal automated WCAG 2.2 audit has been run.
• No manual screen-reader testing has been carried out.
• Colour contrast has not been measured against WCAG ratios across every component.
• There is no published conformance claim. Do not treat this as a WCAG 2.2 AA statement.

If something does not work for you

Tell the facilitator running your session. The journey can be completed on paper alongside the tool, and no part of the session depends on being able to use the application.