October 20, 2026

How to Make Your Shopify Navigation WCAG 2.1 AA Compliant

Practical Shopify navigation accessibility checks for keyboard use, screen readers and mobile drawers, with the limits of quick tests and WCAG 2.1 AA explained.
7 min read
Flux Insights Static Hero
Louis Croughan
Account and Project Manager @ Flux
Shopify navigation WCAG 2.1 AA accessibility - Flux Insights pattern hero

Accessible Shopify navigation helps customers reach products with a keyboard, screen reader, touch or mouse. Start with clear controls, visible focus and menus that open and close predictably. This guide explains practical WCAG 2.1 AA checks, where WCAG 2.2 belongs in new work, and why a quick test is only a starting point.

Accessibility is a revenue question

The ABS reported that 5.5 million Australians, or 21.4%, had disability in 2022. That is a population measure, not the percentage of shoppers unable to use your store. Low vision, limited hand movement and other access needs can change how someone uses a website. See the ABS findings.

A customer who cannot open a menu or reach a product may leave without contacting support. Test those journeys directly rather than estimating lost sales from a population statistic.

Accessibility belongs in the buying experience as well as the compliance checklist. Find the barriers, fix them and check that customers can complete the task.

The legal side is catching up

Accessibility obligations depend on the market, business and service. A technical checklist helps your team build and test; it does not settle every legal question.

The European Accessibility Act has applied since 28 June 2025 and covers ecommerce services, with exemptions including qualifying microenterprises providing services. Check the applicable national rules for your business. In the US, the Department of Justice distinguishes general ADA duties for businesses from detailed technical rules. In Australia, the Human Rights Commission’s 2025 guidance discusses the Disability Discrimination Act and WCAG, including WCAG 2.2. Read the EU overview, US guidance and Australian guidance.

Agree the technical standard with your team and confirm legal obligations for the markets you serve. WCAG 2.1 AA is the focus of this guide; a new project should also assess WCAG 2.2 AA.

Why navigation is where stores break

The header is an important place to start because it appears throughout the store. It is not the only place accessibility can fail.

Your navigation loads on every page, so a problem there blocks every journey. It's also the part brands most often rebuild. Mega menus, featured product panels, promo tiles and multi-level mobile drawers get designed and built custom for global brands, and every custom interaction is another place accessibility can drop out without anyone noticing.

A menu can look right and still be impossible to open without a mouse. Automated checks are useful but cannot establish accessibility on their own. WebAIM detected WCAG failures on 95.9% of the homepages in its 2026 million-page study. That study is not a Shopify navigation audit. See the WebAIM report.

What an accessible navigation actually does

Start with these five behaviours, then test the full navigation and buying journey against the agreed standard.

What it doesWho it helps
Every menu opens and closes with the keyboard as well as the mouseKeyboard users, switch users, anyone who can't use a mouse precisely
Menus work on activation and stay available while you use themPeople with tremors or limited movement, and anyone whose cursor drifts
You can always see which link you're onKeyboard users, who otherwise tab through the header with no idea where they are
A modal mobile drawer manages focus and announces its controlsShoppers with low or no vision, on their phones
Each menu is named, so the main menu and footer can be told apartScreen reader users jumping around the page

We would usually choose click-to-open menus. That is a design preference, not a WCAG rule. A hover menu can work if it also supports keyboard use and meets the requirements for dismissing, reaching and keeping the extra content visible. For common site navigation, a disclosure button and ordinary links are often appropriate; an ARIA menu role is not automatically required. See the W3C disclosure navigation example.

How to test your Shopify navigation accessibility in 15 minutes

A keyboard and your phone’s screen reader can reveal useful problems quickly. Treat this as a first check, not a complete accessibility assessment.

Keyboard test on desktop

Put the mouse away and use Tab and Shift+Tab from the top of the homepage. Can you see the focused control, open every menu and reach each link? Do buttons respond to Enter and Space? Can you dismiss an open dropdown with Escape and continue from a sensible place?

Screen reader test on mobile

Turn on VoiceOver on iPhone or TalkBack on Android. Does the menu button have a useful name and announce whether it is open? Can you reach the visible links and submenus? A modal drawer should manage focus and keep the background out of the interaction while open; a non-modal dropdown has different behaviour. Check focus returns sensibly when the drawer closes.

Zoom test

Check text at 200% and the layout at a narrow width equivalent to 320 CSS pixels. Does the navigation still work without clipped controls, overlapping text or unnecessary sideways scrolling? These checks cover different WCAG requirements.

A failed check gives your team a specific issue to investigate. Passing these checks does not prove conformance. Include a fuller assessment and, where possible, testing with people who use assistive technology. W3C describes easy checks as a first review.

What to ask your agency or dev team

