Digital Marketing Tips and Strategies to Grow Your Business

WAVE Accessibility Tool: A Step-by-Step Guide
Have you ever clicked on a website and felt completely lost—like the menus were in hidden corners, or the text was so tiny you had to squint? Sometimes, the root of that problem is an accessibility issue. Put simply, a site might not be built in a way that everyone can use comfortably. That’s where WAVE comes in. WAVE (short for Web Accessibility Evaluation Tool) helps detect areas on your website with barriers and provides you with tips on how to fix them. It’s free, easy to use, and super handy for making sure your site works for everyone.

If you’ve never heard of WAVE or used it before, don’t worry—you’re not alone! In this guide, we’ll break it down step by step and show you how it can make your website better, clearer, and more user-friendly. Let’s dive in!

What Is the WAVE Accessibility Tool?

So, what exactly is WAVE? Created by WebAIM, this free tool looks for possible problems on any webpage and points them out. Think of it like a traffic light system for your site’s accessibility. If there’s a red light, it means an issue needs immediate attention—like missing text descriptions for images (which can be a big deal for screen reader users). If something’s in yellow, it could be a warning sign that may or may not become a problem.

But what makes WAVE so remarkable is its visual approach: it marks up your page with icons and colored boxes so you can spot issues right where they happen. It also highlights structural elements—like headings, landmarks, and ARIA attributes—to ensure your website is logically organized and easy to navigate. No more digging through code and guessing what went wrong. Just click, glance, and fix!

Key Features of WAVE Accessibility Tools

Browser Extensions

If you’re a fan of quick-and-easy solutions (who isn’t?), you’ll love WAVE browser extensions. You can add them to Chrome or Firefox with just a few clicks. Once that’s done, go to any webpage, hit the WAVE icon in your toolbar, and boom—you get an instant report without switching tabs. It’s perfect for those of us who like minimal fuss.

Online WAVE Tool

If extensions aren’t your thing or you’re using a borrowed computer, don’t worry. WAVE also has an online tool. All you have to do is visit the WAVE website, copy the link to the page you want to test and paste it. Within seconds, you get a full-page view loaded with accessibility markers. This approach keeps you flexible, especially if you switch devices a lot.

Visual Feedback

One of the best parts of WAVE is how it breaks down what might be going wrong. Errors, warnings, and even things that are working just fine each get their own unique symbols. You’ll see icons, colors, and outlines placed directly on top of the webpage elements. This visual overlay system helps you zero in on issues (like missing alt text or poor contrast ratios) more quickly than poring over raw code.

Accessibility Panels

After WAVE loads your page, you can explore different panels to learn more:
- Summary Panel: This shows you how many errors, alerts, and features were found.
- Structure Panel: Gives you a rundown of your headings, lists, and how the page is organized. This is super helpful for seeing whether screen readers will read your page in a logical order.
- Details Panel: Goes deeper by explaining each issue and how to fix it. If you’re the type of person who likes step-by-step instructions, you’ll feel right at home here.
How to Use WAVE Effectively

Getting Started

First things first: pick your favorite way to use WAVE. If you like convenience, grab the Chrome or Firefox extension. If you’d rather not install anything, head straight to the online WAVE site. From there, it’s as simple as entering your page’s URL. Once you see your page covered with icons, you’ll know you’re in business.

Running an Analysis

When you launch WAVE, it basically scans the webpage in front of you and marks all the potential issues. Think of it like a helpful friend pointing out the spinach in your teeth—except here, it’s pointing out an image without alt text or headings that aren’t in the right order. You might see red icons (these are errors), yellow icons (warnings), or other symbols that highlight good features, too. Scroll down to make sure you don’t miss any marks hiding at the bottom of the page.

Interpreting Results

Getting an A+ in accessibility can feel like unlocking a secret achievement! But sometimes, your first scan with WAVE might bring up a list of errors longer than you’d hoped. Don’t panic. Errors typically mean your site is missing something important, like proper labels for form fields or headings that make sense. Warnings, on the other hand, are more like gentle taps on the shoulder, suggesting a potential issue.

You’ll also see that WAVE links these issues to specific guidelines from the WCAG (Web Content Accessibility Guidelines). That might sound fancy, but it basically helps you follow official rules, so you’re not just guessing how to fix stuff.

Prioritizing Fixes

So, you’ve got a bunch of red and yellow icons—where do you even start? Focus on the red ones first (the errors). Fix things like missing alt text or form labels right away since those directly affect how people access and use your content. Next, tackle the warnings. You might spot patterns, like repeated heading problems across several pages. Fixing them in one swoop can save you a lot of time.

Exporting and Sharing Results

If you’re part of a team, you’ll probably want to show your coworkers what needs fixing. WAVE makes this easy—there’s an option to export the report or share a link to the scanned page. This can be a lifesaver when you need to prove to a manager that certain design choices might be causing trouble for users. Plus, it keeps everyone on the same page—literally!

Strengths and Limitations of WAVE

WAVE is user-friendly, offers quick visual feedback, and gives both beginners and experienced developers something to love. It’s like having a built-in teacher who highlights mistakes and nudges you toward the right answers.

