Ecommerce Website Developer

JournalAbout 2 min read

Accessibility in the checkout is a commercial issue

A checkout that cannot be completed by keyboard excludes customers who were ready to pay. The same fixes reduce abandonment for everyone.

Written by

Nazir AbbasApproved contributor

Contributed by

Javed IqbalApproved contributor

Published

Abstract measured panel in the brand colours

Key takeaways

  • Buy something on your own site using the keyboard alone
  • Tie each error to its field, summarise at the top and preserve entered values
  • Never signal a required field or a selected option by colour alone
  • Keep labels outside the field; placeholders disappear as soon as you type
  • Correct autocomplete attributes are an accessibility feature, not a convenience
  • Blocking paste in card or password fields is hostile and does not improve security

Accessibility in ecommerce is usually framed as a compliance obligation. It is also, more immediately, a conversion issue: a customer who cannot complete the checkout does not buy.

The useful thing about checkout accessibility is that nearly every fix improves the experience for everybody.

Test the purchase by keyboard alone

Put the mouse away and buy something. Most teams have never done this on their own site, and most find a blocker within two minutes.

Common failures:

  • A custom dropdown that cannot be opened or closed without a pointer
  • A modal that traps focus, or one that does not trap it and lets you tab behind it
  • A payment field in an iframe that the tab order skips entirely
  • A submit button reachable only by scrolling a container that does not scroll by keyboard

Make errors findable and understandable

Form errors are where accessibility and conversion overlap most directly.

  1. Each error is tied to its field, so assistive technology announces it with the field
  2. A summary appears at the top and receives focus, so the user is told immediately
  3. The message says what to do, not just that something is wrong
  4. Values the customer already entered are preserved

A customer who has to retype their address after an error is a customer who may not bother.

Do not rely on colour alone

A required field marked only by a red asterisk, or a selected delivery option marked only by a colour change, is invisible to a meaningful share of customers. Add a word or a shape as well.

Keep the labels

Placeholder text that disappears when you start typing is the single most common accessibility fault in checkouts, and it affects everybody: once you have typed, you can no longer see what the field was for.

Persistent labels outside the field cost nothing and remove the problem.

Autofill is an accessibility feature

Correct autocomplete attributes on name, address and payment fields let browsers and password managers fill them. For a customer with a motor impairment this is the difference between a two-minute checkout and a ten-minute one. For everyone else it is simply faster.

What to test, in order

  1. The whole purchase by keyboard
  2. The whole purchase with a screen reader
  3. The form at 200 per cent text size
  4. The form with an error in every field
  5. The checkout on a real phone, not a simulated viewport

Frequently asked

Questions readers ask

Why does checkout accessibility affect revenue?

Because a customer who cannot complete the checkout does not buy. Custom dropdowns that need a pointer, modals that trap focus and payment fields skipped by the tab order all block customers who were ready to pay.

What should I test first in a checkout?

Complete a purchase using only the keyboard. Most teams have never done this on their own site and most find a blocker within two minutes. Then repeat with a screen reader, at 200 per cent text size, and with an error in every field.

Are placeholder labels a problem?

Yes, and it is the most common accessibility fault in checkouts. Once the customer starts typing they can no longer see what the field was for. Persistent labels outside the field cost nothing and remove the problem for everyone.

About the authors

Nazir Abbas

Written by

Nazir AbbasApproved contributor

Web Developer & Co-Founder

Builds and maintains ecommerce sites in React, Next.js and WordPress, and handles the technical side of search.

Javed Iqbal

Contributed by

Javed IqbalApproved contributor

SEO Specialist & Co-Founder

Leads search, with more than five years in ecommerce and technical SEO for businesses in the UK, the US and the UAE.

Editorial process: every article is written by one of the two co-founders and reviewed by the other before publication. Technical claims are checked against how the systems actually behave, and anything we cannot evidence is left out rather than asserted.

Related reading