Black Friday is November 27. Before the rush, it's worth spending a little time on the pages where people actually buy from you: the cart and the checkout.
The people who want to shop with you include people who use a keyboard instead of a mouse, people who use a screen reader, people who find low-contrast text hard to read, and people who need a little more time to fill in a form. A few practical checks now can make those pages easier for all of them.
Here are five things you can try yourself, in a few minutes each. You don't need special software. These checks are a starting point, not a complete review of your site. The W3C, which writes the Web Content Accessibility Guidelines (WCAG), also offers a set of Easy Checks for a first look.
1. Form labels: can every field tell you what it needs?
A shopper using a screen reader hears the label, not the visual layout around the box. Someone who zooms in, or who is filling out a long form, can also lose their place if the only clue is placeholder text that vanishes when they type. A clear, visible label helps everyone know whether a field is for an email, a ZIP code, or a card number.
Open your checkout and look at every field: name, email, address, shipping, payment. Ask:
- Is there a visible label that stays on the screen, not only placeholder text inside the box?
- If you click or tap the label, does the cursor move into the matching field? That usually means the label is tied to the field, which helps screen readers and makes small checkboxes easier to hit.
- Do dropdowns, checkboxes, and radio buttons have labels too, including options like "Same as shipping"?
If a field is missing a lasting label, add one that stays visible, and ask your developer or theme support to tie that label to the field in the code. Placeholder text can stay as an extra hint, but it shouldn't be the only label. In WCAG, this is 1.3.1 Info and Relationships and 3.3.2 Labels or Instructions.
2. Error messages: when something's off, is the problem clear?
People mistype an email, skip a required field, or enter a card number in a slightly different format. If the only signal is a red outline, some shoppers won't see it, because color alone isn't enough. If the message is vague ("Invalid input") or sits only at the top of a long page, someone using a screen reader or the keyboard may not find it, and may not know how to continue.
Try submitting the form with a required field empty, then with a badly formatted email. Ask:
- Is there a text message, not only a change in color?
- Does the message name the field and what's needed? "Enter a 5-digit ZIP code" is more helpful than "Error."
- Can you find the message easily, next to the field or clearly placed at the start of the form?
If the problem is hard to spot or hard to understand, add a clear text message close to the field, and don't rely on color alone. In WCAG, this is 3.3.1 Error Identification, and 1.4.1 Use of Color.
3. Color contrast: can you read the prices, buttons, and fine print?
Sale prices, "Continue" buttons, muted placeholder text, and small shipping notes are easy to miss when the text is too close in brightness to the background, especially on a phone in bright light or for someone with low vision.
Look closely at button text, prices, links, error text, and small print. Paste the text color and the background color into a free contrast checker. For regular-size text, WCAG 1.4.3 Contrast (Minimum) calls for a contrast ratio of at least 4.5 to 1. Large text can be 3 to 1. Also watch for required-field marks or errors that use color alone, such as a red asterisk with no wording next to it.
If the text is hard to read, darken the text or lighten the background until the ratio is high enough, and add a word or symbol in addition to color for required fields and errors. Theme color settings can often do this without a redesign.
4. Keyboard-only checkout: can you place an order without a mouse?
Plenty of people don't use a mouse. Some have a tremor or an injury, some use a switch or voice software, and some simply move faster on a keyboard. For them, the Tab key is how they get from the cart to "Place order."
Put the mouse aside, or unplug it, and open your cart. Then:
- Press Tab slowly through the cart and each checkout step. (On a Mac in Safari, first turn on "Press Tab to highlight each item" in Safari's Advanced settings, or use Chrome.)
- Watch for a visible outline or highlight that shows where you are. If it vanishes, a visitor has no idea what they're about to activate.
- Check that you can reach every field, the shipping choices, "Apply coupon," the payment box, and the final button. Press Enter or the space bar to use them.
- Open any dropdown, calendar, or pop-up and make sure you can use it, close it, and keep going without getting stuck.
- Read the buttons and links as you go. "Place order" or "Apply coupon" is clearer than "Submit" or "Click here."
If you can't finish the purchase from the keyboard, a common cause is a theme or page builder that hides the focus outline, or a custom dropdown or payment widget that only works with a mouse. Payment fields sometimes sit in a box from the payment provider; if those are the ones that get in the way, ask that provider or your developer about a more usable option. Ask your developer or theme support to make each control usable with the keyboard and to bring a visible focus outline back. You can often match the outline to your brand colors. In WCAG, this is 2.1.1 Keyboard, 2.1.2 No Keyboard Trap, and 2.4.7 Focus Visible.
5. Enough time: can a shopper finish without the session disappearing?
Checkout can take longer than we think, especially for someone who types slowly, uses a screen reader, or needs to look up an address or a card. On a busy holiday, carts and payment pages sometimes time out. If the page resets without a warning, the shopper can lose their place and their cart.
Look for a timer on the cart, checkout, or payment step. Start checkout, wait a bit, or step away and come back. Does the session end with no warning? If you are warned, can you get more time with a simple action? Try the same on a phone, where typing often takes longer. If a CAPTCHA appears, try completing it with the keyboard, and look for another option, such as an audio challenge.
If time runs out with no warning, or there's no simple way to get more time, ask your platform or developer to warn people before the session ends and to let them extend it, or to give enough time to complete the form in the first place. In WCAG, this is 2.2.1 Timing Adjustable.
What an automated check can and can't do
Automated tools are useful. They help you find and identify common issues, like missing labels or low contrast, on a page you choose. They can't check everything. Keyboard flow and the steps through checkout need a person. The W3C says it plainly: "Tools cannot check all accessibility aspects automatically. Human judgement is required." (W3C, Selecting Web Accessibility Evaluation Tools)
Our free scan at webmax.co/audit is an automated, partial check of one page. It doesn't cover everything, and it isn't a substitute for walking through the cart and checkout yourself.
If you want a hand
If you'd like a person to go through the whole checkout with you, our team can do a manual audit, fix the issues we find in your site's own code, and stay with you for ongoing support. We work toward WCAG 2.2 AA.
We're here for the people who come looking for help.