Skip to content

Magento ADA compliance and accessibility

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 badge.

Hyvä Platinum Partner

40+ projects delivered

ISO 9001 certified company.ISO 27001 certified company.

ISO certification

9001 & 27001

Hyvä certification badges with a 55+ count.

Most certified Hyvä agency worldwide

Adobe Commerce certification badges: Professional, Expert, Master and Certified, with a 200+ count.

200+ Adobe Commerce Certifications

Meet Magento eCommerce Excellence Award

Award-winning agency
3× eCommerce excellence award

Magento accessibility, ADA, WCAG and the EAA

We work out which standard applies, test the store, and give you a fix plan mapped to the templates that cause each issue.

  • Which standard, and which templates

    Where you sell decides the standard, and we agree which templates are in scope.

  • Tested by people, not only tools

    Automated scanning, plus manual testing by keyboard and screen reader.

  • A fix plan by template

    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.

Which standard applies to your store

Where you sell decides it, and WCAG sits behind both laws.

In the US, the ADA

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.

  • ADA Title III
  • WCAG AA benchmark

In the EU, the European Accessibility Act

Applies since 28 June 2025 to e-commerce sold to EU consumers. Microenterprises are exempt for services. Conformity is shown through EN 301 549.

  • Directive (EU) 2019/882
  • EN 301 549
  • WCAG 2.1 AA

We test against WCAG 2.2 AA

It builds on the 2.1 criteria EN 301 549 references and adds newer ones, so one audit serves both markets.

Where Magento stores usually fail

The problems sit in specific Magento components, and these are the ones we test first.

  1. Layered navigation filters

    Unreachable by keyboard, or silent to screen readers.

  2. Colour and size swatches

    Relying on colour alone, with no text label.

  3. Mini-cart and modals

    Not trapping focus, or not returning it when closed.

  4. Mega menus

    That only open on hover.

  1. Galleries and carousels

    No keyboard controls, or moving on their own.

  2. Add-to-cart feedback

    Never announced, so the item seems not added.

  3. Form errors

    Shown visually but not linked to the field.

  4. Checkout and payment iframes

    Where focus gets lost between steps.

What WCAG 2.2 adds for an online store

Six newer criteria that land squarely on Magento components.

Focus not obscured (2.4.11)

A sticky header or add-to-cart bar mustn't hide the element that has keyboard focus.

  • Sticky headers checked while tabbing
  • Sticky add-to-cart bars checked on product pages
  • Cookie banners checked over focused elements

Target size (2.5.8)

Swatches, quantity steppers and close icons need enough space to tap.

  • At least 24 by 24 pixels, or enough spacing around them
  • Colour swatches and quantity buttons measured
  • Close icons on modals and mini-cart checked

Dragging movements (2.5.7)

A price slider in layered navigation needs an alternative to dragging.

  • Min and max price input fields beside the slider
  • Carousels usable with buttons, not only swipes
  • Every drag action has a single-pointer alternative

Redundant entry (3.3.7)

Checkout shouldn't make shoppers retype information they've already given.

  • A same-as-shipping option for billing
  • Details carried between checkout steps
  • Saved addresses offered to signed-in customers

Accessible authentication (3.3.8)

Signing in can't depend on solving a puzzle or memorising characters, unless there's an alternative.

  • Password managers and paste allowed
  • CAPTCHA with an accessible alternative
  • Sign-in links or codes as an option

Consistent help (3.2.6)

Contact and help links should appear in the same place on every page.

  • Help links in the same position site-wide
  • Checkout keeps the same contact option
  • Chat widgets placed consistently

Why an accessibility plugin is not the fix

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.

The templates stay broken

A filter, a checkout error or a swatch stays inaccessible in the store's own code.

A layer, not a repair

Whatever runs on top, the underlying markup is unchanged.

So the plan points at templates

Not at a tool to install.

We built Inclusify

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.

  • Continuous WCAG scanning

    Automated audits surface every issue by severity, so the team knows what to fix first.

  • Fixes documented at the source

    Remediation is tracked against the code, which is the only fix that holds up.

  • A widget visitors control

    Contrast, text size, motion and more, as genuine help rather than a cosmetic patch.

  • Works on Magento

    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 Inclusify

How we work, from consult to fix plan

Three steps, each ending in a document you keep.

1

Consult

Which standard applies, and which templates are in scope, from homepage to checkout.

A scope summary

2

Audit

An automated scan, plus keyboard and screen-reader testing on key templates and checkout.

A written audit report

3

Fix plan

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 audit

What's in the audit report

Issues that share a cause are grouped, so developers fix a component once rather than chasing it across fifty pages.

  • The criterion and severity

    Which WCAG criterion fails, and how badly it affects shoppers.

  • Every page it appears on

    So the fix is checked everywhere it lands.

  • How to reproduce and fix it

    Keyboard and screen-reader steps, and the recommended fix.

Luma, Hyvä and custom themes

No theme guarantees accessibility on its own. What matters is how your store was built on it.

Luma

Fixes go into the theme's templates, layout files and JavaScript components.

  • Templates
  • Layout XML
  • JavaScript

Hyvä

Fixes go into the Hyvä templates and their Alpine.js behaviour.

  • Templates
  • Alpine.js

Custom and headless

Fixes go into the frontend components themselves.

  • Components
  • Storefront code

The fix plan names the exact files for whichever theme you run.

Doing the fixes, and keeping them fixed

We can make the fixes and check accessibility on every release.

Through SOLVE or a dedicated team

Tracked in the Magebit Client Portal, every solution reviewed by a developer.

Checks in the release process

Regressions caught before they ship.

Guidance for content editors

So new images and pages don't undo the work.

Why ambitious brands choose Magebit

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.

Adobe Solution Partner

#1 Adobe Commerce partner worldwide

The top-ranked Adobe Commerce agency on the planet by Adobe themselves.

Read the story
Hyvä storefront visualHyvä certification badge

55+ Hyvä Certificates

The most certified Hyvä agency in the world. Confirmed by Hyvä themselves, twice.

Explore Hyvä development
Four people smiling at an event with two holding clear trophies in front of pink Meet Magento New York screens.

Award-winning solutions

Innovator, World Traveler, and eCommerce Excellence awards across Meet Magento NYC and HIVE London, and more.

Kristaps Rjabovs and the Magebit team

Hyvä Platinum Partner

The most-certified Hyvä agency worldwide and the first Hyvä Platinum Partner in the USA. 55+ Hyvä certifications and 40+ projects delivered.

Two overlapping ISO certification logos: ISO 9001 and ISO 27001 certified company.

ISO certified

ISO 9001 & 27001 for quality and security.

Scrum Alliance CSM Scrum Master badge with a star and gear border.

Scrum Alliance certified team

Truly agile team that moves and adapts faster than your typical agency.

Baymard Institute logo with colored angled shapes to the right of the text.

Baymard certified design team

UX grounded in large-scale ecommerce research.

Start with the checkout

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

Kristaps Rjabovs, co-founder of Magebit.

Frequently asked questions

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.

Book an accessibility audit

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.

  • 1

    Consult

    Which standard applies, and what's in scope.

  • 2

    Audit

    Automated and manual, by keyboard and screen reader.

  • 3

    Fix plan

    Every issue traced to its template, yours to keep.

Schedule a call