AccessibilityLast reviewed · August 17, 2026

Built to be
usable by everyone.

We build software for a living. Accessibility is part of that craft, not a compliance checkbox bolted on at the end — so this page tells you exactly what we target, what we have tested, and what we know is still imperfect.

Our conformance target

This site aims to conform to Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the standard referenced by the Americans with Disabilities Act in practice, by Section 508 in the United States, and by EN 301 549 in the European Union.

We describe this as partially conformant: most of the site meets the standard, and we are transparent below about where we have not finished verifying. We do not claim certification, because no such certification exists for WCAG.

What we have actually tested

As of August 17, 2026, on every page of this site:

Automated testing. axe-core run against the WCAG 2.2 AA ruleset across all pages, at both desktop and mobile viewport widths. No violations outstanding at the time of review.
Keyboard navigation. Every interactive control is reachable and operable by keyboard alone. A “Skip to content” link is the first stop on each page, and every focusable element has a visible focus outline.
The contact form. Our multi-step intake dialog keeps keyboard focus inside itself while open, closes onEsc, returns focus to whatever opened it, and announces step changes, errors, and submission results to screen readers.
Reduced motion. Animations are disabled for visitors whose system requests reduced motion.
Structure and text. Landmark regions, a single descriptive page heading, alternative text on meaningful images, labels tied to every form field, and a declared page language.
Contrast. Text and background combinations checked against the 4.5:1 (and 3:1 for large text) AA thresholds. Our yellow brand accent is deliberately never used for body text on light backgrounds because it cannot meet that ratio.

Known limitations

Being straightforward about the gaps is more useful to you than a clean claim:

Automated testing has limits. Tools like axe-core reliably catch roughly a third to a half of real barriers. We have not yet completed a full manual audit with screen readers across all pages and assistive technologies.
Third-party embeds. Some pages embed video and scheduling tools we do not control. Their accessibility is determined by those providers.
Older articles. Long-form posts migrated from our previous site may contain images whose alternative text is less descriptive than what we now write, or documents we have not remediated.

Tell us if something blocks you

If any part of this site prevents you from doing what you came to do, we want to hear about it — that is a bug and we will treat it like one. Email info@qrewtech.com with the page address and what went wrong.

We aim to respond within five business days. If you need information from this site in a different format, ask and we will get it to you another way.

Procurement and VPAT requests