Why can't a blind customer check out at my store?

Checkout often fails due to unannounced fields and errors

A blind customer can get stuck at the checkout step for several identifiable reasons. Form fields without a properly linked label cause a screen reader to only announce "input field" without indicating whether it is a postal code, card number, or required field. Error messages that appear only visually — a red border, text not linked to the field — are not read aloud by a screen reader, so a customer may attempt to proceed without knowing something is missing. The order in which a screen reader navigates through the page can also differ from the visual order, causing steps like "select shipping method" or "enter card details" to be announced in illogical sequence or even skipped entirely. Buttons that are technically clickable but not marked as buttons may be ignored by assistive technology.

These problems often compound at the checkout step, because it contains more dynamic elements than a product page: expandable address fields, live validation, a choice of payment methods updated via JavaScript. Each of these elements must be not only visible but also programmatically recognizable — a screen reader works with the underlying code, not what appears on screen. A page that looks flawless to a sighted visitor can fail precisely at that point for a screen reader user.

What WCAG 2.1 says as a standard on this topic

The requirement that form fields, error messages, and interactive elements be correctly recognized by assistive technology is set out in WCAG 2.1 — the practical application of EN 301 549, the standard referenced in the European Accessibility Act. The ACM/Motivaction study of approximately one hundred major online shops (March 2026) shows how often this fails in practice: on 33% of the sites examined, a customer could ultimately place an order but at considerably greater effort, and only 13% were fully operable with a keyboard — a condition closely linked to usability with screen readers, since both navigate a page without a mouse. An automated scan detects some of these issues, such as a missing label, but whether checkout as a whole is logical and fully usable with a screen reader requires an assessment that a scan alone cannot provide.