We hold this site to WCAG 2.2 AA. Below is what CI checks on every build, and what it doesn't. Same first-party approach as our security review and delivery record: named limits instead of a badge.
An audit of the built site found five buying-path pages shipping with no page heading, no way to skip the navigation, and a menu that was quietly writing itself into the document outline. Those are fixed, and four checks now run on every build so they can't come back unnoticed.
Each one fails the build with a readable list of what it found, not a silent pass.
verify-a11yEvery page has one <h1> inside <main>. Heading levels never skip. No heading sits outside <main>, so the nav cannot reopen the outline. Each page has a working skip link. Every image has alt text. Every link and button has an accessible name. Every form control has a label. No element uses a positive tabindex. No focusable element sits inside a <summary>. The heading permalink declares a 24px floor.
verify-seoCanonical URLs, structured data, meta descriptions, and page titles are present, correct, and unique on every route. A search engine and a screen reader both depend on the same thing here: an honest, unambiguous description of what the page is.
verify-themeEvery text-and-surface colour pairing in both themes clears 4.5:1 contrast. Every focus indicator clears 3:1. No component draws its own focus ring in a colour that skips the check.
verify-copyProse density and banned filler phrases. This is not a WCAG rule, but it comes from the same instinct. A screen-reader user hears every word we did not cut.
Read this before the checklist above, not after.
Tell us what page, what you were trying to do, and what happened instead. Send a project brief and put "Accessibility" in it. We read every one.
Source: https://customlabs.io/accessibility/