What we tested,
and what we did not.
A measurement log rather than an aspiration, including the things we have not checked. Built toward WCAG 2.2 AA, and deliberately not called certified.
What we have actually tested
This is a measurement log, not an aspiration. Every claim below was checked against the running site with automated tooling and a real browser, and the checks are re-runnable.
Colour contrast is measured on every text node of all twelve pages against its real background, and tested against the WCAG 2.2 AA thresholds of 4.5:1 for normal text and 3:1 for large text, with no rounding in our favour. Result: zero failures.
The layout is verified at thirteen viewport widths from 320px to 6016px on every page, with no horizontal overflow and no runtime errors.
Every interactive control is reachable and operable by keyboard. Text alternatives exist for every icon, and there are no icon-only buttons carrying meaning alone.
Reduced-motion preferences are honoured: when the system asks for reduced motion, animated figures resolve to their final values immediately rather than counting up.
With JavaScript disabled, all content remains, including the final values of every figure, and the contact form states plainly that it needs scripts and explains why.
What we have not tested
We would rather say this than imply more than we know.
We have not run a full screen-reader session. Assistive technology behaves in ways automated checks do not model, and we will not claim a conformance level we have not personally walked through.
We have not tested on Safari or on iOS, because our verification environment is not those browsers.
We have not completed a third-party accessibility audit or had this site accredited under VPAT, WCAG or Section 508.
The standard we are working to
The Web Content Accessibility Guidelines version 2.2, level AA, published by the W3C as a W3C Recommendation. This site is built toward that standard — which is a narrower and more honest claim than a conformance statement, and it is deliberately not labelled as certified.
If you want this page to say something stronger, that takes a formal audit by an independent accessibility specialist, and we will publish the result either way.
Why this page exists at all
Title III of the ADA concerns places of public accommodation, and web accessibility obligations for businesses are generally argued through those rules and their state analogues rather than a single federal web-specific statute. Businesses that want to be usable by disabled visitors have the strongest practical reason to comply whether or not any specific rule is pointed at them.
Meeting a legal requirement is a floor. A person who cannot use the site is the actual problem, and it does not matter which rule was breached.
Reporting a barrier
If something here does not work for you, say so through the contact page. Barriers get reported to a person, acknowledged, and treated as defects rather than feedback. We would rather have an honest complaint than a silent one.
Last updated 2026-10-04. This page describes what this site actually does today, and it changes the day the site changes.
Contact
Prices, scope and engagement questions go through the brief page. Anything on this page you want challenged, corrected or explained gets a straight answer.