Website Accessibility Archives - Page 10 of 20/Tag

Common Barriers Found in Accessibility Monitoring
Have you ever tried to use a website or open an email, only to find that some parts are impossible to read or use? That’s exactly what happens to people who face accessibility barriers online. Web accessibility is all about making sure digital content can be used by everyone, including people with disabilities. It covers things like readable text, clear navigation, and even how images are described for those who rely on screen readers.

A great way to keep your website or marketing emails user-friendly for all is through routine accessibility monitoring. Think of accessibility monitoring as a regular check-up that catches problems before they become bigger headaches. This practice is not just about following rules; it’s about ensuring your audience feels valued and included.

The Importance of Ongoing Accessibility Monitoring

Accessibility is an evolving target. Standards shift, technologies change, and user needs grow more complex. That’s why a one-time audit is rarely sufficient. Instead, incorporating accessibility monitoring into your regular workflow offers multiple benefits:

Early Issue Detection

When you track accessibility metrics continuously, you can detect and address accessibility gaps before they become widespread or lead to costly legal issues. This proactive approach helps avoid major overhauls, saving both time and money.

Improved User Experience

The best user experiences are built on consistency and reliability. When a website is accessible, it isn’t just beneficial for users with disabilities—it enhances the site’s overall usability, making it more intuitive and enjoyable for everyone.

Brand Reputation and Trust

Demonstrating a commitment to inclusivity can significantly bolster your brand reputation. Users who find your platform welcoming are more likely to trust your brand, return for future visits, and recommend you to others.

Regulatory Compliance

Accessibility regulations, such as the Americans with Disabilities Act (ADA) in the U.S. or the Web Content Accessibility Guidelines (WCAG) internationally, are increasingly enforced. Routine monitoring ensures your site remains in compliance, mitigating the risk of legal action or damage to your brand image.

Common Accessibility Barriers Identified

Accessibility issues can vary widely from site to site. However, accessibility monitoring consistently highlights some recurring problem areas. Below are a few of the most common explanations of why they matter.

Missing Alternative (Alt) Text for Images

Alt text (or “alternative text”) is a short written description of an image, embedded in the HTML using the alt attribute. This text is essential for screen readers to convey the meaning of the image to users who cannot see it.

Why It Matters
- A user who relies on assistive technology may only hear “image” or “graphic” if alt text is not provided.
- Missing alt text not only harms accessibility but also impacts SEO, as search engines use alt text to understand image context.
Solution

Always add descriptive alt text that explains what’s in the image. For example, “A smiling person holding a coffee cup,” rather than “coffee-cup.jpg.”

Insufficient Color Contrast

Color contrast refers to the ratio between the foreground (text or important elements) and the background. Low contrast can make text and interface elements nearly unreadable for users with visual impairments.

Why It Matters
- Users with color vision deficiencies, low vision, or even older monitors can struggle to perceive low-contrast elements.
- Poor contrast reduces readability and increases user frustration, potentially leading to lost conversions for e-commerce sites.
Solution

Use color contrast tools to check your text and background combinations. Aim for contrast ratios that meet WCAG standards, like a ratio of at least 4.5:1 for most text.

Keyboard Navigation Failures

Not everyone navigates a website using a mouse or a trackpad. Many rely on their keyboard (or keyboard-like devices) to move through links, buttons, and form fields.

Why It Matters
- If a website’s interactive elements are not properly coded for tab or arrow-key navigation, users with motor impairments or who rely on screen readers can become “stuck” on the site or unable to complete essential tasks.
- In e-commerce, this can cause significant revenue loss if customers cannot move through the purchase funnel without a mouse.
Solution

Make sure you can move between all clickable or interactive elements using the keyboard alone. This includes things like buttons, links, and form fields.

Missing Form Input Labels

Forms with missing or unclear labels can create major barriers. Users relying on assistive technology might not understand what data each form field requires.

Why It Matters
- For e-commerce, if a prospective buyer cannot fill out billing and shipping forms, they simply can’t complete a purchase.
- Proper labeling reduces errors, cart abandonment, and user frustration.
Solution

Always pair form fields with clear and descriptive labels. For instance, “First Name” should clearly label the first name field.

Missing or Improperly Structured Headings

