Legal
Accessibility statement
Last updated: 4 June 2026
Contents
Accessibility statement
Beta — provisional. gradIQual is in early beta. This statement reflects our current approach; we have not yet completed a formal third-party accessibility audit, and we will update it as we test and improve.
Last updated: 4 June 2026
Our commitment
We want gradIQual to be usable by as many teachers as possible, including those who rely on assistive technology. We design with clarity, readable type, and sufficient colour contrast as core principles, and we treat accessibility as part of building the product well — not an afterthought.
The law we follow
As a private service provider, we are not covered by the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, which apply to public-sector organisations. Our duty is under the Equality Act 2010, which requires service providers to make reasonable adjustments so disabled people can use their services. We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our working standard for meeting that duty.
Conformance target
We are working towards conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA — the current W3C standard, which incorporates WCAG 2.1. We have not yet completed a formal third-party audit, so we do not claim full conformance; we design to this standard and welcome reports of any barriers.
What we do
- Use clear, plain language and a calm, uncluttered layout.
- Maintain readable text sizes and accessible colour contrast, avoiding heavy gradients and relying on more than colour alone to convey meaning.
- Aim to support keyboard navigation and assistive technologies.
- Provide text alternatives for meaningful images.
Known limitations
We have not yet completed a formal audit, so we cannot yet publish a verified list of conformance gaps. As we test, we will list any known limitations here, with a plan and timescale to address them.
How we test
During development we use automated accessibility checks and manual keyboard testing. We are planning formal testing — including with screen readers — against WCAG 2.2 AA, and will update this statement with the results.
Feedback and contact
If you encounter an accessibility barrier using gradIQual or this website, please tell us — your feedback helps us improve. Contact security@gradiqual.com and we will respond as soon as we can, and make reasonable adjustments where we can.
If you are not satisfied
If you contact us about an accessibility barrier and are not happy with our response, you can get free, independent advice from the Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com, which advises on rights under the Equality Act 2010. (EASS covers England, Scotland, and Wales.)