Consult
Which standard applies, and which templates are in scope, from homepage to checkout.
A scope summary
Find out whether shoppers using a keyboard, a screen reader or a magnifier can actually buy from your store. We audit against WCAG 2.2 AA and give you a fix plan by template.
Adobe Commerce gold partner
#1 Adobe Commerce partner worldwide

Hyvä Platinum Partner
40+ projects delivered


ISO certification
9001 & 27001

Most certified Hyvä agency worldwide

200+ Adobe Commerce Certifications
Award-winning agency
3× eCommerce excellence award
We work out which standard applies, test the store, and give you a fix plan mapped to the templates that cause each issue.
Where you sell decides the standard, and we agree which templates are in scope.
Automated scanning, plus manual testing by keyboard and screen reader.
Every issue mapped to its WCAG criterion, ranked by impact and effort.
We don't certify compliance, and we're not a law firm. We show where the store stands and what to fix first.
Where you sell decides it, and WCAG sits behind both laws.
Title III covers businesses open to the public, and online stores are widely treated as covered. With no codified web standard, WCAG AA is the practical benchmark.
Applies since 28 June 2025 to e-commerce sold to EU consumers. Microenterprises are exempt for services. Conformity is shown through EN 301 549.
It builds on the 2.1 criteria EN 301 549 references and adds newer ones, so one audit serves both markets.
The problems sit in specific Magento components, and these are the ones we test first.
Unreachable by keyboard, or silent to screen readers.
Relying on colour alone, with no text label.
Not trapping focus, or not returning it when closed.
That only open on hover.
No keyboard controls, or moving on their own.
Never announced, so the item seems not added.
Shown visually but not linked to the field.
Where focus gets lost between steps.
Six newer criteria that land squarely on Magento components.
A sticky header or add-to-cart bar mustn't hide the element that has keyboard focus.
Swatches, quantity steppers and close icons need enough space to tap.
A price slider in layered navigation needs an alternative to dragging.
Checkout shouldn't make shoppers retype information they've already given.
Signing in can't depend on solving a puzzle or memorising characters, unless there's an alternative.
Contact and help links should appear in the same place on every page.
Plugins, apps and overlays add a toolbar or script on top of the store. They don't change the templates underneath, and that's where the failures are.
A filter, a checkout error or a swatch stays inaccessible in the store's own code.
Whatever runs on top, the underlying markup is unchanged.
Not at a tool to install.
Magebit is the team behind Inclusify, an accessibility scanner and visitor widget. It finds the issues, assists visitors, and documents the fixes made in the code.
Automated audits surface every issue by severity, so the team knows what to fix first.
Remediation is tracked against the code, which is the only fix that holds up.
Contrast, text size, motion and more, as genuine help rather than a cosmetic patch.
Installed through footer scripts, and on Shopify, WordPress and other platforms too.
Inclusify doesn't make a store compliant on its own, and neither does any tool. It's how we find issues fast and show the work behind every fix.
Scan your store free with InclusifyThree steps, each ending in a document you keep.
Which standard applies, and which templates are in scope, from homepage to checkout.
A scope summary
An automated scan, plus keyboard and screen-reader testing on key templates and checkout.
A written audit report
Each issue mapped to its criterion, ranked by impact and effort, traced to its template.
A plan your team can run
Automated tools find only part of what matters. Manual testing is where most checkout and navigation issues show up.
Book an accessibility auditIssues that share a cause are grouped, so developers fix a component once rather than chasing it across fifty pages.
Which WCAG criterion fails, and how badly it affects shoppers.
So the fix is checked everywhere it lands.
Keyboard and screen-reader steps, and the recommended fix.
No theme guarantees accessibility on its own. What matters is how your store was built on it.
Fixes go into the theme's templates, layout files and JavaScript components.
Fixes go into the Hyvä templates and their Alpine.js behaviour.
Fixes go into the frontend components themselves.
The fix plan names the exact files for whichever theme you run.
We can make the fixes and check accessibility on every release.
Tracked in the Magebit Client Portal, every solution reviewed by a developer.
Regressions caught before they ship.
So new images and pages don't undo the work.
Magebit brings Magento expertise to businesses in every country. From Perth, Melbourne and Sydney to London, Dubai, New York, Los Angeles, Charlotte and Florida, we’re ready to help wherever you are.
The top-ranked Adobe Commerce agency on the planet by Adobe themselves.

The most certified Hyvä agency in the world. Confirmed by Hyvä themselves, twice.
Explore Hyvä development
Innovator, World Traveler, and eCommerce Excellence awards across Meet Magento NYC and HIVE London, and more.

The most-certified Hyvä agency worldwide and the first Hyvä Platinum Partner in the USA. 55+ Hyvä certifications and 40+ projects delivered.
ISO 9001 & 27001 for quality and security.
Truly agile team that moves and adapts faster than your typical agency.
UX grounded in large-scale ecommerce research.
The checkout is where most stores lose shoppers who use a keyboard or a screen reader. Tell me where you sell and which theme you run, and we'll show you where the store stands.
Reviewed by Kristaps Rjabovs
Co-founder of Magebit, Forbes 30 Under 30

If you can't find the answer you're looking for, feel free to reach out to us. We're here to help.
If you sell to customers in the US, it very likely does. The ADA doesn't set a technical standard for private websites, so WCAG AA is the usual benchmark. Your counsel can confirm how it applies to your business.
If you sell to consumers in the EU, your store has had to meet the EAA's accessibility requirements since 28 June 2025, unless you're a microenterprise. In practice that means meeting WCAG AA through EN 301 549.
Level AA. It's the level both the ADA benchmark and the EAA's standard point to. We test against WCAG 2.2 AA, which covers the 2.1 criteria and the newer ones.
No. A plugin or overlay adds a layer on top of the store but doesn't change the templates, which is where the failures are.
It depends on the build. Any theme can be made accessible or inaccessible by how it's customised, which is why we audit your store rather than the theme.
It depends on how many templates are in scope. We'll give you a timeline after the consult.
No. No agency can certify a store as legally compliant. We tell you where the store stands against WCAG and what to fix first, and your counsel handles the legal side.
Explore the Magento services Magebit has to offer.
Tell us where you sell and which theme your store runs. We'll start with a consult to scope the audit. Not ready yet? Start with the Magento accessibility checklist.
Which standard applies, and what's in scope.
Automated and manual, by keyboard and screen reader.
Every issue traced to its template, yours to keep.
We use cookies to understand visits, show relevant ads and play videos. You choose what to allow.