A site that some visitors cannot use is a site that quietly turns customers away. We treat WCAG 2.2 level AA as the engineering floor of every build, and we verify it by measurement rather than asserting it in a brochure.
Why it matters
Accessibility regulation keeps widening: public-sector rules, disability legislation applied to the web, and consumer requirements in more and more markets. We are engineers, not lawyers, and we do not offer legal advice. What we can say plainly is that a site built and verified to WCAG 2.2 AA stands on the standard those regimes reference, and a site that ignores it carries a risk you did not price.
The same structure that serves a screen reader serves a search crawler: real headings in order, labelled controls, descriptive text on images, links that say where they go. Accessibility work and search work reinforce each other, which is why we treat them as one discipline rather than two invoices.
Comfortable contrast, generous touch targets, a page you can work with a keyboard, motion that respects your settings: visitors rarely name these things, but they feel them as care. The absence reads as cheapness, on exactly the page where you are asking to be trusted.
In practice
The standard reads as abstract until it is applied. This is what it concretely means in every site we ship.
Verification
Every built page is audited against WCAG 2.2 AA at phone, tablet and desktop widths, in both light and dark schemes, on every change. A violation does not produce a report somebody might read; it fails the build, and a failed build cannot deploy. Accessibility regressions are caught before a visitor can meet them.
Contrast ratios are computed, target sizes are measured in pixels, heading order is parsed, and the same checks run on every language version of every page. What a checklist asserts, the suite proves.
Automated checks catch a great deal but not everything. Before a site ships we also work it the way an actual visitor with access needs would: navigate it entirely by keyboard, read it at enlarged text sizes, and step through the forms with the screen reader's announcements in mind.
Built in
Retrofitting accessibility is the expensive way to get it: recoloring a brand palette that never cleared contrast, rebuilding components that cannot take focus, rewriting pages whose headings were decoration. We take the opposite path. The design system is checked for contrast in both schemes before a single page is composed, interactive components are built keyboard-first, and the audit runs from the first deploy of the project, not the last. By launch, accessibility is not a task on a list; it is a property of the codebase that the tests keep true.
Everything a website engagement includes Accessible in every language, including RTL How an engagement runs
Ask us anything about the standard, or ask us to look at your current site. Reach us via the contact form or at sales@wwi.dev.