Platform guides
Accessibility and the EAA, by platform
This page is available in English only. What each website builder gets right, where sites built on it usually fail WCAG, and what actually applies to your business regardless of which one you use.
Shopify
Shopify handles hosting, checkout, and payments — it doesn't handle accessibility for you. Whether a Shopify storefront meets WCAG 2.1 AA depends almost entirely on which theme you run and which apps you've installed, not on the platform itself.
Read more →WooCommerce
WordPress core is developed with an active accessibility team and its own coding standards — but WooCommerce is a plugin, and the theme plus the other plugins you run alongside it are where accessibility problems in practice come from, not WordPress core itself.
Read more →Wix
Wix ships a genuinely useful built-in tool — the Accessibility Wizard, available in the Wix Editor — that scans a site for missing alt text, checks heading hierarchy, and can enable keyboard navigation and a visible focus indicator. It's a real starting point. It isn't a WCAG audit, and Wix's own documentation doesn't claim it is.
Read more →Squarespace
Squarespace's templates are visually polished, and that's exactly where accessibility risk tends to concentrate: image-heavy, animation-heavy designs are harder to make accessible than plain layouts, and template choice has a bigger effect on WCAG compliance than most site owners expect.
Read more →Webflow
Webflow is different from the other platforms on this page in one important way: it gives designers direct control over the actual HTML that gets published, down to which tag an element renders as. That's a genuine advantage for accessibility when a designer uses it deliberately — and a common source of failures when they don't, because Webflow doesn't enforce semantic markup for you.
Read more →Something else?
The check doesn't care what you built with — it reads the page a browser renders.
Run a free check →