In this episode co-hosts Anne Bovelett and James Kemp are joined by Amber Hinds from Equalize Digital.
The conversation centers around the importance of accessibility in web development, particularly for WooCommerce shops. They highlight the contributions of the Accessibility Checker plugin and the collaboration between WooCommerce and Equalize Digital to tackle accessibility issues.
The conversation also touches on the European Accessibility Act, the benefits of accessible websites, and best practices for plugin and theme developers. The episode encourages developers and shop owners to prioritize accessibility to enhance user experience and comply with emerging regulations.
Our sponsors keep the lights on.
Take a moment to check them out.

Since 2005, Automattic has built tools for the open web including WordPress.com, WooCommerce, and Jetpack that are used by millions of people to create, sell, and publish online. They believe in ownership, flexibility, and open source and we’re grateful for their support. Learn more at automattic.com.

Omnisend just dropped SMS pricing to $0.007, and their migration team moves your automations, templates and contacts in five days, free. That means you could be saving up to 35% in less than a week. We’re glad to have them supporting the show and the community we’re building around it. Use the code OpenChannels and get 30% off your first 3 months of any paid plan.
Key Takeaways
The Importance of Accessibility in E-Commerce: Accessibility is not just about compliance; it’s a way to expand your audience, improve user experience, and increase conversions. An accessible website ensures that everyone, including people with disabilities, can navigate and interact with your store effectively.
WooCommerce’s Commitment to Accessibility: WooCommerce is working to make its core product and extensions fully accessible. Recent audits of its front-end output have identified and addressed key issues, with plans to complete conformance by June 2025, ahead of the European Accessibility Act deadline.
The Role of Accessibility Checker: Equalize Digital’s Accessibility Checker plugin is a powerful tool for identifying and addressing accessibility issues. Its free and pro versions help users audit their sites, detect issues like color contrast problems, and even automate some fixes.
Accessibility Boosts SEO and Conversion Rates: Fixing accessibility issues like proper HTML semantics not only improves usability for all users but also boosts search engine rankings and reduces bounce rates. This creates a win-win for businesses aiming for higher traffic and conversions.
Legal and Financial Implications of Accessibility: Compliance with accessibility standards like WCAG 2.1 AA is becoming mandatory in many regions, including the EU, where non-compliance could result in fines or legal action. Businesses targeting global markets need to ensure compliance to avoid penalties and reputational risks.
Education and Collaboration Are Key: Educating plugin and theme developers about accessibility is crucial for creating an ecosystem where non-technical users can build accessible websites. Collaboration between accessibility advocates and developers, like the partnership between WooCommerce and Equalize Digital, sets a strong example.
Practical Tips for Website Owners: Manual testing, like navigating your website without a mouse or using a screen reader, complements automated tools to identify accessibility barriers. Choosing plugins and themes with clear accessibility information ensures a better foundation for compliance.
Accessibility Benefits Everyone, Including Older Audiences: Disabilities can affect anyone, whether from aging, accidents, or illnesses. Accessible websites cater not just to people with permanent disabilities but also to those with temporary or situational limitations.
The Long-Term Value of Accessibility: A website built with accessibility in mind has a longer lifespan and is better prepared for growth. As businesses scale, accessibility ensures they remain compliant with laws and inclusive to all customers.
Resources for Learning and Improvement: Equalize Digital’s free Small Business Accessibility Playbook and accessibility meetups provide valuable guidance. WooCommerce’s upcoming accessibility knowledge base will further support developers and users in building accessible solutions.
Connect
Links and Resources
- Accessibility Checker Plugin
- Shop.EqualizeDigital.com
- WordPress Accessibility Meetup
- Small Business Accessibility Playbook for WordPress
- WebAIM’s Million Report
Timestamps and Chapter Titles
- 00:00 Introduction
- 01:08 Introduction to Equalize Digital
- 03:49 Features of the Accessibility Checker Plugin
- 06:24 Collaboration with WooCommerce
- 10:40 Importance of Accessibility in Web Development
- 14:01 Challenges and Solutions in Accessibility
- 18:28 WooCommerce’s Commitment to Accessibility
- 23:47 Future Plans for WooCommerce Accessibility
- 26:09 WooCommerce Accessibility Audit Overview
- 27:27 Audit Findings and Next Steps
- 30:32 Importance of Manual Testing
- 31:27 European Accessibility Act and Compliance
- 33:05 Building for the Future
- 35:02 The Business Case for Accessibility
- 37:23 Challenges and Considerations
- 39:44 Commitment to Accessibility
- 44:17 Resources and Final Thoughts
Episode Transcript
Anne:
Hello everyone. It’s been a while, but welcome to a new episode of All Things We’re Pressing Accessible at the Do the Woo podcast. My name is Anne Bovelett. I am your co-host today, and with me are Amber Hinds from Equalize Digital and James Kemp from WooCommerce, who recently changed positions. So I don’t actually even know what his official title is today, but I’m sure they’re going to introduce themselves. So Amber.
Amber:
Thanks for having me. I’m excited to be here. I am the founder and CEO of Equalize Digital, which is a company focused on WordPress accessibility. We do accessibility audits, user testing, and remediation. We also have a WordPress plugin called Accessibility Checker that can scan your website for accessibility problems and show you those so you can fix ’em.
Anne:
Wonderful. I’m a big fan.
Amber:
Oh, thank you.
Anne:
Yeah, I am. And James, what about you?
James:
Yeah, hi, I’m James. Like you said, my role has recently changed, so I’m now the core product manager for WooCommerce, and that essentially means that I’m overseeing every project that goes into the core plugin.
Anne:
Wonderful. So dear audience, you have to know something upfront. I know both Amber and James; I’ve met them personally. It was a great joy to finally meet Amber in person at WordCamp Europe, and also the same with James. We played this silly game—remember, at one of the booths? It was so much fun. I always think that everybody knows who everybody in WordPress, especially inside the accessibility bubble. But like I say, it is a bubble, and I keep learning that. I think it’s very important that the message goes out about the importance of accessibility and how great it is that you, as a user, don’t have to worry about what’s happening under the hood—the part you can’t really touch.
It’s absolutely amazing to me that Equalize Digital created this plugin that you can install on your website. It doesn’t do hanky-panky with other servers; it’s just on your server, and it will tell you all the issues that it can find automatically. Right? Correct me if I’m wrong, Amber, but automated tools can find up to 35% of accessibility issues, which I think covers the majority of problems that people run into. These are often things caused by the person building the site, like issues with color contrast, content structure, and so on. I would love for Amber to tell us more about that plugin because, in your web shop and websites in general, this is a fantastic tool. I want the world to know about it.
Amber:
Yeah, thanks. So Accessibility Checker—there’s a free version that you can run. It won’t do products in the free version, though. If you have a WooCommerce shop, you’ll need the paid version of Accessibility Checker because we limit custom post types. Otherwise, the free version will handle unlimited posts and pages. But of course, as we all know, paid versions of plugins have lots of neat features.
One of the great features in our paid plugin is that you can set it up, and it will crawl your entire website. It doesn’t matter how big it is—we have WooCommerce shops with hundreds of thousands of products, and they use it successfully. It scans everything, then comes back and tells you about issues like color contrast problems, forms missing labels (like if you’re using a contact form plugin and haven’t labeled fields properly), or headings that are out of order. It can flag empty buttons, empty links, and ambiguous links (like “Click Here” instead of something meaningful like “Buy Our Product”).
There are more than 40 different checks. Recently, about a couple of weeks ago, we did a big release that includes some fixes. For some issues, the plugin lets you toggle a checkbox, and it will fix them automatically. Now, of course, you should always test changes like these on a staging site first, not your live website. That’s very important as a shop owner. But we’ve built in this capability, and we also have audit history in our small business and above plans. This tracks your site’s progress, showing whether you’re improving or, hopefully not, getting worse. It provides tables and graphs to help visualize your progress.
You can even export issues to CSV if you need to import them into a project management system instead of managing them directly in your website. The plugin shows you issues in both the post editor and on the front end, highlighting them directly. We also try to guide users with documentation about fixing these issues, and of course, our support team is happy to answer questions.
Anne:
Yeah, cool. I’m a happy pro user. So what I’m really curious about—and what the audience would probably like to know as well—is how did you guys connect with the team from WooCommerce? How did that go? What happened?
Amber:
Maybe I can give a little backstory, and I’m curious to know, James, you can say right on this podcast how important or relevant this was. I run the WordPress Accessibility Meetup, which is an official WordPress Meetup. It’s on Zoom twice a month. Towards the end of last year, I don’t always speak—most of the time, I’m just the moderator—but we were having a hard time finding someone for a talk right after New Year’s. So I was like, “Okay, I’ll give one over Christmas break.”
I realized we had a lot of customers using WooCommerce that came to us for audits. One of the things that can be challenging when you’re auditing a WooCommerce shop for accessibility is knowing what is coming from WooCommerce and what problems are coming from the 50 plugins installed on the website.
So I thought it would be helpful both for me in my business and to make an interesting talk to figure out what a baseline of accessibility looks like in WooCommerce core with the 2024 theme. Over the holidays last year, I built a functional shop. You can go to shop.equalizedigital.com—it’s a drop-shipping store using core WooCommerce with the 2024 theme. As I built the shop, I accessibility-audited it and opened 50 accessibility issues for WooCommerce. They’ve all been closed now—they’re all fixed. At the time, though, I gave this presentation called, “Can You Build a Low-Code WooCommerce Shop That’s 100% Accessible?” assuming you make the right choices with your content.
I’m curious, James—did that alert you to us? Is that part of how this partnership started, or was that unrelated?
James:
Yeah, that was highly relevant. I already knew who you were from being in the community for a while. I think I put a tweet out—I can’t remember exactly what it said—but it was centered around accessibility and WooCommerce. It was something like, “What would you like to see improved in terms of accessibility?” Either you or someone else linked to your post about the 50 issues. I thought it was an audit you did for a client, but it’s interesting that it was purpose-built for that presentation.
Someone linked me to that post, and at the time, those issues hadn’t been addressed yet—or a lot of them hadn’t.
Amber:
Yeah, they sat for a couple of months before getting attention.
James:
Right. That ties into why they eventually got fixed. At that point, I connected with some people internally and said, “Look, we’ve got this awesome list of 50 things that would help make WooCommerce more accessible. We should fix these.”
The biggest issue was finding the capacity to do it. We had other projects underway that would’ve been hard to drop. That’s where our partnership with TenUp came in. TenUp had some capacity available, and we assigned those 50 issues to them. They worked on implementing all the fixes, and I think they pushed through reasonably quickly. At this point, they’re resolved.
So that was definitely the starting point. I don’t know if you want to go further into where we’re at now, or if you want to lead into that more, Anne?
Anne:
Oh, yeah, I’d love to learn more. I also want to say something in between because, again, we are living in a bubble. For us, accessibility feels like the most natural thing in the world, but I still notice that a lot of people are like, “What are you talking about?” Or worse, they say, “Blind people don’t visit my website.”
We hear that line all the time. I recommend anyone listening to this to share this podcast with fellow web creators, or anyone really, because creating an accessible website can actually increase your conversion rates like nothing else. It’s always fascinating when you talk about conversions in web shops and bring up accessibility. Financial stakeholders often say, “Give me the numbers. How many disabled people visit my website?”
That’s when you have to explain that you can’t measure assistive technology usage for security and privacy reasons. I like pointing people to articles about how accessibility increases conversions. But what usually works is addressing companies directly: “How much are you paying your SEO company? A lot, right? How’s your bounce rate? Oh, it’s big? Let’s talk about why.”
Amber:
Yeah, there’s so much overlap between accessibility and SEO. We’ve seen that with some of our customers. One example wasn’t an e-commerce shop but a community college. They came to us wanting remediation work. We didn’t do any redesigning except for fixing color contrast. It was literally the same website from a design standpoint and the same from a content standpoint. They weren’t adding new content or blogging or anything like that.
We just fixed the underlying HTML behind the elements. That meant rebuilding a lot of things, like their accordions, tabs, and headings where they’d just bolded paragraphs. We saw a big increase in traffic and applications to the college without changing any content or design. It was purely semantic changes. It made the website easier to find and easier for people to navigate and complete the actions they wanted to take.
Anne:
Did you blog about this one?
Amber:
Yeah, I actually co-presented a talk at a conference with the community college. I can send you a couple of links to include in the show notes.
Anne:
Yeah, please do! I’m especially excited to hear this because I don’t know when this episode will air, but I’m the keynote speaker for WordCamp Netherlands on Friday. This is exactly the kind of thing I’ll be talking about.
To circle back: people don’t realize how much their conversion depends on the accessibility of their website. If you have questions, check the show notes to see how to reach us and learn about accessibility. It’s not as scary or difficult as people think, right?
Speaking of scary and difficult, here’s something I’d like to ask you, James. Accessibility can be a hot potato in development teams. In my experience, people often interpret accessibility feedback as, “You don’t know what you’re doing.” It’s not what we’re saying, but that’s how people feel—it’s like you’re telling them they’re not good coders. How do you approach this within your team so others can learn from it and see it’s not that scary?
James:
That’s an interesting question. For context, I ran a plugin company for WooCommerce, building extensions to extend WooCommerce’s functionality. In that time, I connected with a lot of people in the WordPress space. My main platform for doing that was Twitter/X. When I joined WooCommerce, I found it a great platform to connect with the community.
That’s one reason why the product manager role was a good fit for me. I had experience with the community, building products for WooCommerce, and WooCommerce itself. One of my goals when I joined was to bridge the gap between the community and what happens behind the scenes at WooCommerce.
Accessibility was one of the first projects where I could put that bridge to good use. I brought feedback from the community about accessibility to the team that could address it. I spoke to Beau, our head of engineering, and said, “We have this list of accessibility issues. Let’s fix these.”
Everyone was aware we had accessibility issues. Honestly, I believe most websites and platforms have accessibility issues.
Amber:
That’s true—96%.
James:
Yeah, I was going to say 90%, then thought maybe 80%. But no.
Amber:
No. Have you heard of WebAIM’s Million Report?
James:
No, I don’t think so.
Amber:
WebAIM is an organization out of a U.S. university. Every year, they crawl the top 1 million websites by traffic and run an automated test based on their WAVE scanner. They’ve published a report for the past 10–15 years. This year’s stat is that 96% of homepages have easily detectable accessibility problems.
If you’ve never intentionally worked on accessibility for your website, I can guarantee there are problems.
James:
Yeah, 100%.
Anne:
The good news is most of these problems are things you can fix yourself—at least until you hit a point where you need professional help. That’s the beauty of WordPress and our community. The people building WordPress and its ecosystem are very accessible. I know it’s a bad pun, but it’s true.
You can reach out through Slack, GitHub, or even social media. Most people will respond positively, helping you or pointing you in the right direction. You don’t have to be a developer to do this. You can say, “I don’t know how to fix it,” and people will guide you.
Amber:
Absolutely.
Anne:
So, you went internally and said, “We know we have accessibility issues.” How did that go, James?
James:
Actually, it went fine. Everyone agreed that we needed to fix these issues. As I mentioned, we worked with TenUp, who had capacity to handle them. Once that project started, it was smooth sailing.
I think it’s important to set users up for success. While we can’t control everything, like plugins or themes users install, our goal is to provide the best possible starting point and recommend ways to maintain that accessibility.
Amber:
Yes. That’s something I’ve been advocating for: plugin and theme developers need to prioritize accessibility. Most websites aren’t built by developers. They’re built by DIYers, designers, or business owners. They need tools that don’t require them to fix technical problems.
If WooCommerce and its ecosystem can provide an accessible foundation, it makes a huge difference. Developers and users alike benefit.
Anne:
This is an ultra-interesting point from a commercial perspective, James. This is more directed at you and WooCommerce in general. I know you have your marketplace, and I’m sure you thoroughly review what’s being sold there regarding accessibility. But, of course, there are reasons why not every plugin or extension created for WooCommerce is listed on the marketplace.
Is there any thought about creating incentives to motivate plugin creators to ensure they don’t hinder the accessibility of the entire store? Because that’s essentially what’s happening. A good example is cookie plugins. I don’t use analytics on my website because the cookie plugins I like have issues like keyboard traps. This is just an example, but do you have any standpoint on that? Or maybe even some news?
James:
I don’t have any news, I’m afraid. But we’ve discussed this in the past. The marketplace is managed by a different team than mine, so I only know what I’ve heard. One idea we’ve touched on is a badging system to indicate whether a plugin is “Accessibility Ready.” That’s the terminology we’ve considered using because, as we’ve said, anything can be accessible, but if used irresponsibly, it may not stay that way.
A badging system would help differentiate plugins. If two similar plugins are available, and one is labeled “Accessibility Ready” while the other isn’t, that becomes a selling point. I think that approach could work.
Another thing we want to do—and haven’t yet—is create an accessibility section on the WooCommerce website. This would detail how the core product is accessible and act as a knowledge base for third-party developers, guiding them on how to ensure their plugins are accessible.
Amber:
I think I owe you some content for that.
James:
You do, yes. But we’re still waiting on…
Amber:
That’s on my plate this week, actually.
James:
Good timing! This ties into where we are now. For context, earlier this year at WordCamp Europe, Darren (from WooCommerce) and I hosted a dinner for WooCommerce developers, agencies, and team members. Amber and Chris were among the attendees.
Separately, I met with Anne and Bette, another accessibility expert in the WordPress space, specifically around e-commerce. The sense I got from those conversations was that while we were addressing issues Amber had raised earlier, we needed to do more. We want to lead the way in accessibility, which I believe we should.
After some discussions, the solution we came up with was to conduct a full accessibility audit of the WooCommerce plugin. Initially, we decided to focus on the front-end output—the HTML for checkout pages, product pages, and anything WooCommerce renders on the front end. We wanted that to be 100% accessible out of the box.
Amber’s team completed the audit, and I believe 80 issues were raised. Does that sound right, Amber?
Amber:
Yes, that’s right. It’s important to note that this was just WooCommerce core—we didn’t include add-ons, payment gateways, or anything like that. We tested all shortcodes and blocks, whether users are implementing the shortcode or block versions, as well as product single pages and account pages.
James:
Right. We also included deeper pages, like hidden account pages or the “Order Received” page, which isn’t directly accessible through navigation but is part of the user journey.
Amber:
Exactly. We did a full audit. There weren’t as many issues as you might expect—probably because some had already been resolved.
James:
There would’ve been 130 issues if you hadn’t preemptively fixed some things.
Amber:
Yes. TenUp is now working through those remaining issues. Once they’re resolved, we’ll retest everything and write an official Accessibility Conformance Report. This report will show exactly how WooCommerce core aligns with the Web Content Accessibility Guidelines (WCAG). We’ll also include European accessibility standards.
Anne:
That’s fantastic.
Amber:
It’s worth noting that while there were issues, many components already had solid foundations. Labels were in place, screen readers announced content correctly, and there weren’t glaring errors. Most of the work was about refinement, like improving ARIA attributes or label accessibility.
James:
Exactly. It’s a lot of refinement work. We aim to meet the highest levels of accessibility, and if there are reasons we can’t meet certain points, the conformance report will explain why. So far, though, most things should be achievable.
Amber:
I think so too. The goal is for WooCommerce to be 100% WCAG compliant by June of next year. I suspect it’ll happen sooner. That June 2025 deadline aligns with the European Accessibility Act, which requires e-commerce stores to meet WCAG 2.1 AA compliance.
For store owners listening, WooCommerce is doing its part, but you’ll also want to check your own store to ensure it’s accessible. As the store owner, you’re ultimately responsible for compliance.
James:
And you can check your store with your plugin.
Amber:
Yes, you can use Accessibility Checker, but manual testing is also crucial. After scanning your site, go to the front end, turn off your mouse, and put it in a drawer. Use only your keyboard to navigate and perform tasks like searching for products, adding items to your cart, and completing checkout.
Testing with a screen reader is also essential. If you’re unsure how to do that, hire a professional, especially if your store is large or generates over €2 million in revenue annually—that’s the compliance threshold for the European law.
Anne:
Plus 10 employees.
Amber:
Yes, or 10 employees. If you meet either threshold, it’s worth hiring someone to test your site for compliance.
Anne:
Yeah, I think it has to be both. This is an interesting segue into another topic because the European Accessibility Act is a big deal. We often hear people say, “I make less than €2 million, or my client makes less than €2 million.” It’s important to come at this from a “yes” perspective, but I also want to stress that anyone offering commercial services—building webshops for clients—can no longer get away with consciously building inaccessible websites and claiming ignorance.
We don’t have a strong culture of lawsuits in Europe like in the U.S., but the legal landscape is changing. I asked a lawyer, “Can you exclude accessibility liability in your terms and conditions?” And they said, “No way.” This is vital information for professionals to know. Yes, accessibility compliance is important, but beyond compliance, it’s about the revenue people are walking away from when their websites aren’t accessible.
Amber:
The other thing to consider is that e-commerce stores are built to last. Sure, a new business might only make €250,000 a year now, but what’s the lifespan of that website? I’m still supporting sites I built as a freelancer 10 years ago. Should they still be using the same theme and plugins? Probably not, but it happens.
A WooCommerce store, especially one built with solid plugins and minimal random add-ons, could have a very long life. Over time, that business could easily cross the €2 million threshold. As web professionals, we need to think about building sites that position our clients for long-term growth and success.
HTML semantics, SEO benefits, performance—it’s all connected. Accessibility isn’t just about compliance; it’s about building highly optimized websites.
Anne:
Absolutely.
James:
Anne’s point is also relevant. Accessibility isn’t just about compliance; it’s about ensuring everyone can use your website and buy your products. Are there any statistics on how many people browse e-commerce sites without using a mouse?
Amber:
I don’t know that specific stat, but the World Health Organization (WHO) and the CDC in the U.S. say about 1 in 4 people have a disability—that’s 25% of the global population.
Additionally, people with disabilities collectively control over $4 trillion in discretionary income—money they can spend on anything. With the rise in e-commerce post-COVID, it’s likely that people with disabilities are shopping online even more. For example, someone with transportation challenges or visual impairments might find shopping online significantly easier than visiting physical stores.
If the website is coded properly, it’s much easier to read product descriptions and navigate online than to deal with barriers in a physical store.
Anne:
Exactly. And many people have multiple disabilities. I recently spoke with someone from Funka in Sweden who said we often forget about older adults. Aging can bring disabilities, even if someone has been healthy their whole life. The population is aging, and we need to account for that.
It’s also surprising how little people think about who is visiting their website.
Amber:
And disability can happen overnight. An illness or injury could make someone unable to use a mouse temporarily or permanently. If they’re already accustomed to shopping online, they won’t stop—they’ll just seek accessible websites.
A lot of people assume disabilities are rare or that they only affect people born with them, but it’s much broader than that. It could be any of us tomorrow.
Anne:
Absolutely. Think about the kind of website you’d want to use if you suddenly faced a disability.
Amber:
Right. For example, I get frustrated because my smartphone is too big to use with one hand. If a website isn’t logically laid out, I’m gone.
Now imagine a mother holding a child in one arm. She’s the hero of one-handed mobile navigation! And then there’s the secondary audience to consider.
Take baby product shops, for instance. Here in Europe, strollers can cost €1,000 or more. Shop owners often assume young parents are the ones buying them, but it’s usually grandparents, aunts, and uncles making the purchases—and they’re not 25 years old. If the shop’s color scheme is pink and gray with poor contrast, they’re out.
Anne:
Very true. Alright, we could talk about this for hours. So, I think we’ve covered a lot. Is there a specific point either of you would like to make before we wrap up and go about the rest of our day? Is there something special you want to share with the audience?
James:
I think the key takeaway is our commitment to being accessible. As we mentioned earlier, we’ve completed the front-end audit for WooCommerce, and once that’s resolved, the plan is to move on to a back-end audit.
With the back end, we’re a bit more limited because we have to fit within WordPress as a whole. If there’s an accessibility issue in WordPress itself, we can raise awareness, but we can’t necessarily fix it ourselves. That said, there’s still plenty we can address.
After that, we’ll focus on auditing our own extensions, starting with the front end. Most of our extensions are premium, but whether they’re free or premium, accessibility is a priority.
It’s an ongoing effort, and I’m excited about the outcome. For the front end of WooCommerce core, Amber’s team has completed the audit, and pull requests (PRs) have already been submitted for 30 out of 80 issues. More fixes are coming in every week. Once everything is resolved, Amber’s team will retest, and we’ll publish an official Accessibility Conformance Report. By June at the latest, we aim for the front end of WooCommerce to be fully accessible.
Anne:
I can’t wait to have you both back on the show when that happens.
Amber:
Yes, that’ll be great!
I also want to emphasize to WooCommerce store owners: don’t ignore this. Test your site. Accessibility benefits your business.
When choosing plugins for your site, look for accessibility information on the plugin’s website or listing. If there isn’t any, contact the developers and ask what they’re doing to ensure accessibility. If they can’t provide information or say they aren’t doing anything, consider looking for another solution.
James:
Especially with the EU law.
Amber:
Yes, exactly.
James:
One thing we didn’t touch on is that non-compliance can lead to fines. Amber, didn’t you mention there’s even potential jail time in some cases?
Amber:
Yes, in Ireland. Each EU country can set its own penalties for non-compliance with the European Accessibility Act. Ireland has one of the stricter approaches, but yes, there can be large fines. Canada also has provinces with significant fines for accessibility violations. And in the U.S., non-compliance often leads to lawsuits instead of fines.
James:
If your store is based in the U.S. but sells to Europe, do you still have to comply with European laws?
Amber:
Yes. If you’re intentionally targeting the European market—advertising there or selling products there—you need to comply, just like with GDPR.
It’s also critical to make thoughtful choices about the plugins and themes you use. A lot of the accessibility issues we find during audits aren’t coming from WooCommerce itself but from add-ons or themes that modify WooCommerce. For instance, a client might think, “That’s a WooCommerce issue,” but it turns out to be caused by their theme or a third-party plugin.
That’s why I love using the 2024 theme—it’s a great baseline for comparison. I can show how WooCommerce functions in its default state versus how it functions on a client’s site. If it’s accessible in the default setup but not on their site, the issue lies elsewhere.
Anne:
Very true. And for anyone listening, if this all feels overwhelming—like, “What do I do?”—check the show notes. You’ll find links to Amber, James, and me. Equalize Digital has an incredible amount of practical information about accessibility. Recently, they published a fantastic resource that I’d love Amber to talk about.
Normally, we’re not big on promoting our guests’ work in this way, but this is important. Equalize Digital has made this available for everyone—it’s free, accessible information that can help you tremendously. Amber, please tell us about the book you wrote and how people can get it.
Amber:
Sure! It’s called the Small Business Accessibility Playbook for WordPress. It’s a free ebook available on our website. I’ve passed the link over to you so you can include it in the show notes.
The playbook walks you through the basics of accessibility—how to test for accessibility, common issues to watch for, and a list of plugins we know do a decent job. It’s a practical guide to getting started.
Anne:
Wonderful, wonderful. And your online meetups are fantastic! People should check out Equalize Digital on YouTube or find the Accessibility Meetup online. There’s so much information out there for you to grab.
Amber, thank you so much for doing this. I honestly wonder—do you even sleep?
Amber:
Not very much.
Anne:
Not very much, indeed. I’m constantly in awe of what you and your team are doing. The same goes for you, James. One last question for both of you: Are you going to be at the CloudFest Hackathon?
James:
Not me.
Amber:
Unfortunately, no. But I do hope to attend WordCamp Europe again this year.
Anne:
Oh, that’ll be great!
James:
Me too.
Anne:
Then we’ll see each other in Basel. Alright, thank you both so much for your time and for this wonderful conversation.
Recently, I learned we can also write blogs on Do the Woo.
James:
Yes, we can.
Anne:
I hope we’ll do more of that in the future.
James:
Thank you for having us.
Anne:
Thank you very much, both of you.
Amber:
Thank you.







