Accessibility Statement
Last updated: 29 September 2026
This statement covers holisticquality.io. It says what we know about this site's accessibility, what we have not checked, and how to tell us about a problem.
Where this site stands
No full accessibility audit of this site has been done. We do not claim that it conforms to any accessibility standard, including WCAG 2.1, WCAG 2.2, Section 508 or EN 301 549.
What we have checked
- An automated review of the pages' HTML, run on 29 September 2026 with our own script. It reads the page files only. It cannot check how a page looks, how it works with a keyboard, or what a screen reader announces.
- Every text and link colour set in the stylesheet shared by the policy, regulator and research pages, and the bars beside formulas and code, measured against the background each one sits on. The thin divider lines were not measured, and neither were colours set inside individual pages rather than in that stylesheet.
We have not tested this site with a screen reader, with a keyboard alone, or with zoom and text resizing. Apart from the item below about the “page not found” page, colours set anywhere else, including the home page's own styles, have not been measured.
Changed in this update
- Every text and link colour in the shared stylesheet, and the bars beside formulas and code, now measure at least 4.5:1 against their background; the lowest is 4.56:1. Before this update, links in page text were shown in the browser's default colours, which measured 2.17:1, or 1.85:1 once visited.
- Every page now marks its main content as the main region, so screen-reader users can move straight to it.
Known issues
- The Regulator Agency Directory page skips a heading level (a level-1 heading is followed by a level-3 heading).
- The home page has no "skip to main content" link.
- The grey text on the "page not found" page measures 3.24:1 against its background, below 4.5:1.
Contact
If something on this site is hard or impossible for you to use, email safety@holisticquality.io. Please include the page address and what went wrong.