New series: what assistive tech really hears on your checkout page. Start with part one →
Shipwright
Home
Accessibility Sep 17, 2026 2 min read 236 views

What a Screen Reader Actually Announces on Your Checkout Page

Mara Okafor

Mara Okafor

@maraokafor

Share

We recorded VoiceOver and NVDA on six checkout flows and wrote down every word they said. Accessibility bugs are easy to miss because they do not show up in screenshots. The only reliable way to find them is to use the interface the way assistive technology users do.

Cover illustration for the article What a Screen Reader Actually Announces on Your Checkout Page
Figure 1. We recorded VoiceOver and NVDA on six checkout flows and wrote down every word they said.

What users actually experience

Most of the problems we found came from custom controls that looked like buttons but were built from generic elements. Switching to native elements fixed focus, keyboard support, and announcements in one step.

  • Use native elements before ARIA.
  • Every interactive element needs a visible focus style.
  • Test with a keyboard before every release.
  • Keep text contrast at 4.5:1 or higher.

Fixing the markup

Automated checkers catch roughly a third of the issues. The rest need a keyboard, a screen reader, and a few minutes of patience. We now budget that time into every feature estimate.

The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.

Tim Berners-Lee, W3C Web Accessibility Initiative launch, 1997

Quick takeaway

Native HTML first; ARIA only to fill the gaps.

Testing with real tools

⌨️

Keyboard first

Everything reachable and operable without a mouse.

🔊

Announced

Screen readers hear names, roles, and states.

🌗

Contrast

Every token pair meets WCAG AA.

Colour contrast is the one area where tooling is excellent. Every text and background pair in the design system has a measured ratio, and the build fails if a new token pair drops below the WCAG AA threshold.

If you try this on your own project, start with one page or one service rather than the whole codebase. A small experiment gives you real numbers to argue with, and it is easy to roll back if the idea does not fit.

We have been running this approach for several months now. The initial setup took about a day, and the ongoing cost is close to zero once the team knows where to look.

None of this is new, and that is the point. The techniques that last are usually the boring ones that are documented well and supported by the platform itself.

As always, the examples are simplified to fit on a page. The production version has more error handling and logging, but the shape of the code is the same.

Questions, corrections, and war stories are welcome in the comments. Several of our best follow-up posts started as a reader pointing out something we had missed.

Wrapping up

As always, the examples are simplified to fit on a page. The production version has more error handling and logging, but the shape of the code is the same.

Mara Okafor

Mara Okafor

Author

Staff frontend engineer focused on CSS architecture and accessibility. Mara has audited more design systems than she can count and still gets excited about a good focus ring.

Related Posts

Comments 0

Leave a comment

Your email will not be published. Sign in for a faster experience.

Supports **bold**, *italic*, and `code`.