What It Does Well
- Highlights errors and warnings right on the page.
- Teaches you about accessibility by explaining each issue.
- Checks for essential elements like color contrast, heading hierarchy, and ARIA attributes.
- It works within your browser or online, so no extra files are needed.
Where It Falls Short
- Single-Page Focus: WAVE is excellent for testing one page at a time but isn’t designed to crawl an entire site in one go.
- Scope of Automation: Automated checks can’t evaluate everything—like the clarity of your alt text or how user-friendly your navigation is. Manual testing is still essential, especially for things like complex JavaScript interactions.
- Not a Magic Fix: WAVE won’t fix issues for you—it only shows you what to work on. Consider it a trusty sidekick, not a fully automated superhero.
Best Practices for Using WAVE

Combine with Other Tools

While WAVE is incredible, consider also using tools like Google Lighthouse or Accessibility Radar (a11y.Radar). The more eyes on your site, the better.

Manual Testing Matters

Automated tools can catch a lot of problems, but human testing can uncover hidden barriers—like confusing navigation menus or unclear copy. Think of WAVE as your first line of defense, not the only line.

Train Your Team

If you’re not the only one updating the website, make sure others know how to read and understand WAVE reports. Accessibility is more manageable when everybody’s on board.

Start Early

Don’t wait until your site goes live to test for accessibility. Use WAVE during the design phase so you can catch significant issues before they become big headaches.

Make It Part of a Bigger Strategy

Use WAVE as the baseline for your accessibility plan. Re-run tests after making changes and encourage feedback from real users. Over time, you’ll build a more inclusive experience.

That’s a Wrap: Waving Goodbye to Barriers

Making your site accessible is really about welcoming everyone—whether they use screen readers, need larger text, or want a smoother experience. WAVE takes the guesswork out of finding those hidden roadblocks. It shows you exactly where to focus your efforts, helping you make fast progress toward a more inclusive website.

As powerful as WAVE is, remember that it’s only one piece of the puzzle. Combining WAVE’s insights with manual testing, user feedback, and other evaluation tools like Axe or Lighthouse will give you a well-rounded approach to accessibility. Over time, you’ll find that accessibility isn’t just about rules and standards—it’s about caring for the people visiting your site. Happy scanning, and may your website become a place where everyone feels right at home!
Greg McNeil

January 13, 2025

Testing & Remediation, Web Accessibility Monitoring

Accessibility, Accessibility testing, automated testing, WAVE, Web 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
Writing Code for Web Accessibility: A Guide for Developers
Coding often feels like speaking a secret language—it’s complex, intricate, and incredibly rewarding. Including web accessibility in your workflow isn’t about reinventing the wheel; it’s about refining your craft to ensure your work reaches everyone. Accessible code builds on the practices you already know, with small adjustments that make a significant impact. In this guide, we’ll explore actionable steps to help you create accessible, user-friendly websites that leave no user behind.

What Is Accessible Code?

Accessible code ensures everyone can interact with your website, regardless of ability. Following standards like the Web Content Accessibility Guidelines (WCAG) helps create an inclusive space for all users. By integrating accessibility, you’re not just meeting legal requirements but building a better, more welcoming web experience.

Accessibility encompasses several aspects, including:
- Visual Accessibility: Making visual content perceivable by users with visual impairments, often through tools like screen readers.
- Interactive Usability: Ensuring interactive elements work seamlessly with keyboards, touchscreens, or voice commands.
- Content Clarity: Structuring information logically to assist users with cognitive impairments.
- Compatibility: Writing robust code that works with assistive technologies and adapts to future updates.
The Four Golden Rules of Accessibility: POUR

The foundation of accessible code is rooted in WCAG’s four guiding principles: Perceivable, Operable, Understandable, and Robust (POUR). These principles ensure your website is usable for everyone. Let’s break them down:
- Perceivable: Users must be able to see or hear content.
  - Provide text alternatives for non-text content like images (e.g., alt text).
  - Use captions and transcripts for multimedia content.
- Operable: Interactive elements must be usable with any input device.
  - Ensure keyboard navigation works for all features.
  - Include features like skip-to-content links to improve navigation.
- Understandable: Content and interfaces should be easy to comprehend.
  - Label forms clearly and provide concise instructions.
  - Write meaningful error messages that guide users in resolving issues.
- Robust: Code should be compatible with a wide range of assistive technologies.
  - Use valid, semantic HTML to ensure content is interpretable.
  - Test compatibility with assistive technologies like screen readers.
Adhering to these principles ensures compliance with accessibility standards while enhancing usability for everyone.

Best Practices for Writing Accessible Code

Here’s how to apply accessibility principles to your code:

1. Use Semantic HTML

Semantic HTML provides structure and meaning to your content. Elements like <header>, <nav>, <main>, and <footer> improve navigation for screen readers and other assistive technologies.

Instead of:
```
<div onclick="doSomething()">Click me</div>
```
Use:
```
<button onclick="doSomething()">Click me</button>
```
Semantic tags enhance usability and reduce the need for ARIA roles, ensuring better compatibility.

2. Make Forms Accessible

Forms are a common source of frustration for users with disabilities. Pair input fields with <label> tags to provide clear context:
```
<label for="email">Email:</label>
<input type="email" id="email" name="email">
```
For added guidance, use aria-describedby for hints:
```
<p id= "emailHint"> We'll never share your email.</p>
<input type="email" id="email" aria-describedby="emailHint">
```
Additionally:
- Group related fields with <fieldset> and <legend>.
- Include real-time error validation with accessible alerts.
3. Ensure Keyboard Navigation

Interactive elements should be operable using a keyboard. Use logical HTML structures and the tabindex attribute sparingly to create a natural focus order.

