216digital.
Web Accessibility

Phase 1
Web Remediation for Lawsuit Settlement & Prevention


Phase 2
Real-World Accessibility


a11y.Radar
Ongoing Monitoring and Maintenance


Consultation & Training

Is Your Website Vulnerable to Frivolous Lawsuits?
Get a Free Web Accessibility Audit to Learn Where You Stand
Find Out Today!

Web Design & Development

Marketing

PPC Management
Google & Social Media Ads


Professional SEO
Increase Organic Search Strength

Interested in Marketing?
Speak to an Expert about marketing opportunities for your brand to cultivate support and growth online.
Contact Us

About

Blog

Contact Us
  • A Case for Starting Accessibility Early in Development

    When you’re kicking off a new web project, it’s easy to focus on exciting features and visual design. But here’s something that often gets pushed aside until it’s almost too late: accessibility. The truth? Accessibility isn’t just a box to check off at the end of development; it’s a fundamental part of creating an inclusive, user-friendly experience from day one. To truly succeed, you need to start accessibility early.

    Think about it: no one wants to realize their new website or app needs major tweaks just to be usable for everyone. Starting accessibility early not only benefits people with disabilities but boosts usability for all your users, saves you money, and keeps you in line with standards like Web Content Accessibility Guidelines (WCAG). And who doesn’t want to avoid headaches later on?

    Let’s break down why embedding accessibility into your project from the very beginning is worth every bit of effort—and how to make it happen smoothly.

    Why Start Accessibility Planning from the Beginning?

    Making accessibility a priority from day one can feel like a big commitment, but here’s what you gain by choosing to start accessibility early:

    Avoid Costly Retrofits

    Fixing accessibility issues at the end of a project can mean reworking significant parts of your site—an expensive and time-consuming ordeal. Imagine designing your site, launching it, and then realizing it doesn’t meet accessibility standards. Adding features like keyboard navigation or fixing color contrast at that point can mean redoing large chunks of your design. Planning for these details early on keeps everything smoother (and kinder on your budget).

    Enhance User Experience for All

    When you start accessibility early, you set the stage for a user experience that is friendly and inclusive for everyone. Accessibility isn’t just for those with disabilities—it’s for everyone. Features like clear navigation, easy-to-read text, and well-labeled elements make browsing better for all users. Designing with accessibility in mind from the start ensures these benefits are baked in, rather than added later.

    Stay Compliant and Avoid Legal Issues

    Starting with WCAG standards and other accessibility guidelines from the get-go helps you avoid legal hiccups. These guidelines form the backbone of inclusive web design and ensure you’re in line with regulations like the Americans with Disabilities Act (ADA). Following these rules early on makes compliance one less thing to worry about.

    How to Integrate Accessibility into Each Stage of Development

    Accessibility can be woven into every phase of your project with just a bit of planning. Here are some actionable steps for developers and designers:

    Design with Accessibility in Mind

    From the beginning, designers play a critical role in accessibility by setting the structure and visual flow of a project. Here are a few accessibility best practices to incorporate during the design phase:

    Color Contrast and Readability

    Make sure your text is easy to read against its background. According to WCAG guidelines, regular text should have at least a 4.5:1 contrast ratio, while larger text should have a 3:1 contrast ratio. Testing tools like WebAIM’s Color Contrast Checker make this quick and easy to verify.

    Intuitive Layout and Navigation

    A clear, intuitive layout ensures all users can navigate your site. Place navigation elements consistently, keep forms simple, and use ample white space to make content easier to digest. These are just a few examples of how to start accessibility early in your design strategy.

    Descriptive Text for Buttons and Links

    Buttons and links should have descriptive text that tells the user exactly what will happen when they click. Instead of a vague “click here,” label it with “Learn More About Accessibility,” for example. Clear labels improve navigation for users and assistive technologies alike.

    Use the Right HTML Tags

    Developers can make a huge impact when they start accessibility early by using semantic HTML. Semantic HTML tags—like <header>, <main>, <nav>, and <footer>—convey the structure of your webpage to screen readers and other assistive devices, helping users navigate more effectively.

    Proper HTML Markup

    Use headings (<h1>, <h2>, etc.) in a logical order, and never skip heading levels. This creates a clear hierarchy for users relying on screen readers and assists everyone in navigating your content.

    Descriptive Alt Text for Images

    Screen readers rely on alternative text (alt text) to describe images to visually impaired users. Ensure every image with meaningful content has a description that conveys what’s in the image or its purpose. If the image is purely decorative, use an empty alt attribute (e.g., alt=" ") to signal to screen readers that it can be ignored.

    ARIA Attributes

    Accessible Rich Internet Applications (ARIA) roles and attributes provide additional context where HTML alone may fall short. For example, you can use aria-label to describe the function of a button or aria-live to notify screen readers of real-time changes, like alerts.

    Test for Accessibility as You Go

    Testing for accessibility throughout development lets you catch issues early before they become a headache to fix. Here’s how to implement regular accessibility checks:

    Automated Accessibility Tools

    Automated testing tools like Lighthouse and WAVE can detect many common accessibility issues, such as missing alt text or incorrect heading levels. However, keep in mind that while these tools are valuable, they’re not a complete solution.

    Manual Testing and Keyboard Navigation

    Not all accessibility features can be evaluated by automated tools, so manual testing is essential. Many users with disabilities rely on keyboards instead of a mouse, so test your site using keyboard navigation alone. Make sure users can access all interactive elements (like links, forms, and buttons) and follow a logical tab order.

    Screen Reader Testing

    Use screen readers like NVDA (for Windows) or VoiceOver (for Mac) to simulate how users with visual impairments experience your site. This will help you catch any missing descriptions, confusing elements, or awkward navigation.

    Get Feedback from Users with Disabilities

    Involving people with disabilities in testing phases offers invaluable insights. Real users bring unique perspectives that automated tools or simulated testing just can’t replicate.

    Plan for Inclusive Testing

    Recruit a diverse group of testers who use different assistive technologies, including screen readers, magnification software, and voice control. Their feedback can reveal practical challenges and usability issues you might not anticipate.

    Iterate Based on Feedback

    Make adjustments based on real-world experience and retest if needed. Accessibility is an ongoing process, and user feedback will help you understand where improvements are necessary.

    Regularly Check Your Site

    Keeping your site accessible isn’t a one-and-done task—it’s an ongoing process. Regular audits help ensure that your site or app stays up to date with accessibility standards as you make changes or add new features. These check-ups can catch any issues that might have been overlooked during development, or that pop up over time. But audits alone don’t cover everything; that’s where regular monitoring comes in.

    Services like a11y.Radar makes a big difference by providing continuous monitoring to help keep your website accessible. With automated checks and detailed reports, a11y.Radar alerts you to potential issues early on so you can fix them before they turn into bigger problems. Plus, it helps you stay aligned with current WCAG guidelines, which are always evolving.

    Combining regular audits with a monitoring service like a11y.Radar keeps your site running smoothly and ensures a user-friendly experience for everyone.

    Building a Culture of Accessibility

    Making accessibility a foundational part of your development culture is key to sustaining these practices long term. Here are some ideas to foster an accessibility-first mindset in your team:

    Educate and Train Your Team

    Provide training on accessibility guidelines and tools for all team members, from designers and developers to project managers and content creators. Workshops, webinars, and resources on WCAG standards and inclusive design can help create a shared understanding of accessibility’s importance.

    Keep Accessibility Resources Available

    Ensure your team has access to accessibility checklists, WCAG guidelines, and tool recommendations. Having these resources easily accessible means team members can refer to them at any stage of development.

    Regularly Review and Share Accessibility Wins

    Celebrate small successes, such as completing accessibility testing on a new feature or receiving positive feedback from an accessibility audit. Recognizing and sharing progress reinforces the importance of this work and motivates your team to continue prioritizing accessibility.

    Helpful Tools for Accessibility

    There are a variety of helpful tools for accessibility checks and improvements. Here are a few top options:

    • WebAIM’s Color Contrast Checker: Verifies that contrast meets WCAG standards for readability.
    • Lighthouse and WAVE: An open-source accessibility tool that runs quick checks on your web pages for WCAG compliance.
    • Screen Readers: Test with NVDA (Windows), VoiceOver (Mac), and TalkBack (Android) to experience your site from the perspective of visually impaired users.
    • ARIA Authoring Practices Guide: This guide provides information on implementing ARIA roles and attributes to enhance assistive technology compatibility.

    Ready to Make Accessibility Part of Your Game Plan?

    So, there you have it—starting accessibility early isn’t just a nice-to-have; it’s a win-win for everyone involved. By weaving accessibility into your project from day one, you’re not only sidestepping costly revisions but also crafting a better experience for all your users. Plus, you’re keeping things legally sound, which is always a good move.

    But we get it—navigating the world of WCAG guidelines and accessibility best practices can feel a bit like decoding a secret language. If you’re ready to start accessibility early in your web development process without complicating your project, let’s talk. Schedule an ADA briefing with us at 216digital, and we’ll guide you through your journey in plain English (no tech jargon). Let’s work together to make the digital world a more inclusive place—one accessible website at a time.

    Greg McNeil

    October 28, 2024
    Legal Compliance, The Benefits of Web Accessibility
    Accessibility, Accessibility testing, ADA Compliance, UX, web development
  • ADA Lawsuits: How They’re Shaping the Internet

    The Internet is an essential part of daily life. We shop, work, learn, and even socialize online. But for millions of people with disabilities, the digital world can feel like a locked door. That’s where the Americans with Disabilities Act (ADA) steps in. Originally designed to ensure access to physical spaces, the ADA is now playing a significant role in making sure the digital world is accessible to everyone.

    Let’s dive into how ADA lawsuits are shaping the future of the Internet and why this movement towards web accessibility matters for all of us.

    Why Web Accessibility Matters

    Imagine trying to buy groceries online, book a doctor’s appointment, or read the news—but being unable to do so because the website isn’t accessible. This is the reality for many people with disabilities. Web accessibility aims to remove these barriers, making sure websites are usable by all, whether someone is blind, deaf, has limited mobility, or faces cognitive challenges.

    It’s not just about compliance; it’s about creating a better experience for everyone. When websites are more accessible, they’re also more user-friendly. For example, features like closed captions help users with hearing impairments, but they’re also useful for anyone in a noisy environment.

    How the ADA Applies to the Digital World

    The ADA, passed in 1990, is a law meant to prevent discrimination against people with disabilities. While it initially focused on physical locations, it’s evolved to include digital spaces like websites, mobile apps, and online services.

    Title III of the ADA requires “places of public accommodation” to be accessible. While that originally meant places like stores and restaurants, the DOJ published guidance in 2022 confirming its position that the ADA does apply to websites, stating:

    “…the Department has consistently taken the position that the ADA’s requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web.”

    – U.S. Department of Justice | Guidance on Web Accessibility and the ADA (2022)

    This shift is significant because it brings the same standards of accessibility that apply to physical spaces into the digital realm. If a website isn’t accessible, it could violate the ADA—leading to legal action.

    Key Lawsuits Driving Change

    Several high-profile lawsuits have set important legal precedents for web accessibility, encouraging businesses to prioritize digital inclusivity. Here are some of the most significant cases that have reshaped the digital landscape:

    Robles v. Domino’s Pizza (2019)

    In 2016, Guillermo Robles, a blind man, sued Domino’s Pizza because he couldn’t use their website or mobile app to order food. Robles relied on screen-reading software, but Domino’s website and app were not compatible with it, making the services inaccessible.

    The case went through multiple courts, with Domino’s arguing that the ADA did not clearly apply to websites. However, the Ninth Circuit Court of Appeals disagreed, stating that the ADA does cover websites and apps if they are closely tied to a physical location that serves the public. The U.S.

    Supreme Court declined to review the case, effectively affirming the lower court’s ruling. This landmark case established a strong precedent that digital services must be accessible, especially if they’re an extension of a physical business.

    Winn-Dixie Stores Inc. v. Gil (2017)

    In 2016, Juan Carlos Gil, a blind man who uses screen-reading software, attempted to access the website of the grocery chain Winn-Dixie but found it was incompatible with his software. Unlike Robles v. Domino’s, Winn-Dixie had no functional website components for users to complete transactions online; however, the website did allow users to refill prescriptions, access coupons, and find store locations—services that were considered extensions of its physical stores.

    The federal court sided with Gil, ruling that the website’s connection to the physical stores meant it had to comply with ADA requirements. Although the Eleventh Circuit later reversed this decision, arguing that websites themselves are not necessarily “places of public accommodation,” this case still sparked important conversations about digital accessibility. It highlighted that when a website is integral to a business’s services, it must meet accessibility standards.

    Bashin v. ReserveCalifornia.com (2023)

    Bryan Bashin, a blind user, filed a lawsuit against ReserveCalifornia.com, a state-run site responsible for booking campsites in California’s state parks. Bashin faced numerous challenges while using the website, including unlabelled buttons and forms that his screen reader couldn’t interpret. What made this case unique was that Bashin targeted not just the website itself, but also the state contractor responsible for the website’s development and maintenance.

    This lawsuit emphasized the importance of holding government contractors accountable for digital accessibility, setting a new precedent. The court ruled in favor of Bashin, making it clear that not only are government-run websites subject to ADA compliance, but so are third-party developers who manage public websites. This ruling added new pressure on contractors and developers to implement accessibility features from the start, ensuring that websites are built with inclusivity in mind.

    Evolving Legal Requirements for Web Accessibility

    As the number of ADA lawsuits grows, so do the legal requirements for web accessibility. While there’s no one-size-fits-all standard, the Web Content Accessibility Guidelines (WCAG) have become the go-to benchmark. These guidelines are designed to make websites more usable for people with disabilities and cover areas like:

    • Text Alternatives: Providing descriptive text for images, videos, and other non-text content.
    • Keyboard Accessibility: Ensuring users can navigate sites using only a keyboard.
    • Readable Fonts and Color Contrast: Make sure fonts are easy to read, and colors are distinguishable for people with vision impairments.
    • Video Captions and Transcripts: Offering captions for videos and transcripts for audio content.

    By aligning your website with these guidelines, you reduce the risk of legal challenges and create a better user experience for everyone.

    How Businesses Are Adapting

    As the legal landscape shifts, many businesses are taking proactive steps to ensure their websites comply with accessibility standards. Here are a few strategies they are employing:

    Investing in Training and Resources

    Many companies are now training their web development teams on accessibility standards. By understanding the principles of web accessibility, teams can create more inclusive websites from the ground up.

    Conducting Accessibility Audits

    Regular audits of websites can identify areas needing improvement. Companies are increasingly employing tools and experts to evaluate their sites against WCAG standards. This helps pinpoint issues like missing alt text or improper heading structures.

    Integrating Accessibility Features from the Start

    More businesses are making accessibility a priority during the design phase. This includes adding features such as keyboard navigation and ensuring that content is structured in an accessible way. By embedding these practices from the beginning, companies can avoid costly retrofits down the line.

    Engaging with the Community

    Some businesses are partnering with organizations that advocate for individuals with disabilities. By seeking feedback from actual users, they can better understand accessibility challenges and improve their websites accordingly. This not only leads to a better product but also fosters goodwill and loyalty among customers.

    Long-Term Implications for the Future of the Internet

    The growing emphasis on web accessibility has several long-term implications for the future of the Internet:

    Increased Awareness of Inclusivity

    As more companies recognize the importance of web accessibility, we will likely see a cultural shift in how businesses approach design and user experience. Prioritizing inclusivity can attract a broader audience and create loyal customers.

    Legal Precedents Will Shape Standards

    As more ADA lawsuits are filed, legal precedents will increasingly dictate what is considered acceptable in terms of web accessibility. Businesses will need to stay informed about these developments to avoid potential legal pitfalls.

    Technological Advancements

    The demand for accessible web design will likely spur innovation in technology and tools. We can expect new solutions that simplify the process of making websites accessible, from AI-driven accessibility checkers to improved assistive technologies.

    A Culture of Accessibility

    As web accessibility becomes a norm, future designers and developers will likely prioritize inclusivity from the outset. This could lead to a more inclusive internet overall, where all users can engage equally.

    Conclusion

    Web accessibility is reshaping the digital landscape, and it’s clear that the ADA’s influence is paving the way for a more inclusive internet. While compliance with these evolving standards may seem daunting, it’s ultimately about creating a digital environment where everyone can navigate and engage with ease. By enhancing accessibility, you’re not just adhering to legal requirements—you’re fostering a more user-friendly experience for all.

    Instead of seeing accessibility as a burden, consider it an opportunity to make your website more welcoming and effective. It’s a chance to lead by example and demonstrate your commitment to inclusivity. If you’re curious about where your website stands, scheduling an ADA briefing with 216digital can be a great first step. Let’s shift the focus from obligation to opportunity, one accessible website at a time.

    Greg McNeil

    October 22, 2024
    Legal Compliance, The Benefits of Web Accessibility
    ADA, ADA Compliance, ADA Lawsuit, Web Accessibility
  • 5 Accessibility Mistakes to Dodge This Holiday Season

    Many eCommerce businesses make most of their income during the holiday shopping season, so your website must perform to the best of its ability during the Black Friday and Cyber Monday promotions. Web Accessibility is probably the last thing on your mind when you’re already in a frenzy to ensure you’re maximizing every visit to your website. However, you may be leaving money on the table or making yourself vulnerable to expensive litigation if you don’t stay diligent with your digital inclusivity.

    For many customers—especially those with disabilities—shopping online is their primary option. If your website isn’t accessible, you’re alienating a significant portion of your audience (up to 20%) and potentially violating the Americans with Disabilities Act (ADA).

    To help you prepare for the holiday rush, let’s go over five common web accessibility mistakes businesses make during holiday promotions and how you can avoid them.

    Insufficient Alt Text for Images

    Holiday promotions often rely on eye-catching images, banners, and product displays. However, if those images lack appropriate alt text, customers using screen readers won’t be able to understand their content. Alt text (short for alternative text) provides a textual description of an image that’s accessible to screen reader users.

    Why It Matters

    Alt text is essential for individuals with visual impairments. If a visually impaired customer is browsing your site and encounters an image without a proper description, they’ll have no idea what’s being displayed. Imagine running a huge Black Friday sale, but your best deals are hidden from a portion of your audience simply because your images aren’t described.

    How to Fix It

    As you add promotional banners and products to the website, always make sure you’re adding alt text to the images. Here’s an example:

    <img src=" winter-sale-banner.jpg" alt=" Banner for Winter Sale - Up to 50% off jackets and coats">

    Do not use image file names or vague text such as “sale-img” or “Sale Image”. Make sure the alt text contains enough information that the user understands the purpose of the image and contains any words that appear on the image.

    Poor Color Contrast

    With holiday promotions comes festive design—bright colors, eye-catching buttons, and themed decorations. While these designs may look great, they often fail color contrast standards. Having adequate color contrast is not only good for color-blind users, but it also makes the website easier for everyone to navigate.

    Why It Matters

    According to WCAG, the minimum contrast ratio between text and background should be at least 4.5:1 for normal text and 3:1 for larger text. When the contrast is too low, customers with low vision or color blindness may struggle to read important information, such as product details or discount codes.

    How to Fix It

    Use tools like the WebAIM Contrast Checker to ensure your color choices meet the WCAG contrast ratio guidelines. For example, a light gray text on a white background will likely fail the contrast test, but switching to a darker gray or black can make a big difference.

    Here’s an example of a common mistake and how to correct it:

    <!-- Poor contrast -->
    <p style="color: #cccccc; background-color: #ffffff;">50% off all products!</p>
    <!-- Better contrast -->
    <p style="color: #000000; background-color: #ffffff;">50% off all products!</p>

    Pay attention to your text color, button colors, and even the contrast of smaller elements like icons.

    InaccessibleNavigation and Controls

    Most store owners don’t consider that some users do not navigate their website with a mouse. Even some users without disabilities prefer to use other input methods to quickly navigate some sections of your website.

    Why It Matters

    Blind and motor-impaired users rely on the keyboard, gestures, or voice commands to navigate your website. If your navigation, contact forms, category filters, and product pages are not properly coded to support these input methods, these users will be denied equal access to the website and may not be able to make a purchase with you at all, losing you a valuable customer and potentially damaging your reputation.

    How to Fix It

    Regularly test the functional portions of your website with a keyboard. Attempt to start at the homepage, navigate to a category page, use the category filters, add/remove product quantities, and select product options without your mouse. If you encounter a problem with an element, it’s likely not coded using the correct element. You can force an element to receive keyboard focus using the tabindex attribute. The role="button" attribute will help users navigating with assistive technology better understand the purpose of the control:

    <span class="swatch-button" tabindex="0" role="button">Beige</span>

    Better yet, use the correct semantic HTML tag to accomplish this:

    <button class="swatch-button">Beige</button>

    Semantic HTML helps users relying on assistive technology understand the purpose of controls and also helps Google better understand the structure of your website:

    <nav>
    	<a href="/products">All products</a>
    	<a href="/products/sale">Sale products</a>
    	<a href="/contact">Contact Us</a>
    </nav>

    Missing Captions on Promotional Videos

    Videos are an excellent way to showcase products, promote deals, or explain services during the holiday season. However, many businesses forget to include captions, making the content inaccessible to users who are deaf or hard of hearing.

    Why It Matters

    Videos contain a lot of important information in the form of spoken words and visual cues. Both blind and deaf users rely on accessible closed captions (not just subtitles) to understand the content of the video. Also, some users may be in noisy environments and are unable to hear the video.

    How to Fix It

    Most popular video platforms have auto-captioning features, but these tend to just subtitle the video rather than create truly accessible closed captions. There are many cheap and easy closed captioning services, such as Rev.com, that have quick turnarounds.

    Here’s how you implement closed captions from an external service:

     <video controls>
      <source src="promo-video.mp4" type="video/mp4">
      <track kind="captions" src="captions_en.vtt" srclang="en" label="English">
      Your browser does not support the video tag.
    </video>

    Always test the captions to make sure they sync properly with the video and cover both spoken dialogue and important sound effects.

    Over-reliance on Automated Accessibility Overlays

    It might seem tempting to use automated accessibility overlays, especially during the hectic holiday season. These are often marketed as one-click solutions to make your website accessible. The Department of Justice has issued clear guidance that these solutions are inadequate in addressing web accessibility, and they may get you targeted with litigation.

    Why It Matters

    Automated accessibility overlays claim to fix all accessibility issues on a website, but they usually fail to address the root problems. Blind users are outspoken that they dislike these solutions as they tend to interfere with the assistive technologies they’re already comfortable with. We’ve also seen these solutions specifically called out in lawsuits as a reason for being targeted.

    How to Fix It

    The best way to ensure your site is accessible is by addressing the core issues in your code and design. Automated tools can help identify problems, but manual reviews and fixes are essential. Invest in manual audits and focus on meeting the WCAG guidelines through thoughtful design and coding practices.

    Here’s an example of using a reliable method instead of relying on an

    <!-- Instead of using an overlay for images, provide clear alt text -->
    <img src= "holiday-product.jpg" alt= "Red winter coat with a 30% off discount tag">

    Automated tools tend to use AI to label images and controls and often misrepresent content on the website, leading to a potentially overtly harmful experience.

    Conclusion

    As you gear up for holiday promotions, make sure accessibility is at the top of your checklist. By avoiding these common mistakes—insufficient alt text, poor color contrast, inaccessible navigation, missing captions, and over-reliance on automated tools—you’ll ensure that your website is welcoming and easy to use for everyone.

    Not only does improving web accessibility help you reach a wider audience, but it also protects your business from legal risks and ensures compliance with WCAG and ADA standards. Taking the time to implement these changes now will pay off during the holiday rush and beyond.

    If you’re unsure about the accessibility of your site, reach out to 216digital using the contact form below for a free evaluation.

    Bobby

    October 21, 2024
    How-to Guides, Legal Compliance
    holiday promotions, How-to, web development, Website Accessibility
  • Retail Accessibility: Avoiding Common Pitfalls

    The internet is overflowing with retail opportunities, but one crucial element often gets overlooked: accessibility. For online retailers, making your website accessible isn’t just about complying with legal requirements—it’s about expanding your customer base and delivering a better shopping experience for everyone. So, how can you ensure your online store is open to all shoppers and avoid common accessibility pitfalls? Let’s dive into the essentials.

    Why Accessibility Matters for Online Retailers

    Web accessibility means making sure everyone, including people with disabilities, can easily use and navigate your site. In the world., about 15% of the population lives with some form of disability. By ensuring your website is accessible, you’re tapping into a market with immense buying power—people with disabilities control over $6 trillion in spending globally!

    But beyond opening your business to a broader audience, accessibility is also about staying compliant with laws like the Americans with Disabilities Act (ADA). In 2023, 82% of ADA lawsuits were related to web accessibility issues in the retail industry, affecting both large and small businesses alike. If your website isn’t accessible, you’re not just missing out on customers—you could also be facing legal risks.

    The Web Accessibility Guidelines

    The Web Content Accessibility Guidelines (WCAG) are the foundation for creating an accessible website. These guidelines revolve around four main principles, often referred to as POUR:

    • Perceivable: Content must be presented in a way that all users can perceive, whether visually or audibly.
    • Operable: Your site should be fully navigable, whether users are using a mouse, keyboard, or assistive technologies.
    • Understandable: Your content should be easy to comprehend and navigate.
    • Robust: Your website should work well with a variety of assistive tools, like screen readers.

    For retailers, aiming for WCAG 2.1 Level AA compliance is a great starting point, and it’s the level referenced by most legal frameworks for web accessibility.

    Steps for Online Retailers to Improve Accessibility Right Now

    Improving your website’s accessibility might sound like a big task, but it’s more manageable than you think. Here are some quick and effective steps to make your site web accessible:

    Auditing Retail Sites for Accessibility Issues

    The first step is knowing where your site stands. Start with automated tools like Lighthouse or WAVE to flag common issues, such as missing image descriptions or poor color contrast. Then, dive deeper with manual testing, working with accessibility experts to uncover more subtle barriers, like challenges with forms or navigation.

    Make Visual Content Accessible

    People with visual impairments rely on alt text to understand images, so be sure to include detailed alt descriptions for all meaningful visuals. For example, instead of a vague description like “product,” use something more specific like “Blue ceramic coffee mug with a handle.” This simple change helps users with screen readers understand what’s being shown.

    Don’t forget about video content! WCAG guidelines require captions for pre-recorded audio in videos. Ensure that auto-generated captions, like those from YouTube, are accurate, and provide transcripts for podcasts to make all media accessible.

    <img src="coffee-mug.jpg" alt="Blue ceramic coffee mug with a handle">
    <video controls>
      <track kind="captions" src="captions_en.vtt" srclang="en" label="English">
    </video>

    Optimize Website Navigation and Structure

    Some users navigate your site without a mouse, relying solely on their keyboard. Make sure your site can be fully navigated using just a keyboard, with elements like menus, buttons, and forms accessible through “tab” key navigation. Also, ensure every interactive element has a visible focus indicator, like a border around buttons or links, so users can easily see where they are on the page.

    button:focus, a:focus {
      outline: 2px solid #ffcc00; /* Provides a visible focus indicator */
    }

    Improve Form Accessibility

    Checkout forms can be a stumbling block for accessibility, especially if they aren’t screen reader-friendly. Make sure all form fields have clear labels and that error messages don’t rely solely on color. For example, instead of just using a red outline to indicate a required field, include a text message like “This field is required” to make the error clear for all users.

    <form>
      <label for="email">Email:</label>
      <input type="email" id="email" name="email" required>
      <span class="error" role="alert">This field is required</span>
    </form>

    The Retail Shopping and Checkout Process

    Imagine trying to check out but not knowing where you are in the process—frustrating, right? Break your checkout process into clear, labeled steps and ensure it’s compatible with assistive technologies. Also, consider adding alternative payment methods like PayPal, Google Pay, or Apple Pay to improve usability for all customers.

    To meet WCAG SC 2.4.4 standards, you can use visual breadcrumbs or progress indicators to let users know where they are in the checkout process.

    <nav aria-label="Breadcrumb">
      <ol>
        <li><a href="/cart">Cart</a></li>
        <li><a href="/shipping">Shipping</a></li>
        <li aria-current="page">Payment</li>
      </ol>
    </nav>

    Implement ARIA Landmarks and Roles

    ARIA (Accessible Rich Internet Applications) landmarks and roles help assistive technologies identify key sections of your page. For instance, wrapping your site’s header in a role="banner" helps screen readers identify it as the main header, making it easier for users to navigate through your site.

    <header role="banner">
      <nav role="navigation">
        <ul>
          <li><a href="/home">Home</a></li>
          <li><a href="/products">Products</a></li>
        </ul>
      </nav>
    </header>

    Testing and Ongoing Monitoring for Retailers

    Web accessibility isn’t a one-time fix—it’s an ongoing process. Retail websites are constantly changing. Regular testing and monitoring are essential to ensuring that those updates or changes to your site don’t introduce new accessibility barriers. Tools like 216digital’s a11y.Radar can help you stay on top of accessibility issues with automated scans and detailed reports, making it easier to maintain a compliant and user-friendly website as new content is added.

    Partnering with Accessibility Experts

    If all of this sounds overwhelming, you don’t have to go it alone. Partnering with accessibility experts can fast-track your progress. Whether you need a thorough audit, code remediation, or ongoing support, companies like 216digital specialize in helping retail sites meet web accessibility standards. They can ensure your site is not only compliant but also delivers a seamless, enjoyable shopping experience for all users.

    Accessibility Overlays: A Quick Fix or a Long-Term Solution?

    You might have heard about accessibility overlays—tools that promise a quick fix for all your accessibility needs. While these overlays might sound tempting, they often fall short. Overlays can miss deeper, underlying issues with your website’s code and design, leaving you vulnerable to ADA lawsuits. In fact, 933 companies were sued last year after installing overlay solutions and many accessibility experts caution against relying on them as a long-term solution.

    Instead, focus on making meaningful changes to your website’s design and functionality. Overlays might be a temporary patch, but they shouldn’t replace a full accessibility strategy.

    Check Accessibility Off Your Shopping List

    By making your website accessible, you’ll not only increase your customer base but also create a better shopping experience for everyone. Accessibility is a journey, and it’s one worth taking. Follow the steps outlined above, test your site regularly, and don’t hesitate to partner with experts to ensure your site stays compliant and user-friendly.

    To help you get started on the right path, consider scheduling an ADA briefing with 216digital. Our team of experts can walk you through the latest accessibility guidelines, provide actionable insights, and show you how to ensure your site complies with ADA standards.

    Online shopping should be for everyone, so let’s make it happen together!  

    Greg McNeil

    October 16, 2024
    How-to Guides, Legal Compliance, WCAG Compliance
    Accessibility, ADA Compliance, ADA Website Compliance, ecommerce website, Retail, WCAG
  • Why ‘Click Here’ Hurts Your Website’s Accessibility

    If you’ve spent any time browsing the web, you’ve probably come across links like “click here” or “read more.” While these phrases seem simple enough, they can actually be confusing or even frustrating—especially for people using screen readers to navigate a site. That’s where descriptive link text comes in. It’s essential for making websites more accessible to everyone, including those with disabilities. So, let’s dive into why using meaningful link text is so important and how you can write it to improve both web accessibility and overall user experience.

    What is Descriptive Link Text?

    Descriptive link text is just what it sounds like—clickable text that clearly explains what the link is for. Instead of generic phrases like “click here” or “read more,” a good descriptive link gives enough context so users know exactly where the link will take them. This is a win for all users but especially important for people with disabilities who rely on screen readers to navigate the web.

    Imagine trying to navigate a website where every link says “click here.” For someone using a screen reader, that’s a frustrating experience because they have no clue where any of those links will lead. Descriptive link text fixes that by making sure all users, no matter how they access the web, have a clear, easy-to-understand experience.

    Why “Click Here” and “Read More” Are Problematic

    Using generic phrases like “click here” or “read more” might seem harmless, but they can actually create confusion. When someone using a screen reader encounters a page full of links that all say “click here,” they’re left with no context about where the links go or what they do. It’s like being handed a bunch of blank signposts with no labels.

    Let’s take a look at an example:

    • Bad Link: Click here to read more.
    • Better Link: Learn more about our services.

    In the second example, the user knows exactly what they’re clicking on, which makes the experience more apparent and more helpful, especially for people using screen readers.

    Empty Links and Their Impact on Accessibility

    Another issue when it comes to web accessibility is empty links. An empty link is one that has no text or meaningful content for a screen reader to announce. For people using screen readers, these links are useless—they navigate to them but get no information about what they do. And for those using keyboard navigation, empty links can be frustrating roadblocks.

    To avoid this, always make sure your links contain text, or if you’re using an image as a link, ensure there’s alternative text (alt text) that clearly describes what the link does.

    How Descriptive Link Text Boosts Accessibility

    One of the best things about the web is its potential to be accessible to everyone. But if we don’t put some thought into how we design and label things like links, we end up excluding a lot of people. Descriptive link text makes websites more accessible and improves the overall user experience in a few key ways:

    • Clarity for Screen Reader Users: Screen readers read links out loud. If the link text is too vague, it isn’t very clear. Descriptive text helps users know exactly what to expect before they click.
    • Better Navigation: Clear, simple language helps everyone, especially users with cognitive disabilities or learning differences, by reducing the mental effort needed to figure out what a link does.
    • Faster Browsing: Descriptive links let users quickly scan a page and understand where each link will take them. This makes it easier for everyone to find what they’re looking for without guessing.

    WCAG Guidelines for Descriptive Links

    The Web Content Accessibility Guidelines (WCAG) provide a set of best practices for making the web usable by everyone. According to WCAG SC 2.4.4 Link Purpose, each link should make its purpose clear, either from the link text itself or from its surrounding context.

    Here are a few essential tips from WCAG on how to write compelling link text:

    • Be Concise and Relevant: Your link text should be short but informative. Don’t go overboard, but include enough detail so users know where they’re headed.
      • Example: Instead of “click here for more,” try “Learn more about accessible landmarks.“
    • Skip the Redundancies: You don’t need to add words like “link” or “website” to your link text. Screen readers already announce that it’s a link, so saying “click here to visit the website” is unnecessary. Just say, “Visit our website.“
    • Avoid Empty Links: Every link should have meaningful content. Empty links are confusing and serve no functional purpose for users navigating with keyboards or screen readers.

    Examples of Effective and Ineffective Link Text

    • Ineffective Link Text:
      • Click here
      • Read more
      • Learn more
      • Here
    • Effective Link Text:
      • Download the 2024 Annual Report
      • Explore our upcoming events.
      • Read more about creating accessible web links.

    In these examples, the goal is to make it crystal clear where the link will take the user, leaving no room for confusion.

    Best Practices for Writing Descriptive Link Text

    • Think About Context: Consider what the user needs to know about the link’s destination. This is especially important for screen reader users who may jump between links without reading the surrounding text. Make sure the link text alone provides enough information.
    • Keep It Short and Sweet: Your link text should be informative but not too long. For example, “Contact Us for Support” is much clearer than “Click here if you need to get in touch with our support team.“
    • Use Natural Phrasing: Don’t feel like you always need to add a “click here” to your sentence. Sometimes, the best link text is already part of your content. For instance, instead of “click here to learn more about our programs,” use the “learn more about our programs” link.
    • Avoid URLs as Links: Long URLs are difficult for screen readers to interpret, especially if they contain numbers and special characters. Instead of linking a URL directly, use descriptive text like “Visit 216digital’s a11y.Radar Monitoring Page.”
    • Alt Text for Image Links: If an image serves as a link, make sure the alt text conveys the purpose of the link. For example, if a shopping cart icon leads to the cart page, use alt text like “View Cart” rather than just “Cart.”

    Linking It All Together

    Incorporating descriptive link text is a small change that can have a significant impact on your website’s web accessibility. By ditching generic phrases, using clear and concise language, and following WCAG guidelines, you’ll make your site more navigable for everyone—especially users who rely on screen readers.

    Creating an inclusive web experience doesn’t have to be complicated, but it does take attention to detail. If you’re unsure whether your website’s accessibility measures, including your link text, are up to standard, it might be time to seek expert advice. At 216digital, we offer ADA briefings that help you identify areas for improvement and ensure your site meets accessibility requirements.

    Take the next step towards a more accessible web presence and schedule a complimentary ADA briefing with 216digital today. We’re here to guide you through the process and help you create a site that’s welcoming and usable for everyone.

    Greg McNeil

    October 14, 2024
    How-to Guides, Legal Compliance, WCAG Compliance
    Accessibility, Alt text, descriptive link text, WCAG, WCAG Compliance, Web Accessibility
  • Digital Accessibility Lawsuit Targets Contractors

    The recent case of Bryan Bashin vs. ReserveCalifornia.com has opened the door to a new type of accessibility lawsuit. It’s not just website owners being held accountable—government contractors who build and maintain websites are now in the spotlight too.

    This case is important for developers, designers, and accessibility experts working on government websites, as it sets a strong example of what can happen when accessibility isn’t prioritized. More importantly, it serves as a wake-up call for businesses and contractors alike to understand that accessibility is not just an option but a legal necessity. Failure to comply with accessibility standards could result in costly lawsuits and reputational damage.

    In today’s digital world, ensuring that everyone, including people with disabilities, can use your website is not just good practice—it’s the law.

    Case Overview: A New Direction

    Bryan Bashin, who is visually impaired, sued ReserveCalifornia.com, claiming the site was inaccessible to people with disabilities. This violated both the Americans with Disabilities Act (ADA) and California’s Unruh Civil Rights Act. What made this case different? Bashin didn’t go after the website owner, California State Parks—he targeted the contractors who created and managed the site.

    ReserveCalifornia.com is a key website for booking campsites and other outdoor activities in state parks. Because it wasn’t fully accessible, users who depend on assistive technologies, like screen readers, had trouble navigating it. By focusing on the developers, Bashin’s lawsuit sends a clear message: if you’re responsible for public websites, you must meet digital accessibility standards—or you could face legal action.

    The Laws: Unruh Act and ADA Title II

    This case relies on two important laws: California’s Unruh Civil Rights Act and the updated ADA Title II rules for government websites.

    • Unruh Act: This California law allows people with disabilities to sue organizations that don’t make their services accessible. Bashin used this law to seek damages, which gave him additional legal options beyond the federal ADA.
    • ADA Title II: This part of the ADA focuses on making sure government services, programs, and activities—including websites—are accessible. Recent updates have strengthened these rules, making it clear that public websites must meet accessibility standards. Bashin’s lawsuit shows how these laws are evolving, putting contractors in the spotlight.

    What It Means for Web Developers: Widespread Impacts

    While this lawsuit happened in California, its effects could reach across the country. The Unruh Act may be specific to California, but ADA Title II applies nationwide. Developers working on public sector projects need to understand that ignoring accessibility could lead to serious risks, especially as more governments crack down on non-compliance.

    Developers and contractors are expected to follow the Web Content Accessibility Guidelines (WCAG), the international standard for digital accessibility. Not meeting these standards puts them at risk of lawsuits like Bashin’s, and the $2 million settlement in this case shows that courts are willing to hold developers accountable.

    What is the WCAG?

    WCAG is the go-to guide for making websites accessible to people with disabilities, such as those who are blind, deaf, or have cognitive challenges. It focuses on making content:

    • Perceivable: Users must be able to experience content, whether through text, images, or other formats like captions.
    • Operable: Users should be able to navigate the site with different tools like a mouse, keyboard, or voice commands.
    • Understandable: The site’s information and operations should be clear and easy to use.
    • Robust: The site should work with current and future assistive technologies.

    For developers, following WCAG not only ensures legal compliance but also opens websites to a wider audience and improves overall user experience.

    Why WCAG Matters

    You might ask yourself, “Why should I care about WCAG compliance?” First and foremost, it helps make your website accessible to a wider audience. If your site isn’t usable for people with disabilities, you could be missing out on potential customers. In a digital age where online shopping and information-seeking are essential, excluding anyone based on accessibility is not just unfair—it’s bad for business.

    Moreover, the Bashin case shows that failing to meet accessibility standards can lead to legal consequences. As more digital accessibility lawsuits arise, companies that don’t prioritize compliance could face significant financial penalties. By adhering to WCAG guidelines, you protect yourself from legal issues and show that you care about your users.

    Best Practices for Developers and Digital Accessibility Experts

    Bashin’s case is a reminder that developers and consultants must make digital accessibility a priority from the start. It’s no longer enough to just create a good-looking or functional website—it has to work for everyone, including people with disabilities.

    Here’s what developers and business owners should focus on:

    • WCAG Knowledge: Work with developers who understand WCAG standards and have experience making accessible sites.
    • Conduct a Website Audit: Regularly audit your website for accessibility issues. There are tools available online that can help you identify problems, such as missing alt text for images or issues with color contrast.
    • Implement Ongoing Training: Train your staff, especially those involved in website management and content creation, about digital accessibility.
    • Ongoing Monitoring: Accessibility isn’t a one-time job. Websites need regular testing to stay compliant. This proactive approach helps prevent potential violations before they lead to costly lawsuits.
    • Stay Informed and Up-to-Date: Digital accessibility standards and regulations change over time. Make any necessary updates to your website to remain compliant.

    The Bigger Picture: Nationwide Repercussions

    The Bryan Bashin vs. ReserveCalifornia.com case is a strong reminder for developers everywhere: accessibility is no longer optional. By holding government contractors accountable for digital accessibility violations, this case sets a powerful precedent. Developers and accessibility experts must be proactive and make sure all public-facing websites—especially those for government services—comply with WCAG and other accessibility standards. The future of digital accessibility enforcement is here, and developers need to stay ahead to avoid costly legal risks.


    To avoid the risks of costly legal action and make sure your website is accessible to everyone, now is the time to act. Find out if your website is ADA compliant today by scheduling a 15-minute complimentary website audit and consultation with our experts at 216digital. We can help determine if your site is at risk of a lawsuit and provide fast, effective ADA compliance solutions so you can focus on what matters most: running your business.

    Greg McNeil

    October 10, 2024
    Legal Compliance
    Accessibility, ADA Compliance, ADA Website Compliance, Bryan Bashin vs. ReserveCalifornia.com, Unruh Civil Rights Act, web developers
  • Web Accessibility Overlays: A False Sense of Security

    As a website owner, you likely recognize the growing need to make your site accessible to everyone, including individuals with disabilities. With increased emphasis on ADA compliance, you may have encountered web accessibility overlays—automated tools that offer quick-fix solutions.

    While they might seem like a convenient solution, these overlays can create significant pitfalls that could leave you vulnerable to legal risks and fail to provide true accessibility.

    In this article, we’ll explore why relying on overlays could lead to a false sense of security and why a more comprehensive approach to addressing web accessibility is critical.

    What Are Web Accessibility Overlays?

    Overlays are software solutions that scan websites for barriers and apply superficial fixes with minimal user involvement. Their promise is simple: They claim to help your site meet Web Content Accessibility Guidelines (WCAG) and ADA standards, making your content more accessible.

    At first glance, overlays seem appealing, with features like adjustable text sizes and color contrast options. However, they fail to deliver a truly inclusive online experience. While some surface level issues can be address, deeper accessibility barriers are frequently ignored or mishandled.

    The Illusion of ADA Compliance

    The biggest misconceptions surrounding web accessibility overlays is that they will guarantee ADA compliance. The harsh reality is that ADA compliance is multifaceted and cannot be achieved through automated fixes alone.

    True web accessibility goes far beyond superficial adjustments. It requires a detailed understanding of the diverse barriers people with disabilities face when interacting with digital content. Overlays, which only focus on cosmetic changes, leave significant gaps in compliance, neglecting critical components of accessibility. Unfortunately, this gives many website owners the false impression that their sites are fully compliant when, in fact, they still fall short in several critical areas.

    Automated Fixes Miss Critical Issues

    While overlays can identify some common accessibility problems, they rely too heavily on automation, often leading to overlooking essential elements.  

    Here are some areas where they typically fall short:

    • Semantic HTML: Using HTML elements correctly ensures that people using screen readers and other assistive technologies can understand your website’s content. Overlays cannot address issues like improper heading structures or missing ARIA labels.
    • Alt Text for Images: Descriptive alt text provides essential context for visually impaired users. Automated tools can only see that they are missing. They cannot interpret the meaning or purpose of the image to generate meaningful descriptions.
    • Keyboard Navigation: Many users are unable to use a mouse, requiring them to navigate a website through the use of a keyboard. To make a website accessible through keyboard navigations corrections must be made on a code level. As discussed above, overlays can only make superficial changes, and cannot make changes directly to the code.

    By relying on these automated solutions, you may inadvertently overlook crucial aspects of web accessibility, leaving your site vulnerable to an ADA lawsuit.

    The False Sense of Security

    The use of web accessibility overlays can foster complacency, leading to a false sense of security. The mere presence of an overlay might make you believe your site is fully accessible, yet significant barriers may still be lurking beneath the surface.

    This illusion is particularly dangerous. If your overlay doesn’t meet full accessibility standards, your website remains non-compliant with the ADA and other state regulations. As a result, businesses that thought they were protecting themselves with an overlay can find themselves in court, dealing with expensive settlements and lasting damage to their reputation.

    In fact, 20% of all accessibility-related lawsuits this year targeted websites using these so-called “accessibility solutions,” and that number continues to grow. Relying solely on overlays not only fails to address critical accessibility issues but also opens the door to legal risks.

    True web accessibility is not a one-time fix; it requires ongoing attention, regular audits, and user feedback. Overlays might provide a band-aid solution, but they can prevent you from developing a genuine commitment to accessibility, which is vital for both compliance and user experience.

    A Human-Centered Approach to Web Accessibility

    To meet the needs of all users and ensure ADA compliance, businesses must adopt a comprehensive, human-centered approach to web accessibility. Here are a few critical steps to achieving this:

    • Understand Web Accessibility Guidelines: WCAG is a set of standards designed to make web content more accessible. Familiarize yourself with these guidelines to understand what needs to be done. They cover aspects like text readability, alternative text for images, and keyboard navigation.
    • Conduct a Website Audit: Regularly audit your website for accessibility issues. There are tools available online that can help you identify problems, such as missing alt text for images or issues with color contrast. Consulting with a specialist firm like 216digital to conduct a thorough audit can also be a wise investment.
    • Engage with Users: Real feedback from individuals with disabilities is invaluable. Understanding their experiences navigating your site will provide critical insights for meaningful improvements.
    • Train Your Team: Train your staff, especially those involved in website management and content creation, about web accessibility principles and best practices. This knowledge is essential to maintaining an accessible online experience over time.
    • Ongoing Monitoring: Compliance is not a one-time task. This proactive approach helps prevent potential violations before they lead to costly lawsuits.

    By prioritizing a human-centered approach, you can create an online environment that truly serves all users rather than settling for a quick-fix solution that only gives the illusion of compliance.

    216digital’s Approach to Web Accessibility

    At 216digital, we understand that genuine web accessibility requires more than just automated tools. Our comprehensive, human-centered approach goes beyond quick fixes to provide long-lasting solutions that focus on risk mitigation and compliance with WCAG 2.1/2.2 AA standards. 

    Through  a11y.Radar, we offer ongoing monitoring, ensuring your website remains compliant and accessible to all users. By emphasizing thorough auditing and remediation services, we help businesses not only meet legal requirements but also tap into the underserved market of individuals with disabilities.

    Our approach is built around long-term accessibility, protecting your business from potential lawsuits and positioning you to serve a broader, more inclusive audience better.

    Conclusion

    Web accessibility overlays may seem like an easy answer, but they often fall short of delivering the accessibility experience your users need and the compliance your business requires. Relying solely on these tools could leave your website open to legal risks and frustrate users with disabilities who still encounter barriers on your site.

    At 216digital, we’re here to help you navigate the complexities of ADA compliance with a human-centered approach. Schedule an ADA briefing with our team today to ensure your website is fully accessible, compliant, and welcoming to every visitor. Don’t settle for quick fixes—invest in meaningful accessibility that makes a real difference.

    Greg McNeil

    October 8, 2024
    Legal Compliance, WCAG Compliance
    ADA Compliance, ADA Lawsuit, Overlay widgets, Overlays, Web Accessibility
  • The Hidden Accessibility Barriers in Popular Plugins

    Plugins offer an easy way for blogs or e-commerce websites to add helpful functionality like newsletter signups, product filters, or bundles to their website without paying costly development fees. But while these popular plugins promise seamless user experiences, many hide serious accessibility barriers that can exclude people with disabilities from entirely using your site.

    Even if you follow accessibility guidelines and best practices throughout your site, plugin vendors may not do the same, which causes your website to become non-conformant despite your excellent work. Understanding how plugins can impact web accessibility is essential to maintaining an accessible website, even if you install them to accomplish simple tasks.

    Let’s explore the common accessibility pitfalls of plugins and what you can do to avoid introducing accessibility errors on your website when utilizing them.

    What Are Plugins, and Why Do They Matter for Accessibility?

    Plugins are pre-built software modules you can add to your website to perform specific tasks. Whether improving SEO, adding an image slider, or embedding a social media feed, plugins extend your website’s features without needing custom development.

    However, plugins don’t always come with accessibility in mind. Many developers focus on functionality and design, overlooking essential elements that make their plugins usable for all, especially people with disabilities who use assistive technology.

    Plugins become a problem when they introduce barriers that prevent users from navigating or interacting with your site. Even if the rest of your website is built according to accessibility standards, a plugin can break that accessibility with one update or feature.

    Common Accessibility Barriers in Popular Plugins

    So, what does an inaccessible plugin look like? These issues can be subtle and not immediately apparent to someone without accessibility experience. Here are a few common barriers often found in popular plugins:

    1. Poor Keyboard Navigation

    Many users with mobility impairments or visual disabilities rely on a keyboard to navigate a website. A plugin that lacks proper keyboard navigation can make it impossible for these users to interact with your site. For example, sliders, pop-up forms, or dropdown menus in some plugins may trap keyboard users, preventing them from moving between page elements using the Tab key.

    One primary culprit is the “tabindex” attribute, which allows developers to control the order in which interactive elements are focused. Some plugins misuse this attribute, causing the focus to jump around illogically, making navigation difficult or impossible.

    2. Lack of ARIA Landmarks and Roles

    ARIA (Accessible Rich Internet Applications) roles and landmarks are essential for users who navigate using screen readers. These assistive technologies rely on ARIA to communicate the structure and purpose of elements on the page. When plugins don’t correctly implement ARIA roles—such as mislabeling buttons or failing to designate headings—it becomes harder for users to understand the content.

    For instance, a popular image gallery plugin may not correctly assign ARIA roles to buttons for navigating between photos. To a screen reader user, those buttons may be entirely invisible, making the gallery feature inaccessible.

    3. Inconsistent Focus Indicators

    Focus indicators are visual cues that help users see which element on the page is currently selected, such as a glowing outline around a button. These indicators are crucial for keyboard users, but many plugins either remove or don’t include focus indicators at all, leaving users stranded without knowing where they are on the page.

    A typical example is sliders that fail to highlight which slide is active or forms where the submit button doesn’t show any visual indication of focus.

    4. Non-Semantic HTML and Improper Heading Structure

    Semantic HTML, which uses elements like <nav>, <article>, and proper headings (<h1>, <h2>), helps assistive technologies interpret content. Unfortunately, some plugins rely on non-semantic HTML—like using <div> or <span> elements for interactive content or headings—which screen readers may not understand as intended.

    For example, a form plugin that uses <div> for form fields instead of <label> elements makes it difficult for screen readers to identify the label of each field, leading to confusion for the user.

    5. Missing or Incorrect Alt Text

    Images used in plugins, especially image-heavy ones like sliders or galleries, often lack alternative text. Alt text is essential for visually impaired users who rely on screen readers to describe the content of images. Without it, users are left in the dark about the purpose of the images in the plugin.

    Some plugins automatically generate alt text, but they may do so incorrectly—using file names or generic labels like “image123,” which provide no meaningful information to users.

    WCAG Guidelines: How Plugins Often Fall Short

    The Web Content Accessibility Guidelines (WCAG) are the gold standard when it comes to web accessibility, but many plugins fail to meet these guidelines. Here’s how:

    Perceivable

    Plugins often fail to provide text alternatives for non-text content, like images and icons. This makes it impossible for screen readers to convey the content to users who are blind or have low vision.

    Operable

    As mentioned, poor keyboard navigation is a major issue with plugins. Any plugin that doesn’t allow users to operate all of its functions via keyboard alone falls short of this WCAG principle.

    Understandable

    Plugins that misuse ARIA roles or use non-semantic HTML can create confusion for users of assistive technology, making the content harder to understand.

    Robust

    Many plugins don’t integrate well with assistive technologies. A plugin that only works in one browser or on certain screen readers is not robust enough to be considered accessible.

    How to Handle Inaccessible Plugins

    So, what should you do if you suspect that a plugin on your site is inaccessible? Here are a few practical tips:

    1. Evaluate the Plugin for Accessibility Barriers

    First, you’ll want to check to see if the plugin vendor has any posted policies or guidance regarding web accessibility. After that, you can install the plugin in a test environment and use standard evaluation tools such as WAVE or Google Lighthouse to determine if any issues appear.

    2. Consider Replacing the Plugin with an Accessible Alternative

    If you find that a plugin is inaccessible, consider replacing it with a more accessible competitor. For example, there are many form, slider, and gallery plugins designed with accessibility in mind. These often prioritize compliance with WCAG guidelines, making it easier for your site to remain accessible.

    3. Reach Out to Plugin Developers

    If you’re committed to a specific plugin that has accessibility issues, don’t hesitate to reach out to the developer. Politely inform them of the barriers their plugin creates and ask if they have plans to address accessibility in future updates. Many developers are open to feedback and may not be aware of the issues until they are brought to their attention.

    4. Use ARIA Landmarks and Roles to Improve Plugin Accessibility

    If you have some technical knowledge, you can manually add ARIA roles or improve the HTML structure of the plugin elements. While this is a more advanced solution, it can be effective in making a plugin more accessible.

    5. Test Regularly with Accessibility Tools

    Tools like WAVE or Lighthouse can help you assess the accessibility of your entire site, including any plugins you’ve added. Regular testing can ensure that your site remains accessible as plugins update and evolve over time.

    Plugins Are Powerful—But Watch Out for Hidden Barriers

    Plugins are a fantastic way to improve your website’s functionality, but they can also introduce hidden accessibility barriers if you’re not careful. As a website owner or developer, it’s your responsibility to ensure that every part of your site, including third-party plugins, is accessible to all users.

    By being proactive—whether through testing, replacing, or communicating with developers—you can avoid the common pitfalls of inaccessible plugins and keep your site welcoming and functional for everyone. Remember, it’s not just about compliance; it’s about creating an inclusive experience that ensures all users can access and interact with your content.

    So, next time you’re about to install that flashy new plugin, pause for a second and ask yourself: Is this accessible?

    Ready to get started? Schedule a personalized ADA briefing with 216digital and get expert guidance tailored to your needs.

    Greg McNeil

    October 7, 2024
    How-to Guides, Legal Compliance
    ADA Compliance, plugins, Web Accessibility, web development, website plugins
  • ADA Compliance vs Web Accessibility: What is the Difference

    As more businesses move online, understanding web accessibility and ADA compliance becomes crucial. These terms are often used interchangeably but represent different aspects of making a website user-friendly for everyone, including individuals with disabilities. Knowing the distinction between web accessibility and ADA compliance can help protect your business from lawsuits while ensuring your site provides an inclusive experience.

    In this article, we’ll examine the definitions of web accessibility and ADA compliance, explore their differences, discuss the legal risks associated with non-compliance, and explain how businesses can proactively address accessibility issues using services like 216digital’s Phase 1 remediation.

    What is Web Accessibility?

    Web accessibility involves designing and developing websites, tools, and technologies to ensure they are usable by people with a wide range of abilities and disabilities. This includes individuals who have visual, auditory, physical, speech, cognitive, or neurological disabilities. The goal of web accessibility is to ensure that everyone, regardless of their disability, can perceive, understand, navigate, and interact with the web.

    Web Content Accessibility Guidelines (WCAG)

    The primary standard for web accessibility is the Web Content Accessibility Guidelines (WCAG), created by the World Wide Web Consortium (W3C). The latest version, WCAG 2.1, provides a comprehensive set of guidelines aimed at making web content accessible. These guidelines are organized around four core principles, commonly known as POUR:

    • Perceivable: Information and user interface components must be presented in ways that all users can perceive.
    • Operable: User interface components and navigation must be operable for everyone, including those using assistive technologies like screen readers.
    • Understandable: Information and the operation of the user interface must be understandable.
    • Robust: Content must be strong enough to work with a wide range of technologies, including those used by people with disabilities.

    While WCAG provides the framework for web accessibility, compliance with it is generally voluntary unless law or legal action requires otherwise.

    What is ADA Compliance?

    ADA compliance refers to meeting the requirements set forth by the Americans with Disabilities Act (ADA), which was enacted in 1990. The ADA mandates that businesses, public services, and other organizations provide equal access to individuals with disabilities. Although the ADA was passed before the internet became mainstream, courts have increasingly ruled that websites are considered public accommodation places, meaning they must be accessible to people with disabilities.

    ADA compliance, specifically in the context of websites, refers to whether your site meets the legal requirements of the ADA as interpreted by courts and the Department of Justice (DOJ). No official legal mandate states that WCAG 2.1 must be followed to achieve ADA compliance, but it is widely accepted that adhering to WCAG is the best way to meet ADA requirements.

    How Does It Differ From Web Accessibility?

    • Web accessibility is the broader concept of ensuring that people of all abilities can use websites.
    • ADA compliance is a legal requirement for businesses in the U.S. to provide equal access to individuals with disabilities, which includes making websites accessible.

    Web accessibility is a best practice, while ADA compliance is a legal standard. Following web accessibility guidelines, like WCAG 2.1, helps businesses meet the requirements of ADA compliance, but the two terms are not identical.

    Is It Possible to Achieve and Maintain Full WCAG 2.1 Compliance?

    Yes, but it’s not always easy, especially for bigger, more complex websites. WCAG 2.1 covers a lot of areas—like how text shows up, how media is handled, how forms work, and more. As technology and user needs evolve, keeping up with compliance is an ongoing effort. Regular testing, monitoring, and updates are needed to ensure the site meets the latest accessibility standards.

    If you’re worried about protecting yourself from ADA lawsuits, aiming for full WCAG 2.1 compliance is a smart move. It can help reduce your legal risks, but it is only legally required in some cases. Courts have ruled in favor of plaintiffs in ADA lawsuits when websites were not accessible, even if they didn’t meet every single WCAG criterion.

    Does Your Website Need to Be Fully Web Accessible to Protect Your Business?

    To protect your business from ADA compliance lawsuits, it’s crucial to address the most common accessibility barriers, even if full WCAG 2.1 compliance is not achieved. Many companies focus on making the most essential parts of their website accessible, such as navigation, forms, and checkout processes. This approach can reduce the risk of a lawsuit while allowing businesses to improve their site’s accessibility gradually.

    It’s also worth noting that courts have yet to require businesses to meet every WCAG 2.1 guideline to comply with the ADA. However, companies that demonstrate they are actively working to make their sites more accessible—by following best practices and improving critical accessibility issues—are generally better positioned to defend against lawsuits.

    The Risk of ADA Compliance Lawsuits

    ADA compliance lawsuits have skyrocketed in recent years, especially against businesses with inaccessible websites. These lawsuits can be costly, both in terms of financial settlements and reputational damage. Predatory law firms have begun targeting businesses—tiny and mid-sized companies—that have websites with accessibility issues. These firms often file “copycat” lawsuits, sometimes targeting hundreds of companies with nearly identical complaints.

    The financial risk is real. Businesses are often forced to settle the lawsuit or pay legal fees, which can run into tens or even hundreds of thousands of dollars. In addition, businesses may also have to invest in website remediation services to fix accessibility issues.

    How Predatory Law Firms Target Websites

    Predatory law firms often conduct automated scans of websites to identify accessibility violations, such as missing alt text, poor contrast ratios, or non-functional navigation for keyboard-only users. Once they identify these issues, they send demand letters or file lawsuits, typically hoping that the business will settle quickly to avoid costly litigation.

    Unfortunately, even well-meaning businesses that are working on improving accessibility can be targeted. This is why it’s essential to address website accessibility proactively rather than waiting for a lawsuit to happen.

    Is Full WCAG 2.1 Compliance Required to Mitigate Lawsuits?

    While full WCAG 2.1 compliance is not explicitly required to avoid lawsuits, businesses should aim to make their websites as accessible as possible. The more barriers that are removed, the less likely it is that a website will be the target of a lawsuit.

    In most cases, addressing key accessibility issues—such as ensuring all images have alt text, providing video captions, and making the site navigable by keyboard—will significantly reduce the risk of a lawsuit.

    Protect Your Business with 216digital

    To help businesses avoid the pitfalls of non-compliance, 216digital offers Phase 1 remediation services designed to address the most critical accessibility issues quickly. These services focus on mitigating the risk of ADA lawsuits by resolving common accessibility barriers that predatory law firms often target. By implementing these initial fixes, businesses can start protecting themselves while working toward broader web accessibility goals.

    In addition to Phase 1 remediation, 216digital offers ongoing monitoring and testing services to ensure your site remains accessible over time. With a proactive approach, businesses can avoid costly lawsuits and provide a better user experience for all visitors.

    Ready to Make Your Website ADA Compliant?

    As the digital landscape continues to evolve, ensuring your website is both accessible and ADA-compliant is more important than ever. While full WCAG 2.1 compliance may not always be required, addressing key accessibility issues can significantly reduce your risk of lawsuits and enhance the user experience for all visitors.

    Take the next step toward protecting your business and making your website more inclusive. Schedule a personalized ADA compliance briefing with 216digital today. Our team can guide you through Phase 1 remediation and ongoing strategies to keep your site accessible and compliant. 

    Greg McNeil

    October 3, 2024
    Legal Compliance, WCAG Compliance
    Accessibility, ADA Compliance, ADA Website Compliance, WCAG, WCAG Compliance, Website Accessibility
  • Avoid ADA Lawsuits: Lessons from Big Companies

    Over the past few years, many well-known companies have faced lawsuits under Title III of the Americans with Disabilities Act (ADA) for failing to make their websites accessible. From retail giants like Nike and Target to entertainment brands like Beyoncé’s Parkwood Entertainment, these companies have all encountered legal challenges due to non-compliant websites.

    These cases provide an important lesson for website owners and content creators: web accessibility is not just a risk for big corporations but especially those running small businesses. Small companies are quickly becoming targets for Title III lawsuits as well. But by proactively making your website accessible, you can avoid legal trouble and enjoy several long-term benefits.

    Let’s examine some of the big companies that have been sued over website accessibility and how small businesses can protect themselves.

    1. Winn-Dixie: The ADA Case that Set the Standard

    Winn-Dixie was one of the first major brands to face a Title III lawsuit over website accessibility. In 2017, a blind customer sued the grocery chain because its website wasn’t compatible with screen reader software. The court ruled in favor of the plaintiff, marking a major precedent for future cases. This case highlighted how even websites that aren’t strictly e-commerce-based can be required to meet ADA standards.

    2. Domino’s Pizza: The Fight Over Online Ordering

    Domino’s Pizza was sued because a blind customer couldn’t use their website and app to order food. The case gained national attention when it reached the U.S. Supreme Court in 2019. Domino’s argued that the ADA didn’t apply to websites, but the Supreme Court declined to hear the case, leaving the lower court ruling in favor of the plaintiff. The lesson? ADA Title III applies to digital spaces just as much as physical locations.

    3. Nike: Accessibility in the Retail Space

    Nike was sued for having an inaccessible website that prevented visually impaired users from making purchases. The company quickly settled the case and implemented changes, demonstrating that the cost of fighting a lawsuit can be much higher than simply fixing accessibility issues upfront.

    4. Blue Apron: The Subscription Service Challenge

    Blue Apron, a meal-kit delivery service, faced a lawsuit when a blind customer was unable to sign up because the website didn’t work with screen readers. Blue Apron’s case showed that even digital-first businesses are vulnerable to accessibility claims.

    5. KitchenAid: The Importance of Universal Access

    KitchenAid, known for its appliances, was sued after a visually impaired user couldn’t navigate their website to access product information. This case underscores that accessibility isn’t just about e-commerce; it also includes providing equal access to all the content and information on your website.

    6. Fox News Network: ADA in Online Media

    Even media companies aren’t immune. Fox News faced a lawsuit for not making its website accessible to people with visual impairments. News outlets, entertainment brands, and other content-heavy websites should ensure that their pages are fully compliant with ADA guidelines.

    7. Beyoncé’s Parkwood Entertainment: Entertainment and Inclusivity

    In 2019, a visually impaired woman sued Beyoncé’s Parkwood Entertainment, claiming that her website wasn’t accessible with screen readers. This case shows that artists, musicians, and entertainment companies are also responsible for making sure their digital content is inclusive for all.

    8. H&R Block: Financial Services

    Tax preparation giant H&R Block was sued over their inaccessible website. The company settled by agreeing to make its site accessible and compliant with the Web Content Accessibility Guidelines (WCAG). This case demonstrates that financial services are held to the same standards as retail or entertainment when it comes to web accessibility.

    9. Burger King: Fast Food, Fast Accessibility Fixes

    Burger King was sued when a visually impaired customer couldn’t use its website to place an order. Like many companies, Burger King settled the case by agreeing to fix its accessibility issues rather than dragging out a lengthy court battle.

    10. Target: A Retailer Making ADA a Priority

    Target was sued in 2006 and eventually settled, becoming one of the first major retailers to make their website fully accessible. Their case set an early example that many other companies have followed.

    How Small Businesses Are Becoming Targets for ADA Lawsuits

    While these cases involved large companies, small businesses are increasingly being targeted by ADA Title III lawsuits. This shift is largely due to the rise in website accessibility lawsuits in general, which have grown significantly in recent years. Small businesses are often seen as easier targets because they may lack the resources to fight a lawsuit or may be unaware of their legal obligations under the ADA.

    The reality is that no business is too small to be sued over website accessibility. This means that whether you’re running a local boutique or a nationwide e-commerce store, you need to be proactive about making your site accessible.

    The Benefits of Web Accessibility

    Beyond avoiding lawsuits, making your website accessible offers several benefits:

    • Broaden Your Audience: An accessible website can be used by people with disabilities, which represents a significant portion of the population. By making your site accessible, you’re opening your business to more customers.
    • Improved SEO: Many accessibility improvements, like proper alt text for images, can also boost your search engine ranking.
    • Enhanced User Experience: Accessibility improvements often go hand-in-hand with usability improvements, making your site easier to navigate for all users.
    • Positive Brand Reputation: By demonstrating that your business values inclusivity, you can enhance your brand’s reputation and build customer loyalty.

    How to Calculate Your Return on Investment (ROI)

    When thinking about the cost of making your website accessible, it’s important to consider the return on investment (ROI). While the upfront cost of an accessibility audit or remediation might seem high, the long-term benefits far outweigh the cost of a lawsuit.

    To calculate your ROI for ADA Compliance, consider:

    1. Initial Accessibility Audit: This will tell you where your site currently stands and what changes need to be made. The cost will vary depending on the size and complexity of your website.
    2. Implementation Costs: These are the costs associated with fixing the accessibility issues identified in the audit. Again, this can vary but should be viewed as an investment in future-proofing your business.
    3. Avoided Lawsuits: The cost of fighting a Title III lawsuit can be substantial, both financially and reputationally. By being proactive, you can avoid these costs altogether.
    4. Expanded Customer Base: More accessible websites mean more potential customers. The boost in revenue can quickly outweigh the costs of compliance.

    How Being Proactive with Web Accessibility Offers an Incredible ROI

    The companies mentioned earlier learned the hard way that it’s always better to be proactive rather than reactive when it comes to website accessibility. Fixing accessibility issues after a lawsuit is filed is much more expensive than addressing them upfront. Not to mention, proactively making your website accessible can help you avoid the reputational damage that often accompanies ADA lawsuits.

    Protect Your Online Business

    Don’t wait for a lawsuit to take action on web accessibility. Get ahead of potential risks by ensuring your site is compliant now. At 216digital, we’re here to help you navigate the complexities of ADA compliance and safeguard your business. Schedule a personalized ADA briefing with us today to understand how you can protect your online presence, avoid costly lawsuits, and expand your customer base through an accessible website. Let’s future-proof your business together—schedule your ADA briefing now!

    Greg McNeil

    September 27, 2024
    Legal Compliance
    ADA, ADA Compliance, ADA Lawsuit, ADA Title II, web accessibility lawsuits
Previous Page
1 … 3 4 5 6 7 … 10
Next Page
216digital Scanning Tool

Audit Your Website for Free

Find Out if Your Website is WCAG & ADA Compliant













    216digital Logo

    Our team is full of expert professionals in Web Accessibility Remediation, eCommerce Design & Development, and Marketing – ready to help you reach your goals and thrive in a competitive marketplace. 

    216 Digital, Inc. BBB Business Review

    Get in Touch

    2208 E Enterprise Pkwy
    Twinsburg, OH 44087
    216.505.4400
    info@216digital.com

    Support

    Support Desk
    Acceptable Use Policy
    Accessibility Policy
    Privacy Policy

    Web Accessibility

    Settlement & Risk Mitigation
    WCAG 2.1/2.2 AA Compliance
    Monitoring Service by a11y.Radar

    Development & Marketing

    eCommerce Development
    PPC Marketing
    Professional SEO

    About

    About Us
    Contact

    Copyright 2024 216digital. All Rights Reserved.