If you're briefing a redesign or reviewing your current store, these questions tell you quickly whether accessibility is being taken seriously.

  • Do you test navigation with a keyboard and a screen reader before launch, or only with automated tools?
  • Will menus open on click, and work fully without a mouse?
  • How will we keep accessibility from breaking when we add promo tiles, apps or new sections later?
  • Which WCAG level are you building to, and will you document it?

Ask for the test scope, devices, assistive technology and findings. Automated results should be one part of the evidence, alongside hands-on testing and a plan for fixes.

Where accessibility fits in a project

The cheapest time to get accessibility right is before anything is built. From the project side, that means treating it like any other requirement, with a place in every phase.

Discovery

Agree the WCAG version, level and test scope up front, alongside browser and device support. Assess WCAG 2.2 AA for new work while checking any specific contractual or legal requirements.

Design

Designers check the things a customer will see. Text that's readable against its background, menus that open on click, and a clear highlight on whichever link you're on. Fixing these in a design file takes minutes. Fixing them after build takes a ticket, a developer and another round of testing.

QA and sign-off

The keyboard and screen reader tests above become part of sign-off, the same way checking the store on an iPhone is. If the menu fails, the release isn't done.

After launch

Add the same quick test to the checklist for every change that touches the header. That's what stops a store that launched accessible from drifting back out of it.

This is the same thinking behind considered design. The details customers never notice are the ones that decide whether the store works for them.

What keeping your nav accessible actually costs

An accessible navigation doesn't stay that way on its own. It can break next month when someone adds a promo tile, a theme update changes the styling, or a new app adds its own banner to the header. Each of those changes needs a quick keyboard and screen reader check before it goes live, and that's QA time you have to budget into every release that touches the header.

Third-party apps are the part you control least. Chat widgets, review pop-ups and announcement bars bring their own code, and your developers can't fix a vendor's product. If an app doesn't work with a keyboard, you can push the vendor, replace the app, or live with the gap.

Do not treat an accessibility overlay as proof that the store conforms. Check the actual menu, drawer and customer journeys. Fix barriers in the theme or relevant app, and retest after changes.

The bottom line

Accessible navigation comes down to a simple standard. Every customer should be able to open your menu, see where they are and reach any product, however they use the web. None of it changes how your header looks. All of it changes who can use it. If your design and build partner treats accessibility as part of how the storefront is designed, you get it at build time instead of paying for it after a complaint. Build it into your design system too, so every new section inherits it. A store that only works with a mouse has a locked front door.

Are Shopify themes WCAG 2.1 AA compliant out of the box?

No theme guarantees conformance on a live store. Test the theme together with its custom navigation, apps and content against the agreed WCAG version and level. Assess WCAG 2.2 AA for new work rather than relying only on an out-of-the-box theme claim.

Does WCAG apply to Australian ecommerce stores?

Australian online services can have obligations under the Disability Discrimination Act. The Australian Human Rights Commission’s 2025 digital accessibility guidance discusses WCAG, including version 2.2. Use it to inform the project brief and obtain advice on your specific obligations; a quick WCAG checklist is not a legal determination.

Does the European Accessibility Act apply to Shopify stores outside the EU?

It can apply to ecommerce services supplied to EU consumers by businesses outside the EU. The Act has applied since 28 June 2025, with exemptions including qualifying microenterprises providing services. Check the applicable national rules and your business circumstances before deciding the scope.

Why does website accessibility matter for ecommerce sales?

Customers need to reach products and complete purchases. An inaccessible menu can block that journey. Test the barriers in your own store rather than turning population disability statistics into a forecast of lost revenue.

Should a Shopify mega menu open on hover or click?

We usually prefer click-to-open menus, but WCAG does not require every menu to open on click. Hover interactions must also work with a keyboard and meet the requirements for additional content. Test whether shoppers can open, use and dismiss the menu predictably.

Can an automated checker test navigation accessibility?

Only partly. Automated tools can flag some markup and contrast problems, but cannot establish that the full navigation works for customers. Combine scans with keyboard, screen reader and responsive checks. A quick manual check is still not a complete conformance assessment.

Do accessibility overlay apps make a Shopify store compliant?

An overlay is not evidence that a store conforms. Test the actual navigation and customer journeys. Fix barriers in the theme or relevant app and verify the result with hands-on checks as well as automated tools.

/score

Does AI recommend your brand?

We ask ChatGPT and Perplexity 10 real buying questions for your category and score you against your biggest competitor. Live, in about 2 minutes.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Free. Enter your store's website, e.g. yourstore.com

Flux is a Shopify Plus Agency for Advanced Engineering & AEO

TLDR Summary
  • Make products reachable with keyboard, screen reader, touch and mouse.
  • Agree the WCAG version and level; assess WCAG 2.2 AA for new work.
  • Give navigation controls useful names, visible focus and predictable behaviour.
  • Test modal drawers and non-modal dropdowns according to how they work.
  • Use automated tools alongside hands-on checks, not as proof of conformance.
  • Recheck the header when themes, apps or content change.