Example:
```
<button tabindex="0">Focus me</button>
```
Avoid negative tabindex values unless necessary, as they can disrupt navigation.

4. Add Alt Text to Images

Alt text makes images accessible to screen readers. Describe the content succinctly:
```
<img src= "puppy.jpg" alt= "A golden retriever puppy playing with a ball">
```
If an image is decorative, use an empty alt attribute (alt= "") to skip it for screen readers.

5. Mind Your Colors

Color contrast impacts readability. Use tools like Contrast Checker to verify that text is legible. Avoid using color as the sole means of conveying information. For example:
```
<span style="color: red;">Required field</span>
```
Should also include:
```
<span class="required" aria-label="Required field">*</span>
```
6. Use ARIA Wisely

Accessible Rich Internet Applications (ARIA) roles can enhance functionality but should be used sparingly. Stick to semantic HTML whenever possible. Common ARIA roles include:
- role= "alert" for dynamic notifications.
- aria-expanded for collapsible menus.
- aria-live for real-time updates.
7. Don’t Forget Multimedia

Provide captions for videos and transcripts for audio content. Respect user preferences for reduced motion by using the prefers-reduced-motion media query:
```
@media (prefers-reduced-motion: reduce) {
  animation: none;
}
```
Testing Your Accessible Code

Even the best code needs testing. Use these methods:
- Automated Testing: Tools like Google Lighthouse or WAVE can identify common issues.
- Manual Testing: Navigate your site using only a keyboard or a screen reader (e.g., NVDA, VoiceOver).
- User Testing: Get feedback from users with disabilities to uncover real-world issues.
Testing should be an ongoing part of your development process to catch and fix issues early.

Challenges Developers Face—and How to Overcome Them

Challenge: Understanding WCAG Guidelines Can Be Intimidating

Solution: Start with the essentials. Focus on foundational elements like semantic HTML, alt text, and keyboard navigation. Once these are second nature, dive deeper into more complex guidelines—one step at a time.

Challenge: Debugging ARIA Roles Can Be Tricky

Solution: ARIA can feel like uncharted territory, but tools like ARIA Authoring Practices and automated testing tools (e.g., Google Lighthouse or WAVE) make it manageable. Stick to semantic HTML where possible to minimize the need for custom roles.

Challenge: Maintaining Accessibility During Updates

Solution: Accessibility isn’t a one-and-done task; it’s an ongoing commitment. Make accessibility checks part of your QA process and leverage tools like WAVE to identify issues after every update. Document accessibility practices in your team’s workflow to keep everyone aligned.

Challenge: Balancing Deadlines with Accessibility Goals

Solution: Tight deadlines can pressure teams to deprioritize accessibility. Combat this by integrating accessibility from the start of a project rather than treating it as an add-on. Small, consistent efforts save time in the long run and prevent last-minute fixes.

By acknowledging these challenges and embracing practical solutions, developers can turn obstacles into opportunities to create better, more inclusive websites.

Keep Learning and Building Accessible Code

Web accessibility is a continuous journey—and an exciting one. As developers, we thrive on solving problems and improving our craft, and accessibility is no different. By staying updated with trusted resources like WebAIM, MDN Web Docs, and the A11y Project, you can keep sharpening your skills and pushing the boundaries of what’s possible. Engage with communities, take courses, and embrace every opportunity to learn. Every small step you take makes the web a more inclusive place for everyone.

Writing accessible code is about thoughtful, inclusive choices that enhance user experiences. Start with the basics, make accessibility an integral part of your workflow, and let learning drive your improvements. The impact of your efforts extends far beyond compliance; it creates meaningful connections and opens your work to all users, regardless of ability.

Ready to take your commitment further? Schedule an ADA briefing with 216digital. Our team specializes in tailored web accessibility solutions, helping you mitigate risks and create a more inclusive online presence. Let’s build a better web—together.
Greg McNeil

January 9, 2025

How-to Guides

accessible code, ADA Compliance, How-to, WCAG, web developers, web development
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
2025 Web Accessibility Standards & Requirements
The digital world is changing fast, and the 2025 ADA web accessibility standards are right around the corner. For public entities and businesses, the countdown to compliance has begun. But this isn’t just about ticking legal boxes—it’s a chance to create online spaces that everyone can access and enjoy.

From keeping track of important compliance dates to navigating global standards like the European Accessibility Act, this guide has everything you need to stay ahead. Whether you’re running a local government site or a growing business, you’ll find actionable steps to get your website up to date with the latest accessibility standards. Let’s break it all down so you can be prepared for what’s coming.

Key Dates for Compliance

Staying on top of the timeline is crucial for meeting the new ADA Title II accessibility standards. Here’s the scoop on the most important deadlines for public entities:
- April 24, 2026: Public entities in cities or counties with 50,000 or more residents must comply with the updated standards.
- April 24, 2027: Smaller public entities—those in areas with fewer than 50,000 people—have an extra year to meet these same requirements.
What Public Entities Should Focus On

Public entities include everything from state and local governments to public schools, libraries, and other essential services. For these organizations, accessibility isn’t optional—it’s a must. That means ensuring your website works seamlessly with assistive technologies like screen readers, providing alternative text for images, and offering captions on video content.

Why Meeting These Deadlines Matters

Missing these deadlines isn’t just a bad look—it can lead to lawsuits and a loss of trust in your community. ADA lawsuits targeting government websites are on the rise, often flagging accessibility gaps that make it hard for users with disabilities to access essential services.

