Accessibility Statement
Built to be usable by everyone. Still a work in progress.
Disability inclusion and accessibility are the first strategic pillar of Vantercor’s own work — so this site has to meet the standard we ask other organizations to meet. This page is a plain account of where it stands: what’s been done, what hasn’t, and how to tell us when something doesn’t work.
Conformance target
WCAG 2.1, Level AA — partially conformant
Vantercor.org is built to meet the Web Content Accessibility Guidelines (WCAG) 2.1 (opens in a new tab), Level AA. We describe our status as partially conformant: a full code-level audit has been completed and real issues were found and fixed, but the site has not yet been tested by people who use assistive technology day to day, which is the only way to be fully confident a site works in practice, not just on paper.
We’re publishing this statement now, honestly, rather than waiting for a perfect score before saying anything at all.
Every claim on this page reflects where the site actually stands today, not where we intend it to end up.
What’s been done
A full code-level accessibility audit.
Every page was checked against WCAG 2.1 AA criteria — not a generic checklist, but computed and verified against the site’s actual code. Real problems were found and fixed, including:
Colour contrast
Every text and background colour pairing was checked against the required 4.5:1 (text) and 3:1 (focus indicators) ratios. Five failing pairs were found and corrected.
Heading structure
Every page was checked for a single, correctly nested heading structure, so the page makes sense to someone navigating by headings alone. Two real structural problems were found and fixed.
Keyboard access
Every interactive element — navigation, forms, filters — is a native, keyboard-operable control with a visible focus indicator. Nothing on this site requires a mouse.
Screen reader support
Forms use properly associated labels and live status regions. Decorative images are hidden from assistive technology; images that convey information have descriptive text.
Clear link text
Links that could read ambiguously out of context — the same words pointing to different destinations — were given fuller descriptions for assistive technology.
Responsive by default
The site is built with relative units and flexible layouts, so it reflows for zoomed text and smaller screens rather than requiring horizontal scrolling.
Known limitations
What we haven’t done yet.
- The site hasn’t yet been tested by people who use screen readers, switch devices, or screen magnifiers as their primary way of browsing — this is the step that actually confirms accessibility in practice, and it’s still ahead of us.
- Reports, briefs and other documents we publish as PDFs are not automatically accessible just because this site is — each one needs its own accessibility pass, which we haven’t built a process for yet.
- This audit reflects the site as it exists at the date below. As pages are added or changed, some may not meet the same standard until they’re reviewed.
Compatibility
What this site is built for.
Vantercor.org is built with standard, semantic HTML, CSS and minimal JavaScript, and is designed to work with current versions of major browsers (Chrome, Firefox, Safari, Edge) and commonly used assistive technology such as NVDA, JAWS and VoiceOver. It has not yet been formally tested against each of these individually — see Known Limitations.
Tell us what isn’t working
Found a barrier? We want to know.
If any part of this site is difficult or impossible to use with the technology or approach you rely on, please tell us. We treat accessibility reports the same way we treat every other claim on this site: seriously, and with a real response, not a form letter.
- Email accessibility@vantercor.org
- General contact Use our contact form and select “Other” — mention accessibility in your message.
- Response time We aim to respond within two business days, and to let you know what we can do about it, even if the fix will take longer.
This statement was last reviewed on September 14, 2026, alongside a full code-level accessibility audit of the site. We intend to review it again as the site grows and as real-world testing is completed.