Website Accessibility Checklist (WCAG 2.2 Compliance)
A practical WCAG 2.2 checklist for business sites: contrast, keyboard, forms, focus, and the failures that still show up in ADA demand letters.
Written and reviewed by Artem Palamarchuk, Founder of BLEX STUDIO.
What does WCAG 2.2 actually require on a business website?
Perceivable, operable, understandable, robust — with 2.2 adding focus appearance, dragging alternatives, and target size. This is not a plugin. A widget that claims “ADA compliant” on a broken form is a sticker.
We already covered the policy weather in ADA compliance 2026. This is the punch list we run on a marketing site.
The checklist we actually use
Keyboard can open the menu, close it, and reach the form without a trap
Focus is visible on every interactive control
Contrast holds on buttons, not only on body text
Images that mean something have alt; decorative images are empty alt
Is WCAG 2.2 legally required?
Treat 2.2 Level AA as the working target for US/EU-facing business sites. Exact legal exposure depends on jurisdiction and sector. We are not your lawyer.
Can a plugin make us compliant?
No. Plugins can help find issues. They cannot invent labels, contrast, or keyboard behavior your theme never had.
How much does remediation cost?
A small marketing site might be $1,500–$6,000. A custom app is a product project. Rebuilds cost more and sometimes are cheaper than patching a hostile theme.
Do we need a VPAT?
If you sell to government or enterprise, probably. Marketing sites usually need fixes more than a PDF of claims.
What about PDFs?
If the PDF is the only way to get prices or forms, it must be accessible — or put the same info in HTML.