Don’t Forget Global Accessibility Standards

If your business operates internationally or even just ships products overseas, you’ll also need to think about global accessibility laws. Standards like the European Accessibility Act (EAA) and Accessibility for Ontarians with Disabilities Act (AODA) could apply to you, even if your business is based in the U.S.
- European Accessibility Act (EAA): Takes effect on June 28, 2025. Similar to the ADA, it requires accessible websites, apps, and digital services across the European Union.
- Accessibility for Ontarians with Disabilities Act (AODA): Applies to organizations in Ontario or those serving Canadian users. Emphasizes WCAG standards, with compliance starting January 1, 2025.
Ignoring these global laws can lead to fines or legal challenges, so keep them in mind if your reach extends beyond the U.S.

What’s New in the 2025 Web Content Accessibility Guidelines

The 2025 ADA updates focus on making websites easier for everyone to use, especially as technology keeps evolving. At the heart of these changes is the Web Content Accessibility Guidelines (WCAG) 2.2, developed by the World Wide Web Consortium (W3C).

Here’s what’s new:
- WCAG 2.2 Integration: The updated accessibility standards now include criteria for making websites more accessible on mobile devices, easier for people with cognitive disabilities, and generally more user-friendly.
- Assistive Technology Compatibility: Websites need to work smoothly with tools like screen readers and voice recognition software.
- Mobile Accessibility: With more people using phones and tablets, sites must be fully functional on smaller screens.
- Video Accessibility: There’s a bigger focus on captions, audio descriptions, and media players that everyone can use.
These updates aren’t just about staying out of court; they’re about building an inclusive online environment. For instance, captions on videos don’t just help users with hearing impairments—they also benefit anyone viewing in a noisy place.

The Cost of Ignoring Compliance

Noncompliance comes with serious risks. In 2024 alone, over 4,000 ADA lawsuits were filed in the U.S. Many stemmed from missing alt text, lack of keyboard navigation, or poor color contrast.

Copycat Lawsuits

A worrying trend is the rise of copycat lawsuits: about 41% of 2024’s accessibility lawsuits targeted companies that had already been sued before. These repeat lawsuits happen when businesses fix only part of their accessibility issues, leaving gaps that new plaintiffs exploit. Often, the same websites, related brands, or even parent companies become repeated targets, creating a cycle of litigation that can be difficult to escape.

The Cost of Noncompliance

Legal fees, settlements, and potential fines add up quickly, with smaller organizations often feeling the strain the most. Defending even one lawsuit can cost tens of thousands of dollars or more, depending on the complexity of the claims. For businesses with unresolved accessibility gaps, these lawsuits not only bring immediate costs but also invite ongoing legal scrutiny, making comprehensive compliance efforts critical to long-term risk management.

Steps to Ensure Compliance

Achieving compliance with the 2025 accessibility standards may seem daunting, but with a structured approach, it’s manageable. By taking proactive steps, you can stay ahead of the curve:

Meeting the 2025 standards might seem overwhelming, but with the right approach, it’s absolutely doable:
1. Audit Your Website: Use tools to catch common accessibility issues, but don’t skip manual checks for things like focus indicators or smooth screen reader navigation.
2. Train Your Team: Make sure everyone—from developers to content creators—understands accessibility guidelines.
3. Implement Updates: Prioritize fixes like alternative text for images and keyboard navigation improvements.
4. Monitoring: Accessibility isn’t a one-and-done thing. Regular updates and monitoring are essential.
Overcoming Challenges in Achieving Compliance

Even with clear guidelines, reaching full accessibility can be tough. A major hurdle lies in understanding the full scope of accessibility requirements. Automated tools often overlook hidden barriers, and smaller organizations may not have the resources or expertise to do a deep dive on every aspect of their site. Legacy systems could add in another wrinkle: retrofitting older platforms for accessibility can be time-consuming and costly.

That’s where partnering with accessibility experts like 216digital can make all the difference. We offer custom audits, expert training, and ongoing monitoring with tools like a11y.Radar, helping you build a sustainable compliance strategy.

It’s Time to Act

With the 2025 deadlines on the horizon, there’s no better time to get started. Sure, it might feel daunting at first, but making your online experience accessible to everyone brings long-term benefits for both your users and your brand. It’s not just about dodging lawsuits—it’s about doing the right thing.

By taking steps now—especially if your deadline is 2026 or just around the corner—you’ll save yourself time, money, and stress down the road. If you’re feeling stuck or overwhelmed, consider chatting with accessibility experts or scheduling a consultation with 216digital. Let’s work together to ensure your website is a place where everyone feels welcome and empowered.
Greg McNeil

January 7, 2025

Legal Compliance

2025, accessibility laws, ADA Compliance, EAA, International Accessibility Laws, WCAG
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
Email Accessibility: Why It Matters for Your Marketing
Did you know that many marketing emails are nearly impossible for some people to read? It’s true! People with disabilities, especially those who use screen readers, often struggle with text that isn’t coded properly or images that don’t have any descriptions. The good news is that email accessibility is simpler than you might think. In this article, we’ll explore why emails can be hard to read for people with disabilities, why you should care, and how you can start making changes today. Let’s dive in!

Why Accessibility in Emails Matters

