Every page we ship passes WCAG 2.1 AA. The build fails if one does not.
Most agencies treat accessibility as a line item you can decline. We treat it as a build gate, which means it cannot be quietly skipped when a deadline gets tight.
How to check our work
We run axe-core, the same engine behind Google Lighthouse and Microsoft Accessibility Insights, across every public route on this site — plus states a page-load scan never reaches, like an open mobile menu and a form displaying its validation errors. Those dynamic states are where real violations hide.
The ruleset is wcag2a, wcag2aa, wcag21a, wcag21aa and wcag22aa. The scan exits non-zero on a single violation, so a failure blocks the release rather than filing a ticket nobody reads.
Point any scanner you trust at any page on this domain. You should find nothing. If you do find something, tell us and we will fix it — that offer is the whole point of publishing this page.
What the gate checks
- Colour contrast on every text and interface element
- Accessible names on every button, link and form control
- Heading order, landmarks and document structure
- Keyboard reachability, including scrollable regions
- Text alternatives for images and icons
- Form error states, announced and associated with their fields
Why a contractor or clinic should care
ADA web accessibility demand letters are a live, expensive problem for small businesses in Florida and Georgia, and they do not target the Fortune 500 — they target the restaurant, the dental practice, the roofing company, because those sites are the easiest to fault and the least likely to fight. Settling one costs more than the site did.
There is also a plainer commercial argument. Roughly one in four US adults reports a disability. A site that is unusable with a keyboard, or unreadable at low contrast, is turning away customers who arrived ready to buy — and it does it silently, because nobody fills in a contact form to complain that they could not fill in your contact form.
We are not lawyers and none of this is legal advice. What we can tell you is that WCAG 2.1 AA is the standard these claims are usually measured against, and that building to it from the start costs a fraction of retrofitting it under a deadline set by someone else.
What we will not claim
An automated scan catches roughly a third of WCAG issues. It cannot tell you whether alt text is meaningful, whether a flow makes sense to someone using a screen reader, or whether your copy is comprehensible. Any agency selling a “100% accessible” badge on the strength of a scanner is overselling the tool.
The gate is a floor that never slips, not a ceiling. And it applies to what we build — we do not extend the claim to sites built before the gate existed, including older work of our own.
Worried about your current site?
We will run the same scan against it and tell you what we find, ranked by severity and by how likely each issue is to show up in a complaint. If it is clean, we will tell you that too.