How current laws shape WCAG? – Interview with Bet Hannon

In today’s episode, we have a special guest who will be diving deep into the world of website accessibility and the various legal landscapes surrounding it.

Bet Hannon is the CEO of AccessiCart, a services agency that helps eCommerce and high user-interaction sites remove barriers for customers with disabilities and meet web accessibility compliance requirements (like ADA and the EAA – the European Accessibility Act). Bet is a contributor to the WordPress Project, a speaker at Meetups & WordCamps, and is the cofacilitator of the WordPress Meetup in Bend, Oregon where she lives.

Joined by our host, Maciej, Bet sheds light on the critical aspects of ensuring websites are accessible to all users, including those with disabilities. She breaks down the key differences between B2B websites and consumer-focused services, and why companies targeting an older demographic need to prioritize accessibility. We’ll also explore the impact of the Americans with Disabilities Act (ADA) on web accessibility and the rise of predatory lawsuits driving businesses to comply.

Bet discusses the evolution of accessibility laws, both in the US and Europe, and the varied enforcement mechanisms and penalties that come with non-compliance. From the importance of minimalistic website design to the role of accessibility experts, this episode is packed with insights on making the digital world more inclusive.

Plus, we’ll touch on innovative exercises like “Mouseless Mondays” to foster empathy and the significance of user feedback in creating genuinely accessible websites. Whether you’re a business owner, developer, or designer, you won’t want to miss this essential conversation

The Legal Roots of Digital Accessibility

Bet starts by explaining that digital accessibility has its foundation in the same principles as physical accessibility. The ADA, for example, never explicitly mentioned websites when it was first passed in 1990, but its purpose — ensuring equal access — naturally extends to the web.

“Accessibility is fundamentally about equal access — the law just formalizes what should already be a design default.”

She notes that early lawsuits in the U.S. (like Domino’s Pizza v. Robles) helped clarify how digital accessibility fits into legal frameworks. Even though enforcement varies, the trend is clear: courts increasingly treat inaccessible websites as discriminatory barriers.

Key Takeaway:

Accessibility law isn’t new — it’s the digital continuation of civil rights.

WCAG: More Than a Checklist

While WCAG serves as the global accessibility standard, Bet emphasizes that it’s a set of principles, not prescriptions. The guidelines define what accessible content should achieve, not necessarily how to achieve it.

“WCAG doesn’t tell you exactly what to do, it tells you the outcome that needs to happen for the user.”

She points out that automated tools are a great start, but not enough. Real accessibility requires manual testing, especially by people using assistive technologies such as screen readers or keyboard navigation.

Hannon summarizes it simply: automated testing checks for compliance, but humans test for usability.

Key Takeaway:

True compliance means usability — not just passing audits.

The Global Shift: How the EAA Raises the Bar

The European Accessibility Act (EAA) is one of the most influential upcoming regulations. As Bet explains, its impact will reach far beyond the EU.

“The accessibility act really covers a lot more things than just websites. It covers products and services… and if you’re running an ecommerce site that has EU customers, you’ll need to comply.”

The EAA expands the scope of accessibility requirements to cover e-commerce, banking, transport, and digital communications, introducing market penalties for non-compliance. For many organizations, it’s the first time accessibility has been treated as a business-critical issue rather than a “nice-to-have.”

Key Takeaway:

The European Accessibility Act makes accessibility a market requirement, not an afterthought.

Accessibility in the WordPress Ecosystem

As a veteran of the WordPress community, Bet points out that open-source platforms have a unique role to play in accessibility. WordPress, powering over 40% of the web, can set the tone for global standards.

“We have an Accessibility Team inside WordPress, and they’re doing great work — but there’s still a lot of education to do.”

She explains that many accessibility issues in WordPress come from third-party themes and plugins that don’t follow WCAG. Developers often focus on aesthetics and features, but accessibility must become part of the default development mindset.

“Accessibility isn’t something you add later. It has to be baked in from the start.”

At the same time, Bet highlights the positive trend: more contributors are testing accessibility locally, reporting issues, and treating inclusive design as part of the quality assurance process.

Key Takeaway:

In WordPress, accessibility success depends on collaboration — not just code.

The Future of Accessibility: From Law to Culture

Toward the end of the conversation, Bet turns philosophical — and practical. She believes that laws can spark change, but culture sustains it.

“Accessibility is a journey. You’re never done, because technology and users keep changing.”

For organizations, that means building ongoing systems for accessibility, not one-time audits. Training teams, budgeting for continuous improvement, and listening to feedback from users with disabilities should become part of the company culture.

“It’s not about perfection. It’s about progress and empathy.”

 

Key Takeaway:

Accessibility maturity comes from mindset, not mandates.

Website Accessibility FAQ

1. What is the European Accessibility Act (EAA), and who does it apply to?

The EAA is a set of regulations aimed at making websites and digital products more accessible to people with disabilities. It applies to businesses operating in the EU or serving EU customers. Microenterprises with less than 10 employees or annual revenue under 2 million euros are currently exempt, but this may change.

2. Why is e-commerce specifically mentioned in the EAA?

E-commerce is highlighted because it plays a vital role in enabling people with disabilities to participate in society and access goods and services independently. The EAA aims to ensure equal access to online shopping for all.

3. What are the benefits of website accessibility beyond compliance?

Accessibility offers several benefits, including:
– Expanding your audience by catering to the estimated 20-25% of adults with disabilities.
– Tapping into a significant market of consumers with disabilities.
– Improving SEO and overall website usability for all users.

4. How long does it typically take to make a website compliant with accessibility standards?

The time required depends on the website’s complexity and existing accessibility level. It can take anywhere from 6 to 9 months or even longer for large and complex websites.

5. Where can I find information about the specific requirements for website accessibility?

The Web Content Accessibility Guidelines (WCAG) are the internationally recognized standards for website accessibility. WCAG 2.2 is the latest version and is the one you should strive to follow.

6. What are some common accessibility issues found on websites?

Common issues include:
– Lack of alternative text for images (alt text).
– Poor color contrast, making it difficult for people with visual impairments to read text.
– Inaccessible navigation menus that cannot be operated with a keyboard.
– Ambiguous link text that doesn’t provide context for screen reader users.

7. Are automated accessibility tools sufficient for ensuring compliance?

Automated tools are helpful for identifying about 30% of accessibility issues. However, they cannot replace manual testing and human judgment, especially for complex issues related to keyboard navigation and context-specific problems.

8. What are overlay plugins, and why are they often problematic for accessibility?

Overlay plugins claim to automatically fix accessibility issues by adding a layer of code to your website. However, they often: – Only address a limited set of issues (around 30%). – Create new barriers for some users, particularly those who rely on assistive technologies like screen readers. – Can raise privacy concerns. – May make your site a target for lawsuits, as they signal a lack of genuine commitment to accessibility.

Full conversation with Bet Hannon

Want to hear the full conversation with Bet Hannon? Check out the latest 🎙️ Osom to Know podcast.

You can also watch us on YouTube – don’t forget to hit subscribe! 📩

And if you’re looking for a partner who can look after your website accessibility don’t hesitate to contact us.