You might be wondering, “Why should I think about email accessibility?” There are two big reasons:
1. Reach More Readers: Accessibility helps you connect with a larger audience, which means more potential customers.
2. It’s the Right Thing to Do: Many people rely on screen readers or special settings to read their messages, and they deserve the same great experience as everyone else.
Plus, consider this: There are about 61 million adults in the United States alone who have disabilities, and over one million of them are blind. Emails that aren’t accessible can stop them from reading newsletters, buying products, or joining your events. By focusing on accessibility, you’re ensuring everyone can connect with you.

The Business Case for Accessible Emails

You might ask, “Why should I spend my time on email accessibility?” Here are three compelling reasons:
1. Stay Legally Compliant: Laws like the Americans with Disabilities Act (ADA) may apply to online communication. Staying compliant avoids potential legal issues.
2. Expand Your Audience: People with disabilities make up a significant group. Including them ensures your message reaches more people.
3. Improve Content for Everyone: Accessible content benefits all users. For example, larger fonts are easier on the eyes, and descriptive link text helps people skimming emails on their phones.
In short, email accessibility isn’t just nice to have — it’s a smart move that can boost your brand and prevent legal headaches.

Why Marketing Emails Tend To Be Inaccessible

Let’s be honest: emails can be tricky. Here’s why:
- They Rely on Tables for Layout: Modern web pages use advanced CSS layouts, but many email clients don’t support them. This forces developers to use tables, which can confuse screen readers if not coded correctly.
- Limited Support for Buttons: Real <button> elements often aren’t supported. Replacing buttons with images can create accessibility issues if the images lack descriptions.
- Drag-and-Drop Tools Aren’t Perfect: Email builders like Mailchimp or HubSpot can generate messy or incomplete HTML code, leading to hidden accessibility problems.
These challenges make email accessibility tricky, but don’t worry. With a few simple steps, you can overcome these issues.

Building an Accessibility Checklist for Emails

Here’s a simple checklist to help you make your emails more accessible:

Template Setup (One-Time Fixes)
1. Add role=”presentation” to Tables: This attribute tells screen readers to ignore table structure, reducing confusion.
2. Underline Inline Links: Don’t rely on color alone to indicate links. Use underlines to make them easily identifiable.
3. Avoid Using One Big Image as Your Email: Screen readers can’t interpret a single large image. If images are disabled, subscribers will see an empty box instead of your content.
Campaign-Level Fixes
1. Add Alt Text to Every Image: Alt text provides descriptions for images. Keep it brief but clear (e.g., “Model wearing a red winter jacket”).
2. Use Semantic HTML Elements: Use <h1> for main headings, <h2> for subheadings, and <p> for paragraphs to help screen readers understand content structure.
3. Use Descriptive Links: Replace vague link text like “Click Here” with “View our winter jackets” to provide context.
Testing and QA for Your Accessible Emails

How can you ensure your emails are accessible? Test them!

Manual Testing

Use free screen readers like NVDA (Windows) or VoiceOver (Mac) to hear how your email sounds. Listening to your email read aloud is a great way to catch problems.

Automated Testing Tools

Use tools like Google Lighthouse or WAVE to scan your email’s web version for issues. Publish a temporary version, get the URL, and analyze it for errors.

A/B Testing

Test different versions of your accessible emails to see what resonates best with your audience. Compare engagement metrics to measure the impact of accessibility.

Accessibility Best Practices for Email Design

Here are additional tips for email accessibility:
1. Make It Mobile-Friendly: Ensure text, buttons, and layouts work well on smaller screens.
2. Choose Readable Fonts and Colors: Use high contrast (e.g., black text on a white background) and avoid tiny fonts.
3. Avoid Flashing or Moving Text: Fast-moving elements can be challenging for some users. Use animation sparingly.
Encouraging a Culture of Accessibility

Once you start focusing on accessibility, share your knowledge with your team:
1. Offer Mini-Trainings: Show marketing and design teams how to add alt text or check code for issues.
2. Collaborate with Developers: Work with your development team to address tricky code problems.
3. Celebrate Wins: Highlight successful accessible campaigns during team meetings to encourage continued focus.
Conclusion

Email accessibility matters because it helps people with disabilities, grows your audience, and enhances your brand’s reputation. The best part? It doesn’t have to be complicated. With simple steps like adding alt text, using descriptive links, and making your designs mobile-friendly, you can create emails that everyone can enjoy.

Take a moment to review your next email draft. Is there alt text? Are links descriptive? Are fonts readable? If so, you’re already ahead of many marketers. Keep going, and soon accessibility will become a natural part of your email marketing process, benefiting both your audience and your brand
Greg McNeil

January 3, 2025

How-to Guides, The Benefits of Web Accessibility

Accessibility, email accessibility, How-to, Web Accessibility, web developers
Accessibility in 2025: Why Web Accessibility Can’t Wait
These days, the internet is part of almost everything we do. Whether you’re shopping, learning, or connecting, the web matters. But what happens when some people can’t access your website in 2025? If your site isn’t built for everyone, think about the message that it sends.

In 2025, ignoring accessibility isn’t just risky—it’s neglectful. It can also lead to hefty legal issues. How many possible customers are you losing because your site doesn’t work for them? And how much would a lawsuit cost, both financially and in lost reputation? Accessibility isn’t just another box to check. It’s a responsibility we all share. If you’re still waiting to act, ask yourself: why the delay?

Evolving Accessibility Standards in 2025