Headings (e.g., <h1>, <h2> provide a logical structure for your content, enabling users with screen readers to navigate effectively.

Why It Matters
- Screen readers often rely on heading tags to jump to different sections of the page.
- A lack of proper hierarchy can make content confusing and time-consuming to navigate, especially if headings are out of order (e.g., an <h3> directly following an <h1>).
What Monitoring Reveals

Accessibility monitoring tools and manual audits can uncover pages with mismatched headings, missing headings, or headings used for stylistic purposes rather than structural ones.

Benefits of Accessibility Monitoring for Web Developers and Ecommerce Managers

Whether you’re responsible for building new platforms or maintaining existing ones, the benefits of accessibility monitoring extend far beyond mere compliance:

Reduced Development Bottlenecks

Identifying and fixing accessibility concerns early in the development process prevents technical debt from piling up. Smaller, more manageable updates are generally simpler to implement, saving development resources in the long run.

Increased Conversion Rates

Accessibility improvements often go hand in hand with better user experience. A site optimized for all users naturally boasts higher conversion rates because it eliminates unnecessary friction in the user journey.

Stronger Data

By continuously tracking accessibility metrics, you gain insight into how people actually use your site. This data can help shape design decisions and user research, contributing to a more holistic product strategy.

Mitigated Legal Risks

In many regions, having an inaccessible website can lead to lawsuits or fines. Ongoing monitoring demonstrates due diligence and places you in a stronger legal position if accessibility complaints arise.

Recommended Tools for Accessibility Monitoring

With various platforms and user scenarios to consider, it’s impossible to cover accessibility manually alone. Thankfully, a range of tools exist to help simplify this process:

Automated Accessibility Scanners
- WAVE: A browser extension that highlights accessibility issues right on the page and offers detailed explanations.
- Accessibility Radar (a11y.Radar): An advanced accessibility scanning tool that provides comprehensive reports on accessibility compliance. It integrates seamlessly with development workflows, allowing for continuous monitoring and real-time feedback during the development process.
- Google Lighthouse: An open-source, automated tool for improving the quality of web pages. It includes accessibility audits that evaluate elements like color contrast, ARIA attributes, and more, offering actionable insights to enhance your site’s accessibility.
Color Contrast Analyzers
- Contrast Checker by WebAIM: Allows you to input foreground and background colors to see if they meet WCAG guidelines.
- Accessible Colors: This gives you suggestions on how to modify your color palette for better contrast.
Screen Reader Testing
- NVDA (Windows), VoiceOver (Mac/iOS), and TalkBack (Android) are commonly used screen readers. Testing your site with these tools ensures a real-world perspective.
CI/CD Integration
- GitHub Actions or GitLab CI: Integrate accessibility checks into your development pipeline so that new commits automatically trigger testing for accessibility regressions.
Best Practices to Maintain an Accessible Website

A robust monitoring strategy is only as good as the actions you take based on its findings. Below are some best practices to ensure that your site remains inclusive:

Make Accessibility Part of Your Design Process

Rather than retrofitting accessibility at the end, consider accessibility from the start. Involve accessibility specialists, if possible, during the wireframing and design phases.

Prioritize Semantics and Structure

Use HTML elements according to their intended purposes. Properly labeled headings, lists, and form fields help both users and assistive technologies make sense of your content.

Adhere Strictly to WCAG Standards

Aim for WCAG 2.1 AA compliance at a minimum. Familiarizing yourself and your team with these guidelines reduces guesswork and ensures you’re meeting widely recognized standards.

Incorporate Regular Training

All team members, from designers to content writers, should understand the basics of accessibility. This ensures a unified approach and reduces the likelihood of new barriers being introduced.

Schedule Routine Audits

Even if your tools are robust, manual reviews are still invaluable. Implement a monthly or quarterly accessibility review process to catch anything automated tools might miss, such as nuanced usability concerns.

Create an Accessibility Statement

Let users know your site strives for accessibility. Provide them with a clear channel to report issues, demonstrating that you value their feedback and are committed to continuous improvement.

Conclusion

Maintaining a website that is usable and delightful for everyone requires consistent attention to accessibility. Through routine accessibility monitoring, you can uncover the most common barriers—like missing alt text, color contrast issues, and keyboard navigation failures—and address them long before they negatively impact the user experience or invite legal complications.

216digital offers a variety of accessibility monitoring solutions and packages. If you’d like to know more, please reach out using the contact form below.
Greg McNeil

January 27, 2025

Web Accessibility Monitoring

a11y.Radar, Accessibility, Accessibility monitoring, Web Accessibility, web accessibility monitoring, Website Accessibility
ADA Lawsuits Are Changing: What It Means for You
In 2024, digital accessibility became a critical focus for businesses as ADA compliance lawsuits revealed new challenges and risks. While the number of lawsuits stayed high, the strategies behind them shifted in surprising ways. These changes underscored the growing need for businesses to stay proactive, not just reactive, about accessibility.

Whether you’re a business owner, developer, or part of an e-commerce team, understanding these trends can help you avoid legal pitfalls and create a better online experience for everyone. In this article, we’ll explore how ADA compliance lawsuits evolved from 2023 to 2024 and share practical steps to safeguard your business.

The Rise and Shift of ADA Lawsuits for Websites

In 2023, there were more than 4,500 website-related ADA lawsuits—continuing an upward trend from previous years. By 2024, that number stayed significant, with over 4,000 filings. However, the real story lies in how these cases progressed. While federal lawsuits dipped slightly, state-level claims surged, catching some businesses off guard.

But where are these lawsuits happening most often? Understanding the geographic hotspots for ADA litigation can give businesses insight into where compliance is under the most scrutiny—and help them prepare accordingly.

Geographic Hotspots

New York again stood out as a hotspot for ADA lawsuits. Favorable state laws and a high concentration of plaintiff law firms contributed to a spike in litigation there. California remained a close second, largely due to its “physical nexus” requirement that often ties digital accessibility to brick-and-mortar stores. For businesses operating or selling in these states, the message was clear: staying ahead of accessibility standards is crucial to reduce legal exposure.

Widgets and Overlays Don’t Cut It

It came as no surprise in 2024 that accessibility widgets and overlays repeatedly fell short of their promises. Many of these so-called “quick fixes” only mask deeper barriers instead of truly solving them—an approach that inevitably leaves websites vulnerable to lawsuits. Over 1,000 businesses discovered this the hard way last year, getting hit with legal action despite having widgets in place.

Why Do Overlays Fail?

Widget typically offer superficial features like text-to-speech or color contrast settings, but they don’t fix the underlying coding errors—unlabeled buttons, broken forms, or improper heading structures—that truly affect users with disabilities. Plaintiffs and their attorneys have become more vigilant in spotting these shortcomings, and rightfully so. If a website is rife with barriers, a widget can’t make it magically accessible. Instead, a holistic approach that addresses root design and development problems is the only reliable way to ensure your site is inclusive and shielded from legal challenges.

Even beyond the issues with overlays, businesses faced another growing challenge in 2024: repeat lawsuits.

The Growing Challenge of Repeat Lawsuits

One of the most alarming trends of 2024 was the rise in repeat lawsuits. Around 40% of lawsuits targeted businesses that had already been sued. Yup, repeat lawsuits are on the rise, and they’re exposing a common problem.

Many companies settle a case, fix a few issues, and then move on. But if you only patch up one part of your site—or ignore your mobile app and subdomains—you’re leaving the door wide open for another round of ADA lawsuits.

The lesson here is pretty clear: you need a comprehensive approach to accessibility. That means reviewing every part of your online presence, not just the parts that got flagged before.

Why E-Commerce Websites Were the Hardest Hit

Just like in 2023, e-commerce businesses were a favorite target for ADA lawsuits in 2024. It’s not hard to see why.

Online stores change all the time—new products, fresh promotions, and constant updates. But every tweak and addition is an opportunity for accessibility issues to sneak in. If your product images don’t have alt text or your checkout page isn’t screen reader-friendly, you’re putting up barriers for customers.

And here’s the kicker: it’s easy for plaintiffs to prove harm when they can show they couldn’t complete a purchase because of these barriers. That makes e-commerce sites a prime target.

The takeaway? Prioritize accessibility. It’s not just about avoiding lawsuits—it’s about making shopping easier and more enjoyable for everyone.

What You Can Do to Avoid ADA Lawsuits

So, what’s the game plan for staying out of trouble? Here are some practical steps to help you avoid ADA lawsuits:
1. Audit Your Site Regularly: Use tools to check for issues like missing alt text, poor keyboard navigation, or inaccessible forms. And don’t stop at automated tools—manual checks are just as important.
2. Work With Accessibility Pros: Partner with experts who can guide you through the process of making your site compliant.
3. Educate Your Team: Train your developers, designers, and content creators on accessibility best practices. The more they know, the fewer issues they’ll create.
4. Involve Real Users: Test your site with people who use assistive technologies. Their feedback is invaluable.
5. Ditch the Widgets: Instead of relying on overlays, invest in long-term fixes that address the root of your accessibility challenges.
Accessibility: A Legal Requirement and a Moral Choice

The rise in ADA lawsuits from 2023 to 2024 proves that accessibility isn’t going away. If anything, the pressure to comply will only grow, especially with new guidelines like WCAG 2.2 and increased enforcement from the Department of Justice.

But accessibility isn’t just about avoiding lawsuits. It’s about making the internet a more inclusive space. When your website is accessible, you’re opening your doors to everyone, regardless of ability.

Don’t leave accessibility to chance. At 216digital, we specialize in helping businesses like yours navigate the complexities of digital accessibility. From comprehensive audits to ongoing support and monitoring through our a11y.Radar tool, we’ve got you covered. Let us help you stay compliant, reduce your risk, and create a website that works for everyone.

Take the first step today—schedule your ADA compliance consultation with 216digital. Together, we’ll build a more inclusive digital experience for your business and your customers.
Greg McNeil

January 23, 2025

Legal Compliance

2024 accessibility lawsuits, Accessibility, ADA Lawsuit, ADA Lawsuits, web accessibility lawsuits, Website Accessibility
Accessibility Testing: Prioritize Fixes That Truly Matter
Accessibility can feel like an overwhelming mountain to climb. Every round of accessibility testing uncovers new problems—some obvious, others hidden deep in the code or design. Where do you start when everything seems important? What if you tackle the wrong issue first, leaving users still stuck?

These questions are important, and the answers can transform how your website serves all visitors. This guide isn’t just about fixing problems—it’s about focusing your efforts where they matter most. By exploring WebAIM’s four-level severity framework, you’ll learn how to prioritize issues effectively and make meaningful progress toward an inclusive website. Let’s dive in and figure this out together.

WebAIM’s Four-Level Severity Framework

WebAIM (Web Accessibility in Mind) categorizes accessibility issues into four levels of severity based on their impact on users. These categories help prioritize fixes by focusing on barriers that significantly affect user experience and access.

Critical Issues

Critical issues completely block users from accessing specific parts of your website or performing essential tasks. Addressing these issues should be the highest priority. Examples include:
- Interactive elements, such as buttons or form inputs, that cannot be reached or activated using a keyboard.
- Videos without captions, which exclude users who are deaf or hard of hearing.
- Content that flashes or strobes in a way that could cause seizures for individuals with photosensitive epilepsy.
To prevent these barriers, developers should prioritize using accessible, native HTML elements and perform thorough accessibility testing, including keyboard and screen reader evaluations, during the development process.

Significant Issues

Significant issues do not entirely block access but make interacting with the website cumbersome or frustrating for users. Examples include:
- Missing visual focus indicators, which make it challenging for keyboard users to identify the currently focused element.
- Poor color contrast that makes text difficult to read for users with visual impairments.
These issues disrupt the user experience and should be addressed soon after critical issues to enhance accessibility.

Moderate Issues

Moderate issues require users to expend unnecessary effort or time to navigate and interact with web content but do not entirely impede access. Examples include:
- Lack of properly structured semantic HTML, such as headings and regions, which slows navigation for screen reader users.
- Generic or vague descriptive link text (e.g., “Click here”) that fails to describe the destination or action clearly.
- Animations that lack user controls, making it difficult for some users to focus on other content.
Comprehensive accessibility testing ensures these moderate issues are identified and addressed to improve usability for all users.

Minor Issues

Minor issues do not create significant barriers but contribute to a polished and professional user experience when resolved. Examples include:
- Slight inconsistencies in focus styles for keyboard navigation.
- Overuse of ARIA attributes, such as redundant tabindex values on elements that are already focusable.
While not urgent, fixing minor issues during routine updates demonstrates attention to detail and commitment to accessibility best practices.

Step-by-Step Guide to Prioritizing Accessibility Fixes

Feeling unsure where to start? Don’t worry—you’re not alone. Here’s a simple plan to categorize and tackle accessibility issues step by step:

1. Conduct a Comprehensive Accessibility Audit

Begin by testing your site with tools like WAVE and Lighthouse. Then, complement these results with manual testing—navigate your site with a keyboard, try a screen reader, and zoom your browser window. Automated tools catch many issues, but hands-on testing uncovers usability challenges they miss.

2. Categorize Issues by Severity

Use WebAIM’s framework to prioritize fixes:
- Critical issues should top your list, as they directly prevent access.
- Serious issues come next, addressing significant usability gaps.
- Moderate and minor issues can be grouped for later phases.
A structured approach to accessibility testing ensures the most pressing barriers are resolved first.

3. Consider the Impact on Your Audience

Think about how each issue affects your users. For example, missing alt text on product images affects a wide audience and should take precedence. If you have user feedback, use it to identify pain points that need urgent attention.

4. Focus on High-Traffic and High-Value Pages

Start your efforts where they’ll have the greatest impact:
- Homepage and landing pages.
- Key interaction points like forms or checkout pages.
- Frequently accessed resources such as blogs or FAQs.
By targeting these areas during accessibility testing, you ensure that the improvements benefit the largest number of users.

5. Use a Phased Approach for Moderate and Minor Issues

After resolving critical and serious issues, create a plan for tackling moderate and minor ones. For instance:
- Update heading structures during new content creation.
- Fix descriptive link text during routine content reviews.
Breaking these tasks into smaller phases makes the process manageable and less overwhelming.

6. Test and Retest

After making fixes, conduct accessibility testing again. If possible, involve users with disabilities to confirm your solutions work in real-world scenarios. Their feedback is invaluable and can guide future improvements.

Tools and Techniques for Effective Accessibility Testing

A good mix of tools and techniques ensures you catch both technical and usability issues. Here’s what to try:
- Automated Tools: WAVE and Lighthouse are great for spotting common errors.
- Manual Testing: Use a keyboard or screen reader to experience your site like some users do.
- Color Contrast Checkers: WebAIM’s Contrast Checker ensures text is easy to read.
- User Testing: Working with people who have disabilities provides first hand insights.
Why Prioritization Matters

Prioritizing fixes has clear benefits:
- Faster Results: You can address critical barriers quickly and make your site accessible sooner.
- Better Use of Resources: Time and budget go toward solving high-impact problems.
- Happier Users: Fixing severe issues first improves usability for everyone.
Taking things one step at a time, with regular accessibility testing, makes the process less overwhelming and helps you steadily improve your site.

Final Thoughts

Accessibility can feel like a big undertaking, but it doesn’t have to be. By focusing on the most critical barriers first and conducting consistent accessibility testing, you can make real progress without burning out. Accessibility isn’t a one-time project—it’s an ongoing commitment to creating a better digital experience for all.

Imagine how many more people could enjoy your site if it were accessible to everyone. Whether you’re a developer, IT director, or content creator, each step you take helps make the web a more inclusive place.

And you don’t have to do it alone. 216digital is here to help. From audits to ongoing accessibility testing and monitoring, we’ll guide you every step of the way. Together, we can create a website that’s user-friendly, inclusive, and aligned with the latest standards. Schedule your consultation today, and let’s get started making your site the best it can be!
Greg McNeil

January 21, 2025

How-to Guides

Accessibility, Accessibility testing, automated testing, How-to, WebAIM, Website Accessibility
Why Legal Compliance for Websites Matters in Canada
Imagine landing on a website and feeling stuck because you can’t navigate it properly, read the content, or interact with its features. Frustrating, right? Now imagine that being your daily reality. For many people with disabilities, this is how they experience the web.

That’s where web accessibility comes in. It’s about making sure everyone—regardless of ability—can use websites with ease. Not only is this the ethical thing to do, but it’s also a requirement for legal compliance for websites in Canada and beyond.The good news? It’s easier to achieve than you might think, and it comes with benefits that go far beyond ticking a legal box.

Why Web Accessibility Matters

Web accessibility ensures that everyone, including people with disabilities, can use your website effectively. In Canada, over one in five people have a disability. By making your website accessible, you’re opening it up to a wider audience, improving your SEO, and building a stronger brand.

Failing to address accessibility can exclude potential users, harm your reputation, and even lead to fines or lawsuits. But accessibility isn’t just about avoiding risks—it’s about fulfilling legal compliance for websites and showing you care about inclusivity while meeting the needs of all your customers.

It also gives your business a competitive edge. Many Canadians prefer to support brands that align with their values, including social responsibility. In fact, 25% of Canadian consumers choose brands that demonstrate inclusivity. Making your website accessible shows you’re committed to these values and helps build trust with your audience.

Accessibility Laws in Canada: What You Need to Know

Canada’s federal and provincial laws require businesses to make their websites accessible. All these laws align with the Web Content Accessibility Guidelines (WCAG), creating a consistent standard nationwide. Below is a quick overview:
- Accessible Canada Act (ACA): Aims for a barrier-free Canada by 2040. Federal organizations must remove barriers, including those on websites.
- Accessibility for Ontarians with Disabilities Act (AODA): Requires Ontario businesses to meet WCAG 2.0 Level AA by 2025. Non-compliance can result in fines of up to $100,000 per day.
- Accessibility for Manitobans Act: Focuses on removing barriers, including in technology, with WCAG compliance and staff training required.
- Nova Scotia Accessibility Act: Aims for a fully accessible province by 2030, with penalties up to $250,000 for violations.
- Accessible British Columbia Act: Requires websites to meet WCAG standards, with full implementation by 2024.
These laws emphasize legal compliance for websites to create inclusive digital spaces while highlighting the risks of non-compliance, such as significant fines and damage to your brand’s reputation.

What is WCAG?

The Web Content Accessibility Guidelines (WCAG), developed by the Wide Web Consortium (W3C), are the global standard for creating accessible websites. These guidelines provide a framework for ensuring that web content is usable by people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, and neurological disabilities.

WCAG is built on four core principles, ensuring that websites are:
- Perceivable: Content must be presented in ways that all users can perceive, whether through sight, hearing, or touch.
- Operable: Navigation and interaction must be functional using various input methods, such as keyboards, voice commands, or assistive devices.
- Understandable: Information and the operation of the user interface should be clear and intuitive.
- Robust: Websites must work with a variety of assistive technologies, including screen readers and text magnifiers
The guidelines are structured across levels of compliance: A (basic), AA (intermediate), and AAA (advanced). For instance, under laws like AODA, Ontario businesses must meet WCAG 2.0 Level AA standards.

Why Accessibility is a Smart Move for Canadian Retailers

Let’s talk business for a minute. Canadians with disabilities represent a market with over CAD 55 billion in annual purchasing power. Making your website accessible means you’re opening your doors to this massive audience.

Accessibility also tackles common issues like shopping cart abandonment. Did you know the average cart abandonment rate is 70%? For users with disabilities, it’s probably even higher—often due to frustrating website designs. By improving accessibility, you’re making it easier for everyone to shop with you, which can boost your sales.

On top of that, Canadians expect brands to align with their values. Studies show that 16% of consumers will stop supporting businesses that don’t prioritize social responsibility. Making your site inclusive sends a clear message: you care about your customers, and you’re committed to doing the right thing.

Why Accessibility Benefits Everyone

When you make your website accessible, you’re not just meeting legal compliance for websites—you’re gaining a ton of other advantages:
- Inclusivity: Your website becomes usable for everyone.
- Better SEO: Search engines love accessible websites, so you’re more likely to rank higher.
- Wider Audience: You’re opening up your site to millions of Canadians with disabilities.
- Stronger Brand Image: Being inclusive shows you care about your customers.
- Legal Protection: You’ll avoid fines and lawsuits, while building a more user-friendly site.
Steps to Make Your Website Accessible

Not sure where to start? Here’s a simple game plan to get your site on the right track:
1. Audit Your Site: Use tools like WAVE and Lighthouse to spot accessibility issues.
2. Learn WCAG Standards: Get familiar with WCAG 2.0 or 2.1 Level AA guidelines.
3. Fix the Basics: Add alt text to images, ensure keyboard navigation works, and include captions for videos.
4. Get Feedback: Work with users who have disabilities to test your site.
5. Educate Your Team: Train your staff on accessibility best practices.
6. Call in the Pros: Accessibility consultants can help with trickier issues.
7. Stay Updated: Keep up with changes in accessibility standards and laws.
The Risks of Ignoring Accessibility

Skipping accessibility isn’t just a bad look—it’s risky business. For example, AODA violations can cost corporations up to $100,000 a day. But the financial cost is just part of the problem.

An inaccessible website can damage your reputation and alienate a large chunk of your audience. People want to support brands that align with their values, and being seen as inaccessible could send them straight to your competitors.

Building a More Inclusive Future

Legal compliance for websites is more than a regulatory checkbox—it’s an opportunity to create a welcoming digital space for everyone. By prioritizing accessibility, you not only expand your audience but also demonstrate your commitment to inclusivity and social responsibility. Canadians value businesses that align with their beliefs, and web accessibility is a clear way to build trust and loyalty while fostering meaningful connections with your customers.

Achieving accessibility doesn’t have to be overwhelming. Simple steps like conducting audits, adhering to WCAG standards, and training your team can make your website more inclusive and user-friendly for all. Accessibility isn’t just about meeting legal requirements—it’s about creating a future where everyone can participate equally in the digital world.

Ready to take the next step? Partner with 216digital for expert guidance on legal compliance for websites. From comprehensive audits to ongoing support, we’ll help you achieve compliance and build a more inclusive online experience. Schedule your ADA briefing today!
Greg McNeil

January 20, 2025

Legal Compliance

Accessibility, accessibility laws, AODA, Canada, International Accessibility Laws, Legal compliance, Website Accessibility
Accessibility in JavaScript: A Developer’s Guide
JavaScript has revolutionized web development, enabling developers to create interactive and dynamic websites. However, these enhancements can also introduce significant accessibility barriers if not implemented thoughtfully. For web developers and eCommerce managers, ensuring that JavaScript-powered features are accessible isn’t just about compliance—it’s about creating an inclusive experience for all users.

This guide explores the essential techniques, testing methods, and best practices to ensure that JavaScript features meet accessibility standards and improve usability for everyone.

Why Accessibility in JavaScript Matters

Interactive JavaScript elements, such as modals, dropdown menus, and dynamic content updates, can be challenging for users with disabilities. Poorly implemented JavaScript can break keyboard navigation, confuse screen readers, or cause focus management issues, creating barriers that exclude a portion of your audience.

By prioritizing accessibility, developers can:
- Meet Web Content Accessibility Guidelines (WCAG).
- Improve user experience for everyone, including users with disabilities.
- Reduce the risk of legal action related to accessibility non-compliance.
- Expand your website’s audience and customer base.
Common Accessibility Barriers in JavaScript

Before diving into solutions, let’s examine some common accessibility pitfalls associated with JavaScript:
1. Keyboard Inaccessibility: Many JavaScript features rely on mouse interactions, neglecting users who navigate with a keyboard.
2. Focus Management Issues: Improper handling of focus can disorient users, especially when triggering modals, popups, or dynamic content.
3. Unlabeled ARIA Roles: Dynamic elements without proper ARIA roles and attributes can confuse screen readers.
4. Non-Compliant Custom Widgets: Custom components like sliders, tabs, or accordions often fail to replicate the functionality of their native HTML counterparts.
5. Content Updates Without Notifications: Dynamic content changes that are not announced to assistive technologies leave users unaware of critical updates.
Best Practices for Accessible JavaScript

To make your JavaScript-powered features inclusive, follow these best practices:

1. Ensure Keyboard Accessibility

All interactive elements must be operable using only a keyboard. Consider the following:
- Use semantic HTML elements like <button>, <a>, and <input>, which have built-in keyboard support.
- Add tabindex= "0" to custom elements to make them focusable.
- Avoid tabindex values greater than 0, which can disrupt the natural tabbing order.
- Implement custom keyboard interactions for widgets like dropdowns and modals. For example, allow users to close a modal with the Escape key.
2. Manage Focus Properly

Focus management is critical when working with dynamic content. Here’s how to handle it:
- Set Initial Focus: When opening a modal, move focus to the first interactive element within it.
- Trap Focus: Prevent users from tabbing out of an open modal.
- Restore Focus: Return focus to the triggering element when the modal is closed.
- Avoid Focus Loss: Ensure that dynamically added content doesn’t cause focus to disappear.
3. Use ARIA Responsibly

Accessible Rich Internet Applications (ARIA) can enhance screen reader compatibility, but misuse can lead to confusion. Follow these guidelines:
- Use ARIA Roles: Assign roles like role= "dialog" for modals or role= "menu" for dropdowns.
- Add ARIA States: Use attributes like aria-expanded, aria-hidden, and aria-live to convey element states to assistive technologies.
- Don’t Overuse ARIA: Avoid using ARIA when semantic HTML can achieve the same result.
4. Announce Dynamic Content Updates

For screen reader users, dynamically updated content must be announced clearly:
- Use aria-live regions to alert users to changes in content.
- Set the aria-live attribute to “polite” for non-urgent updates or “assertive” for critical changes.
- Avoid excessive announcements, which can overwhelm users.
5. Test Custom Widgets Thoroughly

If you create custom widgets, ensure they mimic the behavior of native elements:
- Use the WAI-ARIA Authoring Practices Guide as a reference.
- Make widgets focusable, operable via keyboard, and compatible with screen readers.
- Test with multiple assistive technologies and devices to ensure broad accessibility.
Testing JavaScript for Accessibility

Accessibility testing is an essential part of development. Use the following tools and methods to identify and address accessibility issues:

Automated Tools
1. Lighthouse (built into Chrome DevTools): Provides a quick audit of accessibility issues.
2. WAVE: Highlights accessibility problems directly on your webpage.
Manual Testing

Automated tools can’t catch every issue, so manual testing is critical:
- Keyboard Navigation: Ensure all interactive elements are focusable and operable with the Tab and Enter keys.
- Screen Readers: Test your website with screen readers like NVDA, JAWS, or VoiceOver.
- Focus Indicators: Verify that focus indicators are visible and intuitive.
Real-World Scenarios

Test your website with users who rely on assistive technologies. User feedback can uncover issues that developers might overlook.

Meeting WCAG Requirements

To comply with WCAG, focus on these key guidelines:

Perceivable
- Ensure text alternatives for images and icons.
- Provide captions for video content.
Operable
- Make all functionality available via a keyboard.
- Avoid content that flashes more than three times per second.
Understandable
- Use clear labels and instructions.
- Ensure consistent navigation and predictable interactions.
Robust
- Use valid HTML and ARIA attributes to ensure compatibility with assistive technologies.
Benefits of Accessible JavaScript

Implementing accessible JavaScript goes beyond compliance. It delivers tangible benefits, such as:
- Improved User Experience: Accessible features make your website easier to use for everyone.
- Increased Market Reach: Approximately 16% of the world’s population lives with some form of disability. Accessibility ensures they can engage with your website.
- Better SEO: Many accessibility improvements, like proper headings and alt text, also enhance search engine rankings.
- Legal Compliance: Meeting accessibility standards helps protect your business from lawsuits and reputational damage.
Conclusion

It is far easier to create accessible JavaScript from the onset rather than trying to fix it as an afterthought if you are armed with the proper knowledge.

Stay informed about evolving standards like WCAG and remain proactive in integrating accessibility into your development workflow. If you’re unsure if your JavaScript is accessible or are looking for an implementation partner who is focused on accessibility, reach out to 216digital using the contact form below.
Greg McNeil

January 17, 2025

How-to Guides

Accessibility, How-to, JavaScript, Web Accessibility, web developers, Website Accessibility
Web Accessibility: A Must for Small Businesses
Ever wonder if your website might be quietly turning people away?

As a small business owner, you already have plenty to juggle—so it’s easy to think web accessibility isn’t a top priority. But what if ignoring it costs you sales, hurts your reputation, and even puts you at risk for legal trouble?

The good news is that it’s never too late to start. By making your site accessible to everyone, you can reach more customers, show you care about every visitor, and stand out in a crowded market. Let’s explore why web accessibility matters and how simple steps can make a big difference for your business.

What Is Web Accessibility?

Web accessibility means designing websites so everyone can use them, including people with disabilities. It involves making sure your site works for those relying on screen readers, keyboard navigation, or other assistive tools. This includes people who have visual or hearing impairments, limited mobility, or cognitive differences.

But accessibility benefits more than just people with disabilities. It also helps those with temporary injuries, older devices, or slow internet, and those who can’t hear audio in noisy places. By following standards like the Web Content Accessibility Guidelines (WCAG), your small business can create a smoother, more inclusive online experience for every visitor.

Why Accessibility Matters for Small Businesses

Reach More Customers

The Centers for Disease Control and Prevention (CDC) says that more than 1 in 4 adults in the United States have some type of disability. That’s a huge group of potential customers who may struggle with a site that isn’t accessible. But accessibility also helps others—like older adults, people with temporary injuries, or those using slow internet.

By making your site easier to use, you can connect with a bigger, more diverse audience. In fact, studies show that businesses that focus on accessibility can see up to a 20% increase in their customer base.

Improve Your SEO

Did you know that accessible websites can rank higher in search results? Search engines favor sites that are easy to read and navigate. Features like clear headings, alt text for images, and proper HTML tags not only help users but also boost your SEO.

For example, the radio program This American Life added transcripts for each episode, increasing search traffic by almost 7%. By making your site more accessible, you, too, can improve your visibility and attract more organic traffic.

Build a Better Brand

People today care about inclusivity. A 2023 study showed that 70% of consumers prefer brands committed to diversity and inclusion. By making your website accessible, you show that you value every customer. This builds trust and loyalty, setting you apart from other businesses.

Avoid Legal Risks

The Americans with Disabilities Act (ADA) requires businesses to make their services, including websites, accessible. If you don’t, you might face expensive lawsuits. In 2024, over 4,000 ADA lawsuits were filed, and more than 33% targeted small businesses.

Why the focus on small businesses now? First, there are more small businesses overall. Second, large companies have been dealing with accessibility lawsuits for years, so many have strong accessibility programs already in place. Settlements can cost anywhere from $10,000 to $100,000—plus legal fees. By making your site accessible now, you can avoid these risks and show customers you care.

Don’t Let Cost Hold You Back

Improving accessibility takes time and money, but it doesn’t have to break the bank. Start with the biggest issues, like adding alt text or fixing color contrast. These small changes can make a huge difference. Plus, if you’re in the U.S., you may qualify for the Disabled Access Credit to help with costs.

Including accessibility from the start also saves money later. You won’t need expensive redesigns or add-ons if you prioritize accessibility now. Accessible sites often run more smoothly, which can reduce hosting and maintenance costs in the long run.

Practical Steps to Start Your Accessibility Journey

Feeling overwhelmed? Don’t worry—you can begin with small, simple steps:

Check Your Site’s Accessibility

Regularly audit your website for accessibility issues. There are free tools like WAVE and Google Lighthouse that can help you identify problems, such as missing alt text for images. For a deeper look, think about hiring an accessibility expert.

Stay Informed and Up-to-Date

Web Content Accessibility Guidelines (WCAG) and best practices can evolve over time. Stay informed about any changes and make updates to your website as necessary to remain compliant.

Train Your Team

Train your staff, especially those involved in website management and content creation, about web accessibility. This helps create a culture of inclusivity and ensures that accessibility remains a priority.

Offer Accessible Customer Support

Provide different ways for people to contact you—phone, email, or live chat. Make sure these options are usable by everyone, including people with assistive devices.

How Accessibility Helps Your Business

When you make your website accessible, you can:
- Increase Sales: If your site is easier to use, more people will stay and buy.
- Boost Customer Loyalty: People remember brands that make them feel included.
- Strengthen Your Brand: Being known for inclusivity helps you stand out.
Take the First Step

Starting your journey toward accessibility doesn’t have to be scary. Take small actions, keep improving, and celebrate your wins. The benefits—like reaching more customers, getting better SEO results, and strengthening your brand—are worth the effort.

At 216digital, we will help develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms so that you can focus on what matters: your business. Don’t wait—make your website accessible now. Schedule an ADA briefing with us to get started!
Kayla Laganiere

January 15, 2025

The Benefits of Web Accessibility

Accessibility, ADA Compliance, Benefits of Web Accessibility, Small Business, Website Accessibility
The EAA Lands in June
The European Accessibility Act (EAA) is set to shake things up for businesses operating in the European market. Starting in June 2025, the EAA will require companies to meet strict accessibility standards for websites, mobile apps, and digital products. If you’re working in or serving customers in the European Union (EU), this isn’t just about meeting requirements—it’s a chance to grow your reach and create better digital experiences for everyone.

Let’s dive into what the EAA is all about, why it matters, and how you can get ready for this significant change.

What is the European Accessibility Act?

The EAA is a groundbreaking law aimed at ensuring equal access to products and services across the European Union. Enforced by individual EU member states, it applies to a wide range of digital and physical products, including websites, mobile apps, software, and e-commerce platforms. The primary goal of the EAA is to eliminate barriers for people with disabilities and promote inclusivity and equal participation in society.

The EAA establishes clear accessibility requirements for businesses operating within the EU and harmonizes standards across member states. This ensures consistent accessibility efforts while simplifying compliance for companies working across the EU. For online businesses, compliance is guided by EN 301 549, the technical standard that serves as the foundation for meeting EAA requirements.

Scope of the EAA

The EAA’s web accessibility covers a broad range of applications such as:
- Websites and mobile apps
- E-books and online publications
- ATMs, ticketing, and check-in machines
- E-commerce platforms
EN 301 549: The Technical Backbone of the EAA

At the heart of the EAA’s web compliance is EN 301 549, a technical standard based on W3C’s Web Accessibility Guidelines (WCAG). These standards provide a clear framework for ensuring accessibility in websites, software, mobile apps, and other ICT products. By following WCAG 2.1 AA guidelines, companies can make their digital content usable by individuals with visual, auditory, cognitive, or motor impairments.

Suppose your e-commerce site, cloud software, SaaS platforms, or mobile apps already meet WCAG 2.1 AA requirements. In that case, they likely comply with EN 301 549—and, by extension, the EAA.

Are There Any Exceptions to EAA Compliance?

Although the EAA imposes strict accessibility standards, it recognizes that achieving complete compliance may sometimes be impractical. Under the “Disproportionate Burden Clause,” organizations can request exceptions if they show that meeting the requirements would impose an undue hardship. However, this doesn’t serve as a blanket exemption—companies must provide thorough documentation and clear justification for why they cannot reasonably comply. Even when an exception is granted, they are still expected to take every feasible step to maximize accessibility.

Why the EAA Matters

The EAA’s focus on accessibility marks a significant step forward in creating an inclusive digital environment across the EU. For businesses, compliance isn’t just a legal requirement; it’s an opportunity to reach a broader audience and demonstrate a commitment to inclusivity. As the EAA reshapes the accessibility landscape, it’s time to evaluate your products and services to ensure they’re ready to meet the new standard.

Here’s why it matters:

It’s Legally Required

The EAA is not just a guideline; it’s enforceable legislation that comes into effect in June 2025. Businesses that fail to comply could face fines, legal consequences, and even damage to their reputation. Taking action early gives you ample time to address challenges and ensure your digital products meet the required standards without unnecessary stress.

Reach a Larger Audience

Over one billion people worldwide live with disabilities, representing a significant—yet often underserved—consumer base. Of these, more than 135 million are in the EU, constituting a substantial market segment businesses cannot ignore. Making digital services accessible fulfills a critical need and demonstrates your brand’s commitment to inclusivity and respect for diverse audiences.

For U.S. businesses operating in the EU, compliance with EN 301 549 ensures alignment with the EAA’s requirements, preventing legal and reputational risks.

Better User Experience for Everyone

Accessibility improvements don’t just benefit people with disabilities; they enhance usability for all users. Features like simplified navigation, larger text options, and better color contrast make digital platforms easier for everyone. These changes lead to more satisfied customers and improved engagement.

Boost SEO and Discoverability

Accessibility isn’t just about compliance; it’s also a strategic way to improve your online presence. By following EN 301 549 and WCAG 2.1 AA standards, your website becomes more search engine-friendly, with features like descriptive alt text, clean navigation, and clear content structure. These enhancements make it easier for search engines to index your site, improving rankings and visibility. Embracing accessibility ensures your digital content is discoverable by a broader audience while meeting the compliance standards of the EAA.

How to Prepare for the EAA

Preparing for the EAA might seem overwhelming at first, but tackling it step by step makes the process manageable. Here’s how to get started:
- Audit Your Digital Accessibility: Evaluate your digital products and services against EN 301 549 and WCAG 2.1 AA guidelines. Use tools or hire experts to identify any accessibility gaps.
- Fix What Needs Fixing: Once you’ve pinpointed the issues, prioritize fixes like:
  - Adding alt text to images
  - Ensuring keyboard navigation works seamlessly
  - Improving color contrast
  - Testing for mobile responsiveness
- Train Your Team: Accessibility isn’t a one-time project—it’s an ongoing effort. Train your team on accessibility basics, like creating user-friendly designs, writing clear content, and following coding best practices.
- Use Accessible Tools: Make sure your design and development tools have built-in accessibility features. These tools can catch common issues early and save you time.
- Work with Accessibility Pros: If accessibility isn’t your area of expertise, partner with professionals specializing in it. They can guide you through audits, fixes, and long-term compliance strategies.
- Keep an Eye on Accessibility: Accessibility needs regular maintenance. Review your digital products often, especially when you update or add new features, to make sure everything stays compliant.
Overlays: The Quick Fix That Falls Short

Many businesses are attracted to accessibility overlays—automated tools that promise instant compliance. However, as the European Commission noted in 2023, “Claims that a website can be made fully compliant without manual intervention are unrealistic.”

While overlays may tackle surface-level issues, such as adding alt text or color contrast adjustments, they often fail to address deeper, more complex accessibility challenges like proper keyboard navigation, dynamic content handling, or compatibility with assistive technologies. These limitations mean overlays can leave users with disabilities frustrated and websites at risk of non-compliance. Real accessibility demands both automated solutions and hands-on human expertise.

The Upside of Accessibility

Meeting the EAA’s requirements isn’t just about avoiding fines. It’s an opportunity to:
- Boost Your Brand: An accessible business is seen as inclusive and forward-thinking.
- Build Customer Loyalty: People appreciate companies that make an effort to include everyone.
- Be Ready for the Future: As accessibility expectations grow, being ahead of the curve will pay off.
- Expand Your Market: Serving more people means more potential customers and growth.
Don’t Wait: Turn Accessibility into an Advantage

The European Accessibility Act is a big deal, but it’s also a chance to improve your business in meaningful ways. The June 2025 deadline might seem far off, but it’ll be here before you know it. Waiting until the last minute could lead to rushed fixes, higher costs, and unnecessary stress. Starting now ensures you have time to make thoughtful, lasting improvements.

By aligning with EN 301 549 and integrating accessibility into your workflows, you’ll not only meet the EAA’s standards but also create better experiences for your customers. Embracing accessibility can boost your brand, build customer loyalty, and expand your market while positioning your business as inclusive and forward-thinking.

Take the first step today by scheduling an ADA briefing with 216digital. Our experts can guide you through compliance, helping you stay ahead of the curve and turn accessibility into a strategic advantage.
Greg McNeil

January 10, 2025

Legal Compliance

Accessibility, EAA, European Accessibility Act, International Accessibility Laws, Web Accessibility, Website Accessibility
Accessibility Extensions: How Reliable Are They?
Making a website that everyone can use is an important goal for content creators, website owners, and developers. People who have disabilities, such as vision or hearing impairments, should have the same access to information and services as anyone else. Web accessibility removes barriers so all users can enjoy and navigate online content. One tool that can help is accessibility extensions—browser add-ons or standalone software that scans a website for common accessibility problems. But can you rely on these extensions alone to achieve a fully inclusive site?

In this article, we’ll discuss how these tools work, where they shine, and where you need to look beyond them to create truly accessible websites.

What Are Web Accessibility Extensions?

Web accessibility extensions are programs that you add to your internet browser or use as separate tools to check how well a website follows specific accessibility standards. These rules often come from guidelines like the Web Content Accessibility Guidelines (WCAG) set by the World Wide Web Consortium (W3C).

The extensions scan a webpage’s code and point out things that might make it hard for users with disabilities to use. For example, if a picture is missing a text description (called “alt text”), an accessibility extension might highlight that. Or, if your text color and background color are too similar, the extension might let you know that the contrast is poor.

Popular Accessibility Extensions

There are many accessibility extensions to choose from, and each has its own strengths:
1. Google Lighthouse: This free, open-source tool is built right into Google Chrome’s Developer Tools. It checks your website for performance, accessibility, and search engine optimization (SEO) issues. Lighthouse’s accessibility report can show you issues like missing labels on form fields and low color contrast.
2. BrowserStack: While not strictly an extension, BrowserStack is a popular platform that lets you test your website on many devices and browsers. It also includes accessibility checks so you can spot problems before your site goes live.
3. Color Enhancer: This Chrome extension is helpful for testing different color settings. It simulates how someone with color vision challenges might see your site, helping you adjust your color palette.
4. Total Validator: This tool checks for multiple issues at once. It looks for accessibility problems, HTML errors, and even spelling mistakes. It’s useful if you want an all-in-one solution.
Why These Tools Are Helpful

Accessibility extensions can save time and money, especially in the early stages of website development. They’re usually easy to install and use, often with just a few clicks. Many come at no cost, making them friendly for anyone’s budget. They also highlight the low-hanging fruit—simple issues you can fix quickly, like missing alt text, mislabeled buttons, or poor contrast.

When used regularly, these extensions can become part of your workflow. For instance, you can run Google Lighthouse each time you make a new page, making sure you don’t introduce new errors. Color Enhancer can be switched on while you design graphics, so you can instantly check your chosen colors. By catching issues early, you reduce the risk of more significant accessibility barriers piling up later.

The Limits of Accessibility Extensions

While these tools can be beneficial, they can’t do everything. Accessibility is about real-life user experience. Extensions might catch many problems, but there are several reasons they might not be enough:
1. They Don’t Catch All Errors: Some issues are complicated and need a human eye. For example, a tool might not realize that your navigation menu is confusing or that your form error messages aren’t explained well.
2. Automation Can Miss Nuances: An extension may mark something as fine even if it’s not easy to use in practice. Think of a button that looks accessible but is tricky to reach using keyboard navigation. Human testing would catch that, but an automated tool might not.
3. Limited Customization: Some extensions can’t adapt to specialized needs. If your website has complex interactive elements or unique design features, an extension might not provide accurate feedback.
Practical Steps for Using Accessibility Extensions

To get the most out of your accessibility extensions, you can follow a simple process:
1. Install One or More Extensions: Pick a couple that make sense for your workflow. For a developer, Google Lighthouse is a solid choice; Color Enhancer might be more fitting for a designer.
2. Run Automatic Scans Often: When you add new content or launch a new feature, rerun the extension. This helps you fix issues before they become widespread.
3. Review the Reports: Look at what the tool says and note any errors. For example, if Lighthouse tells you there’s missing alt text, add it immediately.
4. Cross-Check with Another Tool: Since no single extension catches all issues, try a second tool to see if it spots something different. Combining tools gives you a more complete picture.
5. Document Your Changes: Keep track of what you fix. If your team grows or you step away from a project, the next person will know what was corrected and why.
Going Beyond Extensions: Manual Testing & Real Users

Even the best technology can’t replace the insight of real people. To go beyond automated checks, try these methods:
1. Manual Testing: Walk through your website with a keyboard only (no mouse). Can you reach all interactive elements, like menus, links, and form fields? Check if focus indicators (the outlines around clickable items) are visible so users know where they are on the page.
2. Test with Assistive Technologies: Screen readers like NVDA (free for Windows) or VoiceOver (built into macOS and iOS) let people with visual impairments hear text read aloud. Try them out on your site. Can you follow the page structure logically? Are buttons and links announced clearly?
3. Get Feedback from Users: Invite people with disabilities to test your site. This can be done in person or through online platforms. Their first-hand experiences will show you things no tool can catch.
4. Follow WCAG Guidelines: The W3C’s Web Content Accessibility Guidelines provide detailed advice about making websites more inclusive. Follow these guidelines to ensure you’re meeting recognized standards.
5. Keep Checking Over Time: Accessibility isn’t a “one-and-done” situation. Technology changes, and so does your site’s content. Regular audits help you stay current with new requirements or tools.
Professional Tools and Services

For more significant sites or those in specific industries, it can help to invest in professional tools or services. Some companies offer advanced scanning that runs on a schedule and sends alerts when accessibility issues are found. Others offer expert audits, which include hands-on testing by accessibility specialists. Examples include:
- a11y.Radar: Provides automated scans, real-time issue tracking, and actionable developer guidance. It integrates with CI/CD workflows and offers analytics to monitor progress and prioritize critical fixes.
- Siteimprove: This includes monitoring and scoring your site based on accessibility, SEO, and more.
- Specialized Accessibility Consultancies: Hiring an experienced team can help with complex sites or strict legal requirements.
Additional Resources to Explore

If you’d like to learn more or go deeper into this topic, here are a few helpful links:
- W3C Web Accessibility Initiative: Offers guidelines, techniques, and tutorials on how to create an accessible website.
- WebAIM: Contains articles, tools (like the WAVE Extension), and a community forum focused on accessibility.
- A11y Project: A community-driven site with guides, checklists, and news about web accessibility.
- Section508.gov: Focuses on accessibility laws and standards in the United States.
Conclusion

Accessibility extensions are a great starting point. They quickly show you common issues and give you ideas on what to fix. Yet, relying on them alone doesn’t ensure everyone can use your site. By also doing manual checks and involving people with different abilities, you can create a richer, more usable online experience. Combining automated scanning, real-world testing, and guidelines like WCAG gives you the best chance of meeting everyone’s needs.

Remember, building an inclusive website is an ongoing journey. Updates to your site, new browser versions, and changing assistive technologies mean there’s always something more to learn. Encourage your team to see accessibility as a shared responsibility. Keep your tools up to date, document your progress, and work together to reduce barriers for all. In the end, these efforts not only help people with disabilities, but they also make your site more user-friendly for everyone.

If you’re ready to take the next step in making your website accessible, 216digital can help. From expert audits to ongoing monitoring with our a11y.Radar tool, we’re here to guide you every step of the way. Contact 216digital today and ensure your website meets the highest standards for accessibility, usability, and inclusivity. Together, we can build a web that works for everyone.
Greg McNeil

January 8, 2025

Testing & Remediation

Accessibility, accessibility extensions, evaluation tools, Website Accessibility, Website Accessibility Tools
2024 Accessibility Lawsuits: Trends and Lessons

2024 has been another big year for web accessibility—and not in a good way. More than 4,000 accessibility lawsuits were filed against digital properties this year, affecting businesses of all sizes. Whether you’re a small business facing your first lawsuit or a larger company dealing with repeat claims, the message is clear: ignoring web accessibility is no longer an option.

Despite the alarming rise in legal risks, the good news is that you can take practical steps to protect your business and create a better online experience for everyone. Below, we’ll examine the highlights of 2024, why they matter, and how you can get ahead in 2025.

Accessibility Lawsuits Are Shifting to State Courts

In 2024, over 4,000 accessibility lawsuits were filed—1,600 in state courts and 2,400 in federal courts. While federal cases dipped slightly, lawsuits in state courts surged, led primarily by New York and California. These two states accounted for more than 40% of all claims.

Why are state courts becoming more popular? State-specific legal frameworks and streamlined procedures may be giving plaintiffs an edge. For businesses, this shift means that federal-level compliance isn’t always enough—you must also stay aware of state-level requirements. Regular audits, attention to WCAG (Web Content Accessibility Guidelines) updates, and a clear understanding of how your state enforces accessibility standards can help you stay ahead. Ignorance, as it turns out, is no longer bliss.

New York Is at the Center of the Action

New York isn’t just the city that never sleeps—it’s also the state that leads the nation in accessibility lawsuits. In 2024 alone, 2,541 cases were filed in its federal and state courts, surpassing even California.

What’s especially notable is New York courts’ willingness to hear cases against businesses with no physical presence in the state. If your website is accessible to New Yorkers, it’s open to potential litigation. Combine that with active plaintiffs and law firms focusing on accessibility, and you have a recipe for heightened risk.

Copycat Lawsuits Are a Growing Threat

One of the more frustrating trends of 2024 is the rise of “copycat” lawsuits. Out of this year’s filings, 961 cases—41% of all accessibility lawsuits—targeted companies that had already faced noncompliance claims in the past.

These repeat claims often happen when companies fix only part of their accessibility issues, leaving gaps that draw new lawsuits. New plaintiffs may target the same website, related brands, or even parent companies. The takeaway? Partial fixes can turn a one-time lawsuit into a recurring problem.

Small Businesses Are in the Spotlight

Historically, large corporations shouldered most accessibility lawsuits, but 2024 marked a shift. Small businesses—those earning under $25 million a year—were targeted more than ever.

There are two key reasons for this change. First, there are simply more small businesses out there, creating a bigger pool of potential defendants. Second, many large companies have been managing lawsuits for years and have implemented robust accessibility programs. With 82% of big companies already working toward compliance since 2018, plaintiffs are now focusing on smaller businesses that may have fewer resources or less awareness.

For small business owners, this trend can feel overwhelming. The silver lining is that you’re not alone, and even modest efforts can go a long way. You don’t need a massive budget to make your website more accessible—you just need to know where to begin.

Accessibility Widgets: Not the Quick Fix You Think They Are

If you’ve ever considered adding a simple “accessibility widget” to solve all your problems, you’re not alone—but this strategy might create more headaches than it relieves. In 2024, over 1,000 companies with widgets on their sites were still sued for accessibility noncompliance.

Why? Widgets often fail to address the deeper, structural issues that make a site inaccessible. In some cases, they even introduce new barriers, like interfering with assistive technologies or complicating site navigation for users with disabilities. Plaintiffs are increasingly calling out widgets as insufficient and pointing to WCAG violations or “band-aid” approaches that neglect larger accessibility gaps.

Relying on widgets alone could lead to a rude awakening. True accessibility requires meaningful changes to your site’s structure and content. This investment will reduce your legal risk and provide a better experience for all users.

What You Can Do in 2025

The prospect of a accessibility lawsuit is stressful, but there’s plenty you can do to minimize your risk. Consider these steps as you plan for the coming year.

Immediate Actions

Conduct a WCAG 2.2 Audit

Start by evaluating your site against the WCAG 2.1. Common issues include missing alt text, poor color contrast, and unlabeled form fields. Fixing these core issues can make an immediate impact.

Train Your Team

Accessibility isn’t a one-time project. Train your developers, designers, and content creators so that accessibility best practices are woven into everything they do. The more knowledge your team has, the fewer issues will arise.

Long-Term Strategies

Build Accessibility Into Your Workflow

Don’t wait until the end of a project to think about accessibility. Integrate it into each stage of development, from initial design to final testing. Known as “shifting left,” this proactive approach saves both time and money.

Partner With Experts

Accessibility is complex, and you don’t have to navigate it alone. Working with a team like ours at 216digital can help you stay up-to-date on guidelines and maintain ongoing compliance.

Conclusion

Yes, the surge in accessibility lawsuits is concerning. Yes, courts in states like New York and California are becoming more aggressive in penalizing non-compliant businesses. And yes, copycat claims mean one lawsuit can quickly snowball into multiple suits. However, this issue isn’t just about minimizing legal risk—it’s about building an inclusive internet that everyone can use and enjoy.

At 216digital, we strive to be more than just a service provider. Our aim is to be an ally, guiding you through the complexities of digital accessibility. Creating an inclusive website benefits your customers, your brand, and your legal standing. It might sound daunting at first, but that’s where we come in. Our step-by-step approach can help protect your business and empower a broader online audience.

The sooner you begin, the easier it becomes to get your site on track. So, let’s move forward—schedule a call with us, take that initial step, and start building a web experience that truly works for everyone. You’ve got this, and we’re here to help.

Greg McNeil

January 6, 2025

Legal Compliance

2024 accessibility lawsuits, ADA Compliance, ADA Lawsuits, web accessibility lawsuits, Website Accessibility
Making Hidden Content Accessible to Assistive Technologies
As a web developer, you want your website to be usable by everyone, including people who rely on assistive technologies. These technologies—such as screen readers, braille displays, and speech recognition software—can help individuals with disabilities navigate the web more easily. Sometimes, you may need to hide certain parts of your webpage visually without hiding them from these tools. However, doing this incorrectly can cause big accessibility issues.

In this article, we’ll explore how to effectively hide and manage hidden content for people using assistive technologies. We’ll discuss why display: none is problematic, how to use the clip pattern, and how attributes like aria-hidden and hidden can help. By the end, you’ll have a better understanding of how to ensure your website remains inclusive and user-friendly.

The Problem with display: none

When you use display: none in your CSS, you remove an element from the visual flow of the page. This means sighted users will not see it. But, it also means the element is completely invisible to assistive technologies such as screen readers. If you’ve hidden important text or controls this way, users who rely on assistive technologies might miss out on content or functionality that they need.

For example, imagine you have a button that visually looks like an icon, but you hide the text label using display: none. Now, people who can see the icon know what the button does, but people using assistive technologies hear nothing. This creates a poor user experience and makes your site less accessible.

The Clip Pattern: A Better Approach

To visually hide content while keeping it available to assistive technologies, the clip pattern is a popular solution. The idea is to position the element off-screen so sighted users don’t see it, but screen readers can still find it. Here’s an example:
```
.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  border: 0;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
}
```
By applying the .visually-hidden class to your element, you ensure it’s hidden visually but remains accessible to assistive technologies. This makes the content discoverable by screen readers, letting users who can’t see the screen still benefit from it.

Why the Clip Pattern Works

This pattern relies on moving the element so it’s not visible in the viewport and restricting its size to 1px by 1px. With clip: rect(0, 0, 0, 0); (or clip-path in modern CSS), the browser cuts off any visual display. Yet, the element remains in the Document Object Model (DOM), meaning assistive technologies can still access it. That’s the key difference between this and display: none.

Managing Visibility with aria-hidden and the hidden Attribute

Beyond CSS, there are HTML and ARIA (Accessible Rich Internet Applications) attributes that also control how content is shown to both users and assistive technologies. Two important attributes here are aria-hidden and the HTML5 hidden attribute.

aria-hidden="true"

When you add aria-hidden="true" to an element, you’re telling assistive technologies not to read or announce that element to users. This is handy for decorative images or redundant content. For instance, if you have a background image that doesn’t provide important information, you could mark it with aria-hidden="true" so screen readers ignore it.

But be cautious: if you need an element to be read by assistive technologies, do not use aria-hidden=”true”. This attribute will block that element from being announced entirely.
```
<div aria-hidden="true">
  <img src="decorative-image.jpg" alt=""/>
</div>
```
HTML5 hidden Attribute

The hidden attribute is another way to remove content from everyone—both sighted users and assistive technologies. When you use it, browsers typically hide the element. Screen readers will also skip it. This is good if the element is meant to be inaccessible to all users, like a form section that’s not yet relevant or a menu item that’s not available.
```
<div hidden>
  <p>This content is hidden from all users.</p>
</div>
```
Use hidden or aria-hidden when you truly want to exclude an element from assistive technologies. If you want it hidden visually but still available to screen readers, you should stick with the clip pattern or .visually-hidden approach.

Best Practices for Accessible, Visually-Hidden Content

1. Use Semantic HTML

Using proper semantic HTML elements (like <nav> for navigation, <main> for main content, or <section> for thematic grouping) is important for clear structure. It helps assistive technologies interpret your content correctly. Semantic HTML also reduces the need for extra attributes and complex styling, since the markup itself conveys meaning.

2. Avoid Hiding Focusable Elements

If an element can receive focus (like links, form inputs, or buttons), think carefully before hiding it. A hidden yet focusable element can be confusing for keyboard-only users, since it might get focus without being visible. If you must hide a focusable element, consider removing it from the tab order by using tabindex="-1" or ensuring it’s properly revealed at the right time.

For example, if you have a pop-up form that appears only after a button click, you can initially hide it with the clip pattern. Once the user clicks, you can remove the clip pattern or switch the CSS to show the content. This way, the form becomes available to both sighted users and people using assistive technologies at the same time.

3. Provide Context for Hidden Content

Sometimes you want to reveal hidden content dynamically (like a drop-down menu). In these cases, use ARIA attributes such as aria-expanded and aria-controls to inform assistive technologies that a certain part of the page is now visible or hidden. This can help screen reader users understand changes on the page.
```
<button aria-expanded="false" aria-controls="menu" id="menuButton">
  Toggle Menu
</button>

<nav id="menu" class="visually-hidden">
  
</nav>
```
When you click the button, you can toggle its aria-expanded value from false to true, and remove the .visually-hidden class from the menu. This ensures that both visual and non-visual users know the content has been revealed.

4. Test with Multiple Assistive Technologies

It’s important to test your website with different assistive technologies because each one may behave slightly differently. Popular screen readers include NVDA, JAWS, and VoiceOver. Don’t forget to check on both desktop and mobile devices. Regular testing can help you catch accessibility issues before your users do.

Handling Localization

If you’re translating your site into multiple languages, remember that hidden text might also need translation. For example, your .visually-hidden text for instructions or links should be available to screen readers in every supported language. Make sure your language attributes (like lang="en") are correct, and consider cultural differences that could impact how you label hidden elements.

For instance, if you have an English site and a Spanish site, your hidden instructions should be translated into Spanish on the Spanish version. This ensures that users relying on assistive technologies can access the content in the correct language.

Putting It All Together: A Quick Example

Let’s look at a simple example of an accessible button that has visually hidden text:
```
<button class="icon-button">
  <span class="visually-hidden">Submit Form</span>
  <img src="icon-submit.png" alt="" aria-hidden="true" />
</button>
```
- The .visually-hidden class hides the text “Submit Form” from sighted users, but screen readers can still read it.
- The <img> tag includes an empty alt attribute and aria-hidden="true", so assistive technologies ignore the image itself.
- Sighted users see only the icon, while screen reader users hear “Submit Form.”
This example keeps your content accessible to people using assistive technologies and also meets visual design needs.

Additional Resources
- Web Content Accessibility Guidelines (WCAG): A detailed guide on making web content accessible.
- WAI-ARIA Authoring Practices: Official tips on using ARIA roles, states, and properties.
- MDN Web Docs on ARIA: In-depth explanations of ARIA attributes and best practices.
Exploring these resources will help you master hiding content effectively, ensuring people who use assistive technologies can still access everything they need.

Conclusion

Hiding content from sighted users while keeping it accessible to assistive technologies is an essential skill for modern web developers. By avoiding display: none for important information, using the clip pattern for visually hidden content, and carefully leveraging aria-hidden or hidden, you can ensure everyone has a good experience on your site.

Remember to keep the following points in mind:
1. Use the clip pattern (.visually-hidden) to hide content from sighted users but keep it readable by assistive technologies.
2. Use aria-hidden and hidden only when you truly want to hide content from all users, including those using assistive technologies.
3. Pay attention to focusable elements, making sure you don’t accidentally trap keyboard users in hidden sections.
4. Test frequently with various tools and real users to ensure your hidden content behaves as you expect.
5. Localize your hidden text so that people using assistive technologies in other languages can also benefit.
By following these guidelines, you’ll be well on your way to building inclusive websites that work for everyone. Your careful attention to accessibility shows that you value all your users, regardless of their abilities or the assistive technologies they use. Embracing these practices will help ensure a positive, welcoming, and user-friendly experience across the board.
Greg McNeil

December 31, 2024

How-to Guides

Accessibility, assistive technology, How-to, web developers, web development, Website Accessibility

The Importance of Ongoing Accessibility Monitoring

Early Issue Detection

Improved User Experience

Brand Reputation and Trust

Regulatory Compliance

Common Accessibility Barriers Identified

Missing Alternative (Alt) Text for Images

Why It Matters

Solution

Insufficient Color Contrast

Why It Matters

Solution

Keyboard Navigation Failures

Why It Matters

Solution

Missing Form Input Labels

Why It Matters

Solution

Missing or Improperly Structured Headings

Why It Matters

What Monitoring Reveals

Benefits of Accessibility Monitoring for Web Developers and Ecommerce Managers

Reduced Development Bottlenecks

Increased Conversion Rates

Stronger Data

Mitigated Legal Risks

Recommended Tools for Accessibility Monitoring

Automated Accessibility Scanners

Color Contrast Analyzers

Screen Reader Testing

CI/CD Integration

Best Practices to Maintain an Accessible Website

Make Accessibility Part of Your Design Process

Prioritize Semantics and Structure

Adhere Strictly to WCAG Standards

Incorporate Regular Training

Schedule Routine Audits

Create an Accessibility Statement

Conclusion

The Rise and Shift of ADA Lawsuits for Websites

Geographic Hotspots

Widgets and Overlays Don’t Cut It

Why Do Overlays Fail?

The Growing Challenge of Repeat Lawsuits

Why E-Commerce Websites Were the Hardest Hit

What You Can Do to Avoid ADA Lawsuits

Accessibility: A Legal Requirement and a Moral Choice

WebAIM’s Four-Level Severity Framework

Critical Issues

Significant Issues

Moderate Issues

Minor Issues

Step-by-Step Guide to Prioritizing Accessibility Fixes

1. Conduct a Comprehensive Accessibility Audit

2. Categorize Issues by Severity

3. Consider the Impact on Your Audience

4. Focus on High-Traffic and High-Value Pages

5. Use a Phased Approach for Moderate and Minor Issues

6. Test and Retest

Tools and Techniques for Effective Accessibility Testing

Why Prioritization Matters

Final Thoughts

Why Web Accessibility Matters

Accessibility Laws in Canada: What You Need to Know

What is WCAG?

Why Accessibility is a Smart Move for Canadian Retailers

Why Accessibility Benefits Everyone

Steps to Make Your Website Accessible

The Risks of Ignoring Accessibility

Building a More Inclusive Future

Why Accessibility in JavaScript Matters

Common Accessibility Barriers in JavaScript

Best Practices for Accessible JavaScript

1. Ensure Keyboard Accessibility

2. Manage Focus Properly

3. Use ARIA Responsibly

4. Announce Dynamic Content Updates

5. Test Custom Widgets Thoroughly

Testing JavaScript for Accessibility

Automated Tools

The Problem with `display: none`