Accessibility Statement

01Our commitment

We want ProveCONSULT to be usable by everyone who needs it, including people who rely on screen readers, magnification, voice control or keyboard-only navigation. We treat reported accessibility barriers as defects to fix, not feedback to file.

02The standard we work to

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across the public pages and the signed-in application. We do not currently claim full conformance: ProveCONSULT has not yet been independently audited against WCAG, and we would rather say so plainly. Our own review in October 2026 found and fixed a number of issues (listed below). This statement will be updated as our position firms up.

03What we have in place

• A “Skip to main content” link as the first thing on every page, shown when it has keyboard focus.
• Semantic page structure with headings, landmarks and labelled form controls.
• A clearly visible focus outline on every link, button and form field, in light and dark themes.
• Text, and the borders of form fields, at or above the WCAG AA contrast ratios.
• Error messages that screen readers announce when they appear; on the sign-in and account forms they are also linked to the fields they concern.
• Accessible names and states on interactive controls such as menus, dialogs, toggles and the formatting buttons of the text editor.
• Light and dark themes, following your system setting or chosen manually.
• Layouts that reflow for small screens and support browser zoom.
• Text alternatives on informative images.
• Automated checks on every change: accessibility lint rules on the code, and an automated scan of the signed-out pages and the main signed-in pages. Automated tools find only some problems, so they support, not replace, testing by people.

04Known limitations

We know about the following and are working through them. If you find something not listed, please tell us.

• The signed-in application has not been fully tested with screen readers; some large tables and interactive controls may not announce their state completely.
• The automated scan covers the main signed-in pages, not every screen; the rest are checked by code review.
• Some data-dense views use colour badges whose non-visual equivalents we have not yet verified everywhere.
• The rich-text editor (event notes, emails and letters) is now labelled for screen readers, but has not been tested with every assistive technology.

05Documents and exports

ProveCONSULT produces Excel workbooks, Word reports (such as the Report on Consultations) and PDF copies of emails and notes. We have not yet verified these files as accessible documents. The PDF copies of emails and notes are produced by a headless Chromium browser, which tags its PDF output by default, so they carry a basic reading structure; email PDFs have no heading structure, and we have not tested them with a screen reader. Documents you or others upload (for example, letters and information sheets) are stored and shared exactly as uploaded, so their accessibility depends on the original file. The same information is available in the application, and we can help with an alternative format on request.

06Feedback and assistance

If any part of ProveCONSULT is difficult or impossible for you to use, or you need content in another format, contact us and we will work with you to resolve it.