Web accessibility has come a long way. The Web Content Accessibility Guidelines (WCAG) from W3C offer a reliable framework. These guidelines cover how to make digital spaces work for everyone, including people with disabilities.

By 2025, updates like WCAG 2.2 and the emerging WCAG 3.0 raise the bar further. These updates include new mobile standards, improved focus indicators, and better support for cognitive disabilities. By following these evolving standards, you’ll build a site that truly serves every user.

Government Enforcement and Legal Implications

Governments around the world are getting stricter about accessibility. In the U.S., Title II of the ADA now places stronger requirements on public entities. These rules will roll out in April 2026 and 2027, creating clear deadlines for compliance.

Meanwhile, the European Accessibility Act (EAA) takes full effect by June 28, 2025. This law applies to public institutions and private businesses, including e-commerce and financial services. Non-compliance could land you in legal trouble and damage your reputation. Adapting to these rules isn’t just about avoiding fines—it’s about making sure everyone can use what you offer.

Accessibility as a Business Imperative

Many businesses don’t realize how much accessibility can affect their bottom line. The truth is that investing in accessibility is a wise move.

Legal Implications

By 2025, lawsuits about inaccessible websites are becoming more common. In 2024 alone, there were over 4,000 ADA lawsuits in the U.S. That number highlights a growing push for compliance. One unfortunate trend is “copycat” lawsuits, where 41% of 2024’s cases targeted businesses with previous noncompliance.

Settlements can run anywhere from $10,000 to $100,000, not counting legal fees. Worse still, your public image may take a hit that’s hard to fix. Courts have made it plain: websites must be accessible. If you ignore these requirements, you could be facing big legal bills and a tarnished reputation.

Market Potential in 2025

Accessibility isn’t just about avoiding risks. It also opens the door to millions of new customers. About 15% of the world’s population has some form of disability. Add older adults who benefit from clear, easy-to-use sites, and you’ve got an even bigger market.

In the U.S. alone, people over 50 drive more than $8 trillion in economic activity each year, according to AARP. That’s huge, and it’s only growing as our population ages. Making your site accessible also boosts SEO and discoverability. This helps everyone, not just those with specific disabilities.

Competitive Advantage

If two companies offer the same service, but one has a user-friendly website, guess who wins? Accessibility sets you apart. It shows you respect and value every customer, building trust in your brand. In 2025, that might be the difference between thriving and floundering.

An accessible site also signals that your brand is forward-thinking and inclusive. Many customers care about companies that “walk the talk” on social issues. By putting accessibility first, you position yourself as an industry leader.

Challenges and Misconceptions

Some organizations stall on accessibility because they think it’s too pricey or too complicated. Others believe quick fixes, like overlays, will solve everything. These myths can hold your business back.

The Myth of Overlays

Overlays promise one-click solutions, but they often cause more harm than good. They can break your website’s functionality or confuse users of assistive technologies. Sometimes, they even block screen readers or tangle up navigation.

They also don’t meet many legal requirements, leaving you open to lawsuits. True accessibility needs mindful design, thorough testing, and a commitment to ongoing improvements—no shortcuts allowed.

For more information on the harm of screen overlays, check out the Overlay Fact Sheet.

Fear of Cost

Yes, accessibility takes time and resources. But it doesn’t have to ruin your budget. Start small by fixing the biggest barriers on your site. Simple changes—like adding alt text or improving color contrast—can make a huge impact.

In the U.S., businesses can also use the Disabled Access Credit for accessibility expenses. Over time, small steps lead to big changes. You’ll build a more inclusive online presence and reduce the risk of costly legal battles.

The Role of Technology in Accessibility

Fortunately, technology is making accessibility easier. In 2025, AI-driven tools can help identify issues quickly. Popular tests, like Google Lighthouse or WAVE, flag areas that need improvement.

Assistive technologies are also evolving. Screen readers and voice recognition software are getting smarter. However, technology alone can’t solve everything. You must understand your users and design with their needs in mind. That human-centered approach makes your website better for all.

Practical Steps to Get Started in 2025

Worried your website isn’t accessible yet? Don’t panic. You can start today:
1. Conduct an Audit: Use tools like Google Lighthouse or hire an expert to identify issues on your site.
2. Fix High-Impact Problems: Start with basics like adding alt text, improving keyboard navigation, and fixing color contrast.
3. Build Accessibility Into Your Workflow: Make accessibility a part of every project, from design to development.
4. Seek Help When Needed: Partner with accessibility experts to guide your efforts and ensure long-term success.
Maintain and Monitor Accessibility

Remember, accessibility is a journey, not a one-time fix. Keep track of updates and new content to ensure they don’t add barriers—tools like Accessibility Radar (a11y.Radar) help you watch your site’s accessibility over time. By staying proactive, you’ll keep your site usable for everyone.

Looking Ahead: The Future of Accessibility

In 2025, you can’t afford to ignore accessibility. It’s crucial for growth, legal compliance, and being a decent digital citizen. When you make your site accessible, you open your business to more customers, strengthen your brand, and help create a fairer online world.

Don’t wait for a lawsuit or a complaint to spur action. Start now. Conduct an audit, fix any issues you find, and commit to continuous improvement. If you need help, companies like 216digital are ready to guide you. Together, let’s build a web that works for everyone.
Greg McNeil

January 2, 2025

The Benefits of Web Accessibility, Web Accessibility Remediation

