Legal
Accessibility Statement
Last updated: 5 July 2026
This statement applies to the ProQuoter web application and marketing website at proquoter.co.uk. We want as many people as possible to be able to use ProQuoter, whatever their abilities.
1. Our commitment
ProQuoter is designed and built to meet level AA of the Web Content Accessibility Guidelines (WCAG) 2.2. Accessibility is treated as an ongoing responsibility, not a one-off exercise — we consider it when we design and build new features.
You should be able to:
- navigate the app using a keyboard alone
- skip repeated navigation and go straight to the main content of each page
- use the app with modern screen readers
- see clear, visible focus indicators as you move through controls
- have your operating system’s “reduce motion” preference respected
2. How accessible this software is
We consider ProQuoter to be substantially compliant with WCAG 2.2 level AA. The application is built with semantic HTML, uses ARIA where native semantics are not sufficient, sets the page language, provides text alternatives for images, associates labels with form fields, and provides visible keyboard focus.
Some parts of the software have not yet been independently audited against every success criterion. Where we are aware of gaps, we list them below and are working to resolve them.
3. What we have done
- Interactive controls are real
<button>and link elements, not click handlers on non-interactive elements. - A “Skip to main content” link is the first focusable element on every page.
- The page language is set to English (
lang="en-GB"). - Images have text alternatives; decorative images are correctly hidden from assistive technology.
- Form fields have associated labels; icon-only controls have accessible names.
- Dialogs and menus expose their state (open/closed, selected, pressed) to assistive technology.
- Visible focus styles are provided for keyboard users throughout the app.
- The
prefers-reduced-motionsetting is respected to reduce non-essential animation.
4. Known limitations
We are aware of, and working on, the following areas. We have not yet completed a full independent WCAG 2.2 AA audit covering every criterion:
- Colour contrast has not been formally verified against every UI state and theme.
- A complete manual screen-reader pass across every workflow is still in progress.
- Some complex, data-dense screens may not yet be fully optimised for assistive technology.
If you find a problem that is not listed here, please tell us — see “Reporting problems” below.
5. Assistive technology
ProQuoter is a web application and works best in an up-to-date browser. We aim to support recent versions of common assistive technologies, including screen readers and browser zoom / text resizing. If a particular combination does not work for you, let us know so we can investigate.
6. Reporting problems
We are always looking to improve the accessibility of ProQuoter. If you experience any difficulty using the software, or need information in a different format, please contact us and we will do our best to help:
- Email: support@proquoter.co.uk
Please include the page or feature you were using and a description of the problem. We aim to respond within 5 working days.
7. Enforcement
If you contact us with a complaint about accessibility and are not happy with our response, the Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations in the UK. You can contact the Equality Advisory and Support Service (EASS).
8. How this statement was prepared
This statement was prepared based on a review of ProQuoter’s codebase against WCAG 2.2 level AA, covering semantic structure, keyboard operability, focus management, text alternatives, form labelling, and motion preferences. A full independent audit has not yet been completed; this statement will be updated as further testing is carried out and issues are resolved.
See also our Privacy Policy and Terms of Service.