Accessibility across the whole commerce journey
Ecommerce, retail, marketplaces, bookings, subscriptions and lead generation. Every step between discovery and confirmation is a place a customer can be stopped, and a conformant product page does not help if the checkout is unusable.
How does accessibility affect a commerce journey?
A commerce journey is a chain, and a chain fails at its weakest link. A customer can find the product, read the description and choose the options, and still be stopped by a date picker that cannot be operated by keyboard, an error announced only in colour, or a payment field inside an iframe that traps focus. Accessibility work does not create demand. It removes the barriers that prevent customers who already want to buy from finishing. ExceedAbility assesses the whole funnel, not a sample of pages.
Who this covers
Any organisation whose digital experience is designed around a customer completing something: a purchase, a booking, a quote, a subscription or an enquiry.
- Ecommerce
- Retail
- Marketplaces
- Subscriptions
- Membership platforms
- Lead generation
- Quote journeys
- Booking systems
- Ticketing and events
- Travel and accommodation
- Application funnels
- Sales and conversion funnels
Why accessibility matters here
Commerce teams already measure the thing accessibility affects. Every step in a funnel is instrumented, and the drop off at each one is visible. What analytics cannot tell you is why a particular group of customers never gets past step four.
-
Barriers, not preferences
An inaccessible step is not a customer choosing to leave. It is a customer who cannot proceed. The distinction matters because the fix is different: this is not a persuasion problem, it is a defect.
-
Reach across a broader market
Around one in five Australians has disability, and the figure rises with age. Fixes for screen reader and keyboard users also help older customers, people using small screens, people with slow connections and anyone shopping in a noisy or bright environment.
-
Usability findings that analytics never explained
Accessibility work is close reading of an interface by someone testing every state. It routinely surfaces general usability defects: unlabelled controls, unclear error recovery, focus that jumps, states that change without telling anyone.
-
Quality across a long chain of third parties
A modern checkout is assembled from a theme, a platform, a payment provider, an address lookup, a reviews widget and a consent banner. Each is a separate accessibility risk, and no single vendor is accountable for the assembled experience. Someone has to assess the whole thing.
-
Inclusive design as a commercial position
Customers who find that a retailer works for them tend to stay with it. Accessibility is one of the few quality investments that is simultaneously a customer experience improvement, a risk reduction and a statement about who you are willing to serve.
-
Obligations that already apply
The Disability Discrimination Act applies to organisations providing goods or services in Australia, and the 2025 AHRC guidelines set WCAG 2.2 AA as the benchmark. Retailers selling into the European Union are also within scope of the European Accessibility Act, which has applied since 28 June 2025 and expressly covers ecommerce.
Where accessibility problems occur
Assess the funnel in the order a customer meets it. A failure at any single stage ends the journey, no matter how good the other seven are.
-
Discovery
Search, navigation, faceted filters, category pages and results that update without announcement.
-
Selection
Product galleries, size and colour selectors, variant pickers, stock messaging and comparison views.
-
Forms and details
Delivery details, date and time pickers, address lookup, gift options and special instructions.
-
Account creation
Registration, guest checkout, password rules, social sign in and email verification.
-
Checkout
Cart edits, promotion codes, shipping selection, order summaries and the last review step.
-
Payment
Card fields in third party iframes, wallets, instalment providers and step up authentication.
-
Confirmation
Success states that are shown but never announced, order numbers, receipts and confirmation emails.
-
Account management
Order history, returns, subscription changes, invoices and support pathways.
The recurring failure points
Filters and dynamic results
Results that refresh silently, filter counts that never reach a screen reader, and focus that returns to the top of the page after every change.
Custom selectors and pickers
Size, colour and quantity controls built from unlabelled elements, and date pickers that can only be driven with a mouse.
Form validation
Errors indicated by red borders alone, messages that are not associated with the field, and validation that fires and steals focus mid entry.
Payment components
Third party card fields with missing labels, focus trapped inside an iframe, and step up authentication that times out with no warning.
Overlays and interruptions
Consent banners, newsletter modals, chat launchers and countdown offers that cover content, break focus order or cannot be dismissed by keyboard.
Status and confirmation
Cart updates, stock warnings and order confirmations conveyed visually only, so a screen reader user never learns the outcome of their own action.
What we assess
Commerce experiences span more formats than teams expect: the storefront, the authenticated account area, the native app, and the receipts, invoices and terms that arrive as documents. We assess the whole set, because customers meet the whole set.
Websites
Public sites, campaign sites and content estates assessed against WCAG 2.2, with prioritised findings, code level fixes and a retest once the corrections land.
Web applications
Transactional interfaces, authenticated portals, dashboards and enterprise systems, including the custom components and single page frameworks that automated tools cannot judge.
Mobile applications
Native and hybrid applications tested with the platform screen readers and interaction settings your customers actually use, not emulated approximations.
Documents
PDF, Word, PowerPoint, Excel and InDesign remediated to WCAG 2.2 AA and PDF/UA, at volume, plus Easy Read, large print, audio and braille where an alternative format is the right answer.
Design and development
Accessibility input before the build, so decisions about patterns, components and journeys are made once. Design reviews, delivery advice and accessibility written into your definition of done.
Self service and tools
Free checks and references your own team can run today. Useful for triage and for building internal capability, and a sensible first pass before an independent assessment.
Build, test, assure: three layers, not one
Commerce sites are assembled, not built. A theme, a platform, a payments provider, an address lookup, a reviews widget, a consent banner and a chat tool each arrive from a different supplier, and each one ships its own accessibility position.
Your developers and your agency should build accessibly and test their own work. But no individual vendor is accountable for the assembled experience your customer meets, and the party that built the checkout is not the right party to be the sole judge of whether the checkout works for a screen reader user.
Build
Designers, developers, content authors and suppliers build accessibility into the work as it is created.
- Accessible design patterns and component libraries
- Semantic markup, keyboard support and assistive technology behaviour
- Authoring standards for content and documents
Test
Delivery teams test throughout the cycle so problems surface early, while they are cheap to fix.
- Automated checks in the pipeline and in the browser
- Manual keyboard and screen reader checks by the team
- Accessibility in the definition of done and release gates
Assure
An independent specialist gives an objective view of conformance, usability and residual risk.
- Independent WCAG 2.2 assessment with reproducible evidence
- Testing with real assistive technology, not automation alone
- Conformance reporting for procurement, risk and executive audiences
Assess what shipped, not what was promised
Platform and plugin accessibility claims describe components in their default state. Your customers experience your theme, your apps, your content and your customisations, on your live site. An independent assessment tests that, in the order a customer meets it, using the assistive technology they actually use.
Practical places to attach it: accessibility acceptance criteria in agency and platform contracts, an independent assessment before a replatform or a peak trading period goes live, a retest after remediation, and a standing check whenever a new third party widget is added to the checkout.
How ExceedAbility helps
Findings arrive severity ranked with the code level fix attached, so a developer can act on them without a translation step. Scope, effort and dates are agreed in writing before anything starts.
Funnel audits
An independent WCAG 2.2 AA assessment of a complete purchase, booking or application journey, including the third party components inside it.
Accessibility audits →User testing on real journeys
People who use screen readers, magnification, switch access and voice control attempt the actual transaction. It shows you where customers stop, and why.
User testing →Remediation support
Hands on fixes for the difficult parts: custom selectors, date pickers, dynamic filters, modals and the design system components that repeat across every page.
Web remediation →Advice before the build
Accessibility input into replatforms, design systems and vendor selection, so the same defect is not rebuilt into the next version of the store.
Consulting and strategy →Team training
Merchandisers, content authors, designers and developers each learn the part they own, so product uploads and campaign pages stay accessible between audits.
Training programs →Receipts, invoices and terms
The documents a transaction produces are part of the experience. Templates remediated to WCAG 2.2 AA and PDF/UA so every generated document is accessible by default.
Document remediation →Build internal capability first
Free checks and references your team can run today. Useful for triage on a template or a campaign page, and a sensible first pass before an independent assessment.
Common questions from commerce teams
Plain answers to what digital, product and ecommerce leaders ask us most often.
Which steps in a commerce funnel fail most often?
Faceted search and filters that update results silently, product option selectors built from unlabelled custom controls, date and time pickers in booking flows, multi step forms with inaccessible validation, address lookup and autocomplete widgets, payment fields inside third party iframes, and confirmation states shown visually but never announced.
Does accessibility increase conversion?
We do not claim a guaranteed uplift, and we would treat any supplier who does with caution. What can be said precisely is that inaccessible interfaces create barriers that prevent otherwise willing customers from completing a transaction, and that accessibility work routinely surfaces general usability defects that affect everyone. The honest framing is barrier removal, not a growth promise.
We use a hosted commerce platform. Can it still be inaccessible?
Yes. Platform claims describe the vendor's components in their default state, not your theme, your apps and plugins, your content or your customisations. Customers experience the store you actually shipped, including every third party widget in the checkout. An independent assessment of your live implementation is what stands up.
Will an accessibility overlay solve this?
No. Overlay scripts and widgets do not deliver WCAG conformance on their own, and in 2025 the US Federal Trade Commission fined accessiBe one million dollars over marketing claims that an automated widget could. If you are running one, we can show you what the underlying conformance position actually is. Read the full explanation.
When is the best time to assess?
Before a replatform goes live, and well before a peak trading period. Assessing a staging environment gives the team time to fix findings without a change freeze in the way. If the site is already live, start with the single journey that carries the most volume.
Do these obligations apply to Australian retailers?
The Disability Discrimination Act applies to organisations providing goods or services in Australia, and the 2025 AHRC guidelines set WCAG 2.2 AA as the benchmark for digital goods and services. Retailers selling into the European Union are also within scope of the European Accessibility Act, which has applied since 28 June 2025 and expressly covers ecommerce.
Find out where customers are being stopped
Pick your highest volume journey. We will assess it end to end and hand back a prioritised, developer ready list.
Book a Discovery Call Request an Accessibility Review