2025, Accessibility, ADA Compliance, New Year's Resolution, Web 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
Accessibility Overlays: Band-Aid Solutions?
Web accessibility is about making sure that everyone, including people with disabilities, can use your website with ease. Many businesses, however, reach for a quick fix known as a “web accessibility overlay.” These overlays claim to instantly solve a website’s accessibility problems by adding a single line of code. At first glance, this may sound like a dream come true: no major redesigns, no deep coding changes, and no extended timelines. Yet overlays often fail to address the real barriers that people with disabilities face. In fact, they can create new challenges and offer website owners a false sense of security.

In this article, we will explore why web accessibility overlays are often called a “Band-Aid solution” and why relying on them can do more harm than good. We will look at some of the technical limitations, discuss how they can conflict with assistive technologies, and share better ways to make your website truly accessible. We will also include links to helpful resources you can explore independently.

What Are Web Accessibility Overlays?

Web accessibility overlays are add-on tools, often in the form of a plugin or script, that claim to repair accessibility issues on a website automatically. Once installed, they usually give users a menu of features such as:
- Text resizing
- Color contrast adjustments
- Keyboard navigation controls
- Screen reader-friendly labels
These options may seem helpful, and some are. However, these overlays do not usually fix deeper issues in the website’s code. Overlays focus on surface-level changes that might look or feel good initially. For example, making text larger or changing color contrast might help some people. But someone who uses a screen reader or another assistive device might still find the site impossible to navigate if the page structure is confusing or missing proper markup.

Why Accessibility Overlays Fall Short

While overlays may claim to bring your site into compliance with standards like the Web Content Accessibility Guidelines (WCAG), they cannot fix serious problems that come from poor coding, improper headings, or missing labels. Let’s explore some core reasons why these tools can fail.

1. They Don’t Fix Structural Code Issues

A website that is built with accessibility in mind has clean, well-labeled HTML code and logical headings (like <h1>, <h2>, and so on). It also uses the right ARIA (Accessible Rich Internet Applications) attributes where needed. These parts of the code help assistive technologies—like screen readers—understand how the page is organized. If your code is poorly structured, an overlay might add color adjustments or keyboard focus outlines, but it won’t rewrite the site’s underlying structure. Missing or incorrect code stays broken, which causes ongoing problems for anyone who relies on a screen reader or keyboard navigation.

2. Conflicts with Assistive Technologies

One goal of web accessibility is to ensure that people using screen readers, braille displays, or voice recognition software can move through a site and understand its content. Overlays can accidentally disrupt these tools by adding unwanted code or labeling. For example, a screen reader might end up reading duplicate or confusing text because the overlay tries to label items automatically. This could result in a frustrating experience, causing users to abandon your site altogether.

3. False Sense of Compliance

Some businesses install an overlay hoping to protect themselves from legal action under the Americans with Disabilities Act (ADA). However, simply having an overlay does not mean your website is truly accessible or “ADA compliant.” In fact, in 2024 alone, 1,023 companies with an accessibility widget on their website received lawsuits, underscoring that overlays alone cannot shield businesses from legal action. In recent years, many sites using these tools have still faced lawsuits because of the underlying accessibility problems. Accessibility overlays often promise quick compliance, but the law cares about actual accessibility, not just appearances. Relying on an overlay can leave you vulnerable and unprepared if complaints or legal notices arise.

4. Ethical Concerns and User Frustration

Overlays may look like an easy fix for you, but they can feel like a barrier for those who need real accessibility improvements. Many people with disabilities have shared stories of frustration when they encounter overlay menus that don’t work correctly or override their screen reader settings. This can be discouraging for users who regularly deal with inaccessible websites. They may see the overlay as another obstacle rather than a tool that truly helps them. From an ethical standpoint, offering a patch that doesn’t solve deeper issues can be viewed as ignoring the experiences of people with disabilities.

The Risks of Taking the Easy Way Out

Accessibility overlays give website owners the idea that fixing accessibility is simple and quick. Sadly, that is almost never the case. By relying on an overlay, you risk:
- Legal Action: Courts can—and do—rule that a website with an overlay still has accessibility problems. An overlay will not protect you if people with disabilities cannot use your site.
- Damaged Reputation: When users have a poor experience on your site, word can spread quickly. This can harm your brand and turn potential customers away.
- Ongoing Maintenance Issues: Overlays must be updated along with your website’s updates. If the overlay breaks or conflicts with new code, your site could become even harder to use.
Instead of merely putting a bandage on the problems, developing or improving your website in ways that truly benefit all users would be better.

Steps to Achieve Real Accessibility

To create a site that everyone can use, consider a more thorough strategy. This involves reviewing the code, testing it with real users, and making changes that last. Below are some steps you can take.

1. Start with Clean, Semantic Code

Semantic HTML is a fancy way of saying you use the right tags to describe the right content. For example, headings (<h1>, <h2>, etc.) should be in order, and important landmarks (such as navigation and main content) should be labeled. Make sure that images include informative alt text, forms have clear instructions, and interactive elements have correct ARIA attributes if needed. When the base of your site is strong, many common accessibility problems disappear.

2. Test with Real Users and Automated Tools

Automated checkers can point out some problems, like missing alt text or heading errors. However, these tools cannot catch everything. The best approach is to test your website with actual users who have disabilities. Ask for their feedback and watch how they move through your site. You will quickly find issues that an overlay would never fix. This user-first approach ensures your improvements are based on real-world experiences.

3. Collaborate with Accessibility Experts

If you are not sure where to begin, seek help from professionals who specialize in digital accessibility. They can run a thorough audit, identify areas that need work, and guide you in making the proper fixes. This often involves reviewing your design, testing your site’s code, and recommending best practices so that all new content you create will also be accessible.

4. Provide Ongoing Training

Accessibility should be a team effort. Everyone who works on your website—developers, designers, content creators—should know the basics of accessible design. This means understanding how to create keyboard-friendly navigation, how to write alt text, and how to structure pages with clear headings and labels. If your team knows these skills, you are less likely to introduce new barriers when adding or editing content.

5. Plan for Long-Term Maintenance

Websites are never finished; they change over time. That means accessibility is an ongoing project. As you update pages, launch new features, or switch platforms, keep accessibility in mind. Continue testing, train your team, and regularly check for new issues. This helps you stay proactive rather than relying on any one tool to fix barriers as they come up.

Additional Resources

If you would like to learn more about doing accessibility the right way, here are some helpful links:
1. Web Content Accessibility Guidelines (WCAG): The official guidelines published by the World Wide Web Consortium (W3C).
2. W3C Web Accessibility Initiative: Offers guidelines, techniques, and tutorials on how to create an accessible website
3. WebAIM: A well-known resource that offers articles, tools, and services related to web accessibility.
4. The A11Y Project: A community-driven site with resources for building and maintaining accessible websites.
These resources can guide you in understanding the deeper aspects of accessibility and how to address them.

Moving Forward with True Accessibility

Web accessibility overlays may seem like a quick and convenient solution, but they are ultimately a Band-Aid on a much larger problem. While they can address surface-level issues, they often fail to tackle the deeper, structural barriers that prevent people with disabilities from fully engaging with your website. Worse, relying on overlays can give businesses a false sense of compliance, leaving them vulnerable to legal action and alienating users who need genuine accessibility improvements.

Real accessibility requires a proactive, thoughtful approach—one that prioritizes clean code, user testing, and ongoing education. By investing in these strategies, you can create a website that is not just compliant with legal standards but genuinely inclusive for everyone.

If you’re ready to move past quick fixes and build a site that welcomes all users, 216digital is here to help. We offer expert accessibility audits, training, and monitoring services to ensure your website meets WCAG standards and delivers a seamless experience for every visitor. Reach out to us today to schedule an ADA compliance briefing and take the first step toward meaningful, lasting accessibility.

Let’s build a more inclusive digital world—together.
Greg McNeil

December 30, 2024

Web Accessibility Remediation

Overlay, Overlay widgets, screen overlays, Web Accessibility, Website Accessibility

What Is the WAVE Accessibility Tool?

Key Features of WAVE Accessibility Tools

Browser Extensions

Online WAVE Tool

Visual Feedback

Accessibility Panels

How to Use WAVE Effectively

Getting Started

Running an Analysis

Interpreting Results

Prioritizing Fixes

Exporting and Sharing Results

Strengths and Limitations of WAVE

What It Does Well

Where It Falls Short

Best Practices for Using WAVE

Combine with Other Tools

Manual Testing Matters

Train Your Team

Start Early

Make It Part of a Bigger Strategy

That’s a Wrap: Waving Goodbye to Barriers

What is the European Accessibility Act?

Scope of the EAA

EN 301 549: The Technical Backbone of the EAA

Are There Any Exceptions to EAA Compliance?

Why the EAA Matters

It’s Legally Required

Reach a Larger Audience

Better User Experience for Everyone

Boost SEO and Discoverability

How to Prepare for the EAA

Overlays: The Quick Fix That Falls Short

The Upside of Accessibility

Don’t Wait: Turn Accessibility into an Advantage

What Is Accessible Code?

The Four Golden Rules of Accessibility: POUR

Best Practices for Writing Accessible Code

1. Use Semantic HTML

2. Make Forms Accessible

3. Ensure Keyboard Navigation

4. Add Alt Text to Images

5. Mind Your Colors

6. Use ARIA Wisely

7. Don’t Forget Multimedia

Testing Your Accessible Code

Challenges Developers Face—and How to Overcome Them

Keep Learning and Building Accessible Code

What Are Web Accessibility Extensions?

Popular Accessibility Extensions

Why These Tools Are Helpful

The Limits of Accessibility Extensions

Practical Steps for Using Accessibility Extensions

Going Beyond Extensions: Manual Testing & Real Users

Professional Tools and Services

Additional Resources to Explore

Conclusion

Key Dates for Compliance

What Public Entities Should Focus On

Why Meeting These Deadlines Matters

Don’t Forget Global Accessibility Standards

What’s New in the 2025 Web Content Accessibility Guidelines

The Cost of Ignoring Compliance

Copycat Lawsuits

The Cost of Noncompliance

Steps to Ensure Compliance

Overcoming Challenges in Achieving Compliance

It’s Time to Act

Accessibility Lawsuits Are Shifting to State Courts

New York Is at the Center of the Action

Copycat Lawsuits Are a Growing Threat

Small Businesses Are in the Spotlight

Accessibility Widgets: Not the Quick Fix You Think They Are

What You Can Do in 2025

Immediate Actions

Conduct a WCAG 2.2 Audit

Train Your Team

Long-Term Strategies

Build Accessibility Into Your Workflow

Partner With Experts

The Problem with `display: none`

Managing Visibility with `aria-hidden` and the `hidden` Attribute

`aria-hidden="true"`