WooCommerce and WordPress: accessibility checks before a redesign
The new design is approved. Everyone loves the mock-up. Then someone tries to check out using only a keyboard and gets stuck in the menu.
A redesign can make a WordPress site look newer while making it harder to read, navigate or fill in a form. And accessibility problems are far easier to prevent before launch than to retrofit once every page has been rebuilt. So the useful question isn’t “does it pass one automated scan?” It’s “can people who browse in different ways actually use it?”
On a WooCommerce store, that question runs straight into buying decisions. Product variations, image information, error messages and checkout controls all need to work. A theme change can alter how they behave even when your product content stays exactly the same.
Set the scope and involve the right people
List the templates and essential journeys in the redesign: homepage, category pages, product pages, search, account, cart, checkout and support. Put the flows that let a visitor find, compare and buy a product first. If you can reach users with disabilities, get their feedback early and pay them for it. Don’t assume one person’s experience represents every assistive technology or situation.
Give one person ownership of accessibility, and give them time to review the design and the build. It can’t be handed to a plugin scan at the end. Designers, developers, editors and product owners each control part of the experience. Write down who fixes issues and how critical problems affect the launch decision.
Check structure and keyboard use
Use headings to express the page outline. On a product page, the product name is the main heading, followed by meaningful sections such as description, specifications and delivery details. Don’t pick a heading level because the font size looks right. Styling can change without touching the structure.
Then put the mouse away. This is the first test I run on any redesign, because it takes ten minutes and finds real problems. Check that focus moves through controls in a sensible order, stays visible, and never gets trapped behind a menu or modal. Can you open and close the navigation, choose a variation, review the cart and reach checkout? A skip link helps keyboard users jump past repeated navigation.
Menus and pop-ups deserve extra attention. Test opening, closing, and where focus lands after you dismiss them. A modal shouldn’t leave the page behind it confusingly clickable. And test the real build, not just the prototype.
Review content, labels and errors
Every form control needs a clear label. Placeholder text alone disappears when someone types, and assistive technology may not announce it consistently. Group related fields and say which ones are required. When a checkout error happens, name the field and explain the fix. A red border on its own isn’t an error message.
Write link text that makes sense out of context. “Click here” repeated down a page tells a screen-reader user very little. Buttons should describe the action. Variation controls should expose the selected option, and unavailable choices shouldn’t look as if they can be bought.
Give informative images alternative text, and skip it for purely decorative ones. Product images should help show relevant differences, but the text shouldn’t claim details that aren’t visible or verified. Captions and diagrams need text equivalents when they carry essential instructions.
Check colour, motion and readability
Review text contrast, focus indicators, links and status messages in the new design. Don’t signal stock status, errors or selected states through colour alone. Viewing the interface in greyscale or a colour-vision simulation is a good prompt, but confirm with actual contrast measurements.
Make sure text can be enlarged and reflowed without losing content or functions. Try long product names, translated strings if you have them, and browser zoom. Let people pause distracting animations, and respect reduced-motion settings. I’d rather lose a clever transition than make a control harder to follow.
Test with assistive technology and real content
Automated tools catch some issues, such as missing labels or certain contrast failures. They can’t tell you whether a product description makes sense or whether the purchase flow does. If the team has the skill, use a screen reader for representative tasks, and invite experienced testers for the important journeys. Record the browser, device and assistive technology so findings can be reproduced.
Use real content in the test environment. Placeholder copy has convenient lengths and no tricky terms. Test a product with several variants, an out-of-stock state, a long description, an image gallery and a validation error. Include WooCommerce notices and third-party payment steps in the journey, knowing some external components may need separate fixes.
Include accessibility in launch and maintenance
Keep an issue list with severity, affected template, steps to reproduce, owner and status. Fix shared template problems before you review individual pages. Recheck after plugin, theme or checkout updates, because those can change controls and focus behaviour.
Make accessibility part of content training too. Editors need guidance on headings, link labels, image alternatives and tables. Developers need a review step for interactive components. Give visitors a clear way to report barriers, and make sure someone owns the reply.
Related reading
- WooCommerce and WordPress: category copy that helps shoppers
- WooCommerce and WordPress: editorial workflows for seasonal pages
- WooCommerce and WordPress: redirects after a catalogue restructure
A redesign is a chance to make the site easier for more people to use, but only if the team tests real tasks instead of admiring the mock-up. Pick one key shopping journey, complete it with a keyboard and a screen reader, and fix the blockers before launch. Which journey on your store needs that test first?