<img loading="lazy" alt="Post List Summary Featured Image" src="https://3280432.fs1.hubspotusercontent-na1.net/hubfs/3280432/bigcommerce-ada-compliance.webp">

Blind Users And Payment Forms: Where Adding A Card Breaks Down

By Michael Taylor on Oct 27, 2026
Topics: Web Accessibility, User Experience

0 Comments

Editor’s note: Michael Taylor, who is blind and navigates the web with a screen reader, walks through the barriers he hits when adding a payment method (the expiration date, the billing address, and the default card toggle), and each one is something you can check on your own payment forms today. New to the series? Start with what a screen reader is and how it works.

Expiration Date Entry

Most payment card forms I have used ask for the same information. One data point they all ask for is the card’s expiration date. For whatever reason, this step is often an accessibility mess.

There are two common ways these forms ask for payment.  The first is a split text field, with the two-digit month in the first segment and the two-digit year in the second.

My screen reader doesn't always play nice with these segmented fields. Sometimes focus will not advance to the year portion after I type the month. When I try to move focus there manually, that does not always work as expected either.

In other cases, I can only type one digit in the month segment before focus jumps to the year. That makes it impossible for me to enter the date correctly.

The other common design is a series of drop-down menus or item choosers. Unfortunately, this menu sometimes closes on its own before I reach the value I need.

Selecting a Billing Address

Choosing or entering a billing address can also be a problem. I will start with choosing one from a list of addresses I entered previously.

A strange issue I ran into recently on two different sites was that the picker list read every address the same way. Each entry was announced exactly like the first option. This arrangement made it impossible to select anything but the billing address already showing by default.

Other times, the address options aren't spoken aloud at all, or they are announced as a completely unrelated term, like “Submit.”

When I have to enter a new billing address manually, two issues come up most often. Mislabeled or unlabeled text fields and action buttons can make the form very difficult to navigate. If the street address field uses an autocomplete system, the suggestions are often not accessible to my screen reader, making it impossible for me to complete the form.

Default Card Status

Often, my screen reader misses the toggle when I move through the form to add a new card, so I don’t know I can set it as my default payment method. 

Unfortunately, this option is usually turned on by default. A few times I forgot about it because my screen reader never announced it. Then I started seeing unexplained charges and card activity, because the wrong card was now set as my default payment method.

Even when my screen reader can land on the default card element, it often reads it as static text I cannot act on. That is just as much of a problem.

Where That Leaves Me

Adding a payment method is a necessary step on so many of the websites I use. Based on what I have run into, it is currently not a very accessible process. This needs to change so everyone can be included.

Common questions about payment form accessibility for screen reader users

Can screen reader users enter a credit card expiration date?

Not always. In split month and year fields, focus sometimes wouldn't move to the year, or it jumped there after one month digit, so I couldn't enter the date correctly. On the drop-down versions, the menu sometimes closed before I got to the value I needed.

What happens when saved billing addresses all sound the same to a screen reader?

On two sites I used recently, every address in the list was announced exactly like the first one. I had no way to tell them apart, so I could only use the default.

Are address autocomplete suggestions accessible to screen readers?

Often not for me. When the street address field relied on autocomplete, and the suggestions weren't spoken, I couldn't finish the form.

Can a screen reader miss the “set as default card” option?

More often than not, mine does. That option is usually on by default, so a few times a card became my default without my knowing, and I only found out from unexplained charges.

What to check on your own payment forms

Michael’s account covers the payment forms he's run into, but it's worth checking each barrier on yours. Turn on a screen reader and add a card: does focus move cleanly between the month and year of the expiration date, does each saved billing address announce as itself, are autocomplete suggestions spoken, and is the default card toggle announced as something you can change?

Our post on why blind shoppers often cannot complete online checkout covers what tends to go wrong in the steps around this one.

Payment forms outside of retail show the same problems. Michael ran into unlabeled name and billing address fields when he wrote about what it’s like to pay a healthcare bill when you’re blind.

His earlier post on what he wishes developers and QA teams understood about screen readers is also a good companion to this one.

For teams looking at checkout from the conversion side, our guide to checkout strategies ecommerce teams miss when trying to reduce cart abandonment is a related read.

A payment form a screen reader user can't complete creates the same kind of barrier that shows up in accessibility complaints, and finding one is a reason to look at the rest of the journey rather than a single fix. 

To see where your own pages stand, test your site for free. 

If your team doesn't have the developer bandwidth to work through them, UsableNet Assistive is a managed service: our developers remediate and maintain accessibility issues. Schedule a consultation to discuss how your payment and checkout forms sound to a screen reader user.

Michael Taylor

Michael Taylor

I am a regular contributor to the UsableNet blog on digital accessibility. I develop, write, and edit content for the company blog related to my experiences with digital accessibility. I explore various areas of the digital world and combine my unique perspective as a screen reader user with my fun and creative writing style to deliver an informative and engaging final product. My goal is to advance the company's marketing initiatives while also raising awareness about digital accessibility and how it affects the lives of real-world assistive technology users. My work covers everything from common accessibility challenges to robust and accessible design to tutorial-like content for specific web elements.

Need to improve digital usability, accessibility or performance? We can help.