216digital.
Web Accessibility

ADA Risk Mitigation
Prevent and Respond to ADA Lawsuits

WCAG & Section 508
Conform with Local and International Requirements

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

  • Common Web Accessibility Pitfalls That Invite ADA Lawsuits

    The Americans with Disabilities Act (ADA) requires businesses to make their websites accessible to everyone, including people with disabilities. When websites fail to meet accessibility standards, they risk facing lawsuits. In recent years, ADA lawsuits related to digital accessibility have surged, with businesses large and small getting sued for non-compliance. But what exactly are the most common issues that lead to these lawsuits?

    This article will highlight the most common web accessibility barriers that lead to ADA lawsuits and provide real-world examples of lawsuits related to these issues. 

    1. Missing Alt Text

    Alt text, or alternative text, provides a written description of an image on a webpage. Screen readers, which visually impaired users use to navigate the internet, read this description aloud.Without alt text, users with visual impairments have no way of knowing what an image represents.

    For example, if a website has an image of a product for sale, the alt text might say, “Red shoe, size 8.” Without this text, screen reader users won’t know what the image shows, making it difficult to interact with the website.

    Missing or incorrect alt text is one of the most common reasons for ADA lawsuits. Many businesses overlook this small but important step, leaving essential images without descriptions.

    WCAG 2.1 Guideline: 1.1.1 – Non-text Content

    All non-text content, such as images, must have a text alternative that serves the same purpose.

    Example ADA Lawsuit: Fox News Network LLC

    Fox News Network LLC was sued because its website didn’t provide proper alt text for many images. Luc Burbon, a visually impaired user, relied on screen readers to browse the internet. When trying to navigate Fox News’ website, he encountered images without alt text, leaving him unable to understand key content. The court agreed with Burbon, emphasizing that websites must be accessible to everyone, including people with disabilities.

    2. Non-Descriptive Interactive Elements

    Interactive elements, like buttons and links, are crucial for navigating a website. However, if these elements aren’t appropriately labeled, users who rely on screen readers won’t know what a button or link does. This leads to confusion, frustration, and can make essential parts of the website inaccessible to users with disabilities.

    For example, a button labeled “Click Here” without explaining what it does will leave screen reader users guessing, especially if there’s more than one on a page. Adding contextually relevant content to the visual or accessible label, such as “Click here to learn more about our coffee” will differentiate the element while also giving users additional context.

    WCAG 2.1 Guideline: 4.1.2 – Name, Role, Value

    Interactive elements should have clear labels that explain their purpose.

    Example ADA Lawsuit: NIKE, Inc.

    Maria Mendizabal filed a class-action lawsuit against Nike, claiming that the website had many links that were either redundant or completely empty. Users with visual impairments couldn’t understand the purpose of these links, making it challenging to navigate the site. This lawsuit demonstrates the importance of appropriately labeling interactive elements so everyone can understand them.

    3. Lack of Keyboard Navigation

    Many users with disabilities rely on keyboards to navigate websites, especially those who can’t use a mouse. If a website doesn’t allow for keyboard-only navigation, or if drop-down menus can’t be accessed with a keyboard, it becomes unusable for people with mobility impairments.

    For example, if a menu only opens when hovered over with a mouse, someone using only a keyboard won’t be able to open it, blocking their access to critical sections of the site.

    WCAG 2.1 Guideline: 2.1.1 – Keyboard

    All functionality should be accessible using a keyboard.

    Example ADA Lawsuit: Parkwood Entertainment LLC

    In 2019, a lawsuit accused Parkwood Entertainment because Beyoncé’s official website, Beyonce.com, did not provide accessibility for users relying on screen readers.. Mary Conner, the visually impaired plaintiff, couldn’t navigate the drop-down menus using her keyboard. This prevented her from accessing important content and services, leading to a lawsuit.

    4. Inaccessible Forms

    Forms are commonly used on websites—for everything from signing up for newsletters to making purchases. However, forms that are difficult for people with disabilities to fill out can create barriers. Missing labels on form fields, unclear error messages, or forms that don’t work with keyboard navigation are common accessibility issues that lead to lawsuits.

    For instance, if a form field asks for a phone number but doesn’t have a proper label, a screen reader user won’t know what to enter. Or, if an error message isn’t clear about what went wrong, visually impaired users won’t be able to correct their mistakes.

    WCAG 2.1 Guideline: 3.3.2 – Labels or Instructions

    Ensure input fields have proper labels and instructions so users know what information is required.

    Example ADA Lawsuit: H&R Block Lawsuit

    A notable example of this issue is the lawsuit involving the National Federation of the Blind and H&R Block. In this case, visually impaired users discovered that H&R Block’s website did not correctly label the forms. When these users tried to input their contact information or create an account, they struggled because the screen readers failed to indicate what information they needed or where to enter it.

    5.  Inaccessible Pop-Ups and Modals

    Pop-ups and modals (dialog boxes that appear on top of a page) are common features on websites for everything from newsletter sign-ups to product promotions. However, if they are not designed with accessibility in mind, they can disrupt the user’s experience.

    Pop-ups cause confusion if they appear without warning or if users can’t close them using a keyboard. Users relying on screen readers or assistive devices may not even know that a pop-up has appeared, making it impossible for them to continue interacting with the page.

    WCAG 2.1 Guideline: 1.3.1 – Info and Relationships

    When new content, like a pop-up, appears on the screen, announce it to the user and explain how it connects to the rest of the website.

    Example ADA Lawsuit: Five Guys Enterprises

    In a lawsuit against Five Guys, a visually impaired customer couldn’t complete an online order because an inaccessible pop-up appeared when trying to add fries to her cart. Her screen reader didn’t recognize the pop-up, making it impossible for her to finish the purchase. This case highlights the importance of making pop-ups accessible to everyone.

    How to Avoid ADA Lawsuits

    Avoiding ADA lawsuits starts with a proactive approach to web accessibility. Making your website accessible is not only a legal obligation but also an opportunity to provide a better user experience for all visitors, regardless of ability. Here are key steps you can take to avoid common accessibility pitfalls:

    1. Understand Web Accessibility Guidelines: The Web Content Accessibility Guidelines (WCAG) are 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.
    2. 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.
    3. Implement Ongoing Training: Train your staff, especially those involved in website management and content creation, about web accessibility. This helps create a culture of inclusivity and ensures that accessibility remains a priority.
    4. Stay Informed and Up-to-Date: Web accessibility standards and best practices can evolve over time. Stay iCompliance is not a one-time task. 216digital’s a11y.Radar service provides ongoing monitoring. It detects any new accessibility issues that may arise over time. This proactive approach helps prevent potential violations before they lead to costly lawsuits.”

    Conclusion

    Making sure your website is ADA-compliant is not just about avoiding lawsuits—it’s about ensuring that everyone, no matter their abilities, can access and enjoy your content. With the rise in ADA lawsuits, it’s more important than ever to take a proactive approach to web accessibility. Whether it’s fixing missing alt text or ensuring keyboard navigation, addressing these common issues can save your business time and money in the long run.

    If you’re unsure where to start or need help maintaining compliance, 216digital is here to help. Through our years of experience analyzing these cases, we understand how ADA non-compliance lawsuit firms identify their targets. We can help you protect your business from these risks. At 216digital, we will develop a strategy to integrate WCAG 2.1 compliance into your development roadmap. This will allow you to focus on other tasks on your to-do list.

    So don’t wait any longer; find out where you stand by scheduling a complementary ADA strategy briefing today.

    Greg McNeil

    September 25, 2024
    Legal Compliance, WCAG Compliance
    Accessibility, ADA Compliance, ADA Lawsuit, ADA Website Compliance, digital accessibility, WCAG, WCAG Compliance, Web Accessibility
  • Does WCAG Apply to Mobile Apps?

    Does WCAG Apply to Mobile Apps?

    If you’re a website owner or app developer, you’ve probably heard about WCAG (Web Content Accessibility Guidelines). But when it comes to mobile apps, you might wonder: Does WCAG apply here too? The short answer is yes! WCAG isn’t just for websites—it extends to mobile apps as well. Let’s dive into why WCAG is important for mobile apps, what it means for accessibility, and how to ensure your app meets these guidelines.

    What is WCAG, and Why Does it Matter?

    WCAG, developed by the World Wide Web Consortium (W3C), provides guidelines to make web content more accessible for everyone, particularly people with disabilities. These guidelines help ensure that users with visual, auditory, motor, or cognitive impairments can interact with websites—and, as it turns out, mobile apps—with ease.

    When WCAG was first introduced, it focused on websites, but as technology evolved, so did our understanding of accessibility. With the rise of mobile apps, it’s clear that WCAG also applies to them. Whether you’re building an e-commerce app, a social media platform, or a mobile version of your website, adhering to WCAG is crucial for staying compliant with accessibility standards and avoiding legal issues.

    Does WCAG Apply to Mobile Apps?

    Yes, WCAG applies to mobile apps. While WCAG wasn’t initially designed with mobile apps in mind, its principles are just as relevant in the mobile space. The guidelines are technology-agnostic, meaning they can be applied to any digital content, including mobile apps.

    Mobile apps, like websites, must be accessible to everyone, and the same types of barriers that exist on websites—like unreadable text, poor color contrast, or unclear navigation—can also affect mobile apps. That’s why WCAG compliance is essential for mobile app development. Not only does it help create a better user experience for people with disabilities, but it also ensures that your app is legally compliant.

    The Growing Importance of Mobile Accessibility

    Mobile devices have become an essential part of our daily lives, with more people accessing information and services via apps than ever before. This makes it even more important to ensure that mobile apps are accessible. In fact, a significant portion of users rely on mobile devices as their primary way of accessing the internet, including people with disabilities. Ensuring your app meets accessibility standards isn’t just good practice; it’s a way to reach a broader audience.

    Failing to consider accessibility in mobile apps can result in lost users, bad reviews, and even legal consequences. There have been several lawsuits filed in the U.S. where businesses were held accountable for not providing accessible mobile experiences. By following WCAG, you reduce the risk of these issues and open your app to a more diverse audience.

    How WCAG Applies to Mobile Apps

    WCAG guidelines revolve around four core principles: Perceivable, Operable, Understandable, and Robust (often abbreviated as POUR). These principles are crucial when designing both websites and mobile apps.

    1. Perceivable: Information and user interface components must be presented in ways that users can perceive. For mobile apps, this means ensuring that text is readable, images are described through alt text, and media elements are captioned or have transcripts available.
    2. Operable: Users must be able to interact with all interface elements using various input methods, such as screen readers or voice commands. In mobile apps, this could include ensuring that buttons are large enough to be tapped easily and that the app works with assistive technologies like voice control or switch access.
    3. Understandable: The interface must be easy to understand and navigate. This is especially important for mobile apps, where the small screen size can make navigation more difficult. Make sure that users can easily understand how to use your app, with clear instructions and intuitive design elements.
    4. Robust: The app must be compatible with current and future technologies. This includes ensuring that your app works well across different devices, platforms, and with assistive technologies.

    Mobile App Accessibility Checklist

    Now that we’ve established that WCAG does apply to mobile apps, how do you ensure that your app is compliant? Here’s a mobile app accessibility checklist to get you started:

    Text and Readability

    1. Text Resizing: Make sure your text can get bigger without messing up the layout. This is part of WCAG 1.4.4 (Resize Text), which means users should be able to increase text size up to 200% without losing content or functionality.
    2. High Contrast: Use colors that are easy to read against each other, like dark text on a light background. This helps everyone, including those with vision problems. WCAG 1.4.3 (Contrast Ratio) suggests a contrast ratio of at least 4.5:1 for normal text and 3:1 for larger text.
    3. Alternative Text: Always include a description for images, icons, and buttons. This helps screen readers explain what’s on the screen to people who can’t see the images. This follows WCAG 1.1.1 (Non-Text Content).

    Keyboard and Assistive Technology Compatibility

    1. Keyboard Accessibility: Make sure all parts of your app can be used with just a keyboard. This is covered by WCAG 2.1.1 (Keyboard), ensuring that users who can’t use a mouse can still navigate your app.
    2. Assistive Technology: Check that your app works well with tools like screen readers, voice controls, and switches. This is important for WCAG 4.1.2 (Name, Role, Value), which ensures that assistive technologies can interpret user interface elements.
    3. Screen Reader Testing: Test your app with popular screen readers like VoiceOver (for iPhones) and TalkBack (for Android phones) to make sure they work well together.

    Navigation and Interaction

    1. Consistent Navigation: Keep navigation easy and the same across different screens. This is part of WCAG 3.2.3 (Consistent Navigation), which helps users get around without getting lost.
    2. Touch Targets: Make sure buttons and icons are big enough for everyone to tap easily. WCAG 2.5.5 (Target Size) recommends making touch targets at least 44×44 pixels.
    3. Simple Gestures: Avoid using complex gestures like multi-finger swipes without offering simpler options. WCAG 2.5.1 (Pointer Gestures) suggests providing alternatives for complex gestures.

    Audio and Video Content

    1. Captions: Add captions to all your videos so people who can’t hear well can still understand what’s being said. This is part of WCAG 1.2.2 (Captions (Pre-recorded)).
    2. Transcripts: Include transcripts for audio content and podcasts. This is a text version of the audio that helps people who are deaf or hard of hearing, covered by WCAG 1.2.1 (Audio-only and Video-only (Prerecorded)).
    3. Playback Controls: Let users control the audio playback, including volume and speed, and make sure they can pause or stop it. This aligns with WCAG 1.4.2 (Audio Control).

    Color and Contrast

    1. Color Contrast: Ensure there’s a strong contrast between text and background colors to help users with color blindness or vision problems. Aim for a contrast ratio of at least 4.5:1 for regular text and 3:1 for large text, as recommended by WCAG 1.4.3 (Contrast Ratio).
    2. Avoid Color Alone: Don’t use color as the only way to show important info. For example, if you use red to highlight an error, also include text to explain it. This follows WCAG 1.4.1 (Use of Color).

    Error Identification and Recovery

    1. Error Highlighting: Clearly show when something goes wrong, like a missing form field, and give tips on how to fix it. This is part of WCAG 3.3.1 (Error Identification) and 3.3.3 (Error Suggestion).
    2. Clear Error Messages: Make sure error messages are easy to understand, not full of technical jargon. This helps users fix mistakes, as outlined in WCAG 3.3.3 (Error Suggestion).
    3. Easy Recovery: Allow users to fix mistakes without starting over. For example, let them undo actions or correct errors easily. This is covered by WCAG 3.3.4 (Error Prevention (Legal, Financial, Data)).

    Test with Real Users

    1. User Testing: Even if you follow all the WCAG guidelines, it’s crucial to test your app with real users who use assistive technologies. Their feedback is invaluable for ensuring your app is truly accessible.
    2. Keep Improving: Use feedback from user testing to make your app better. Keep updating and checking your app to make sure it stays accessible as you add new features.

    The Benefits of Accessible Mobile Apps

    Making your mobile app accessible is not just about complying with regulations—it’s about providing a better user experience for everyone. Here are some key benefits:

    • Wider Audience: Accessible apps reach a broader audience, including users with disabilities who may not be able to use apps that don’t meet WCAG guidelines.
    • Improved Usability: Many accessibility improvements, like clearer navigation and larger touch targets, make your app easier to use for all users, not just those with disabilities.
    • Avoiding Legal Risk: Compliance with WCAG helps you stay on the right side of web compliance laws, reducing the risk of lawsuits related to accessibility.
    • Better Reputation: Being proactive about accessibility can enhance your brand’s reputation and show your commitment to inclusivity.

    Final Thoughts

    In the digital age, mobile apps are a key part of how we interact with the world, and making sure they’re accessible is crucial for providing an inclusive experience. WCAG does apply to mobile apps, and by following the guidelines, you can create apps that are usable by everyone, regardless of their abilities. Whether you’re just starting out or you’re improving an existing app, using the mobile app accessibility checklist can help ensure that your app is WCAG-compliant and ready to serve all users.

    Remember, accessibility isn’t just about following the law—it’s about doing the right thing for your users and your business. To learn more about becoming accessible and staying compliant, schedule an ADA briefing with 216digital today. We’re here to help you take the next steps!

    Greg McNeil

    August 27, 2024
    WCAG Compliance
    digital accessibility, mobile apps, WCAG, WCAG Compliance, Web Accessibility
  • Insights from WebAIM’s Screen Reader Survey #10

    Insights from WebAIM’s Screen Reader Survey #10

    In today’s digital age, ensuring that your website is accessible to everyone is more important than ever. WebAIM’s Screen Reader Survey #10 offers valuable insights into how people with disabilities use screen readers, which can help you make your website more accessible. If you’re an IT director, company owner, or anyone involved in managing a website, understanding these takeaways can help you improve your site’s digital accessibility and ensure it meets standards like Web Content Accessibility Guidelines (WCAG).

    Targeted Demographic: Who Uses Screen Readers?

    The WebAIM Screen Reader Survey #10 highlights a diverse group of people who use screen readers. These users come from various backgrounds and have different needs, but they all rely on screen readers to access content online. Knowing your audience is vital to making your website accessible. Here is a breakdown of who these users are:

    1. People with Visual Impairments: This is the largest group of screen reader users, with 76.6% of respondents being visually impaired. They might have complete blindness or low vision that prevents them from reading text on a screen. Screen readers convert text into spoken words for these individuals, allowing them to navigate and understand web content.
    2. People with Learning Disabilities: Some users with learning disabilities find screen readers helpful. They might have difficulty processing written text or need assistance with comprehension. Screen readers can help by reading text aloud and breaking it down into more manageable parts.
    3. Older Adults: As people age, they may experience vision loss or other difficulties that make screen reading challenging. Older adults may use screen readers to compensate for reduced vision or cognitive changes that affect their ability to interact with digital content.
    4. People with Physical Disabilities: Some users with physical disabilities that affect their ability to use a mouse or keyboard may rely on screen readers to navigate websites. They might use adaptive technology to interact with their devices, making screen readers an essential tool for accessing web content.

    Targeted Age: Understanding the Age Range

    The survey also reveals insights into the age range of screen reader users. While screen readers are crucial for users of all ages, certain age groups use them more frequently:

    1. Younger Users: Younger users with disabilities are increasingly tech-savvy and may use screen readers alongside other assistive technologies. They often expect modern websites to be accessible and are quick to notice when accessibility features are lacking.
    2. Middle-Aged Users: This group may include people who have acquired disabilities later in life or who are managing long-term conditions. They often need screen readers to access work-related or personal online content.
    3. Older Adults: As mentioned earlier, older adults may use screen readers due to age-related vision loss or other issues. This demographic is growing, making it essential for websites to cater to their needs.

    Understanding the age range of screen reader users can help you design your website in a way that accommodates different life stages and technological preferences.

    Disabilities and Disability Types: Types of Disabilities Addressed

    Screen readers are used by individuals with a range of disabilities. Let’s take a closer look at the types of disabilities that screen readers help address:

    1. Visual Impairments: This includes both complete blindness and low vision. Screen readers convert on-screen text into speech, making content accessible to users who cannot see it. For users with low vision, screen readers can be combined with other assistive technologies, such as screen magnifiers.
    2. Cognitive Disabilities: Users with cognitive disabilities might struggle with memory, attention, or processing information. Screen readers can assist by reading text aloud, which can make it easier for these users to understand and retain information.
    3. Motor Disabilities: Individuals with motor disabilities might have difficulty using a keyboard or mouse. Screen readers can help by allowing users to navigate websites using voice commands or other adaptive technologies.
    4. Hearing Impairments: While screen readers are primarily used by people with visual impairments, some individuals with hearing impairments might also use them. For example, screen readers can be used in conjunction with other assistive technologies to provide a complete experience for users with multiple disabilities.

    The Importance of Digital Accessibility

    Understanding these demographics and disability types underscores the importance of digital accessibility. Web accessibility ensures that your website can be used by everyone, regardless of their abilities. This is not just about compliance with standards like WCAG; it is about creating an inclusive digital environment.

    This is why digital accessibility should be a priority for your business:

    1. Legal Compliance: Many countries, including the United States, have laws that require websites to be accessible. Failing to meet these requirements can result in legal action, which can be costly and damaging to your reputation.
    2. Broader Audience: By making your website accessible, you open it up to a wider audience. This includes not only people with disabilities but also those who use assistive technologies or have temporary impairments.
    3. Better User Experience: Accessible websites often provide a better overall user experience. Features that help screen reader users can also benefit other users, such as more straightforward navigation and more readable content.
    4. Enhanced Brand Image: Companies that prioritize accessibility are seen as more inclusive and socially responsible. This can improve your brand’s image and help build a positive reputation.

    Making Your Website Accessible

    To ensure your website meets digital accessibility standards, follow these best practices:

    1. Adhere to WCAG Guidelines: WCAG is the gold standard for web accessibility. They provide specific recommendations for making web content more accessible. Familiarize yourself with these guidelines and implement them on your site.
    2. Test with Screen Readers: Regularly test your website with screen readers to identify any accessibility issues. This can help you ensure that your content is being read correctly and that users can navigate your site effectively.
    3. Seek Feedback: Get feedback from actual screen reader users. Their insights can be invaluable in identifying and addressing accessibility issues that you might not have considered.
    4. Stay Updated: Digital accessibility is an evolving field. Keep up with the latest trends and updates to ensure your website remains compliant and accessible.

    Wrapping Up

    WebAIM’s Screen Reader Survey #10 provides crucial insights into who uses screen readers and how they interact with web content. By understanding the demographics, age ranges, and disability types of screen reader users, you can make informed decisions about improving your website’s digital accessibility. Adhering to WCAG guidelines and incorporating accessibility best practices will not only help you comply with legal requirements but also enhance the user experience for everyone.

    For IT directors and company owners, prioritizing web accessibility is a smart move that benefits both your users and your business. By taking these insights to heart, you can create a more inclusive and effective online presence.

    If you’d like to talk further about your web accessibility initiative, Schedule a Complimentary ADA Strategy Briefing with the experts at 216digital. We will help you take the steps towards web accessibility on your terms by developing a strategy to integrate WCAG 2.1 compliance into your development roadmap.

    Greg McNeil

    August 6, 2024
    WCAG Compliance
    digital accessibility, screen readers, Web Accessibility, WebAIM’s Screen Reader Survey, WebAIM’s Screen Reader Survey #10, Website Accessibility
  • Screen Readers 101: Making Your Site Accessible

    Screen Readers 101: Making Your Site Accessible

    In today’s digital age, making your website accessible to everyone is more important than ever. One critical aspect of digital accessibility is ensuring that your site is compatible with screen readers. But what exactly are screen readers, and why is it so important to make sure your website works well with them? In this blog post, we’ll dive into what screen readers are, who uses them, how they browse the Internet, and how you can test your website to ensure it’s screen reader-friendly.

    What are Screen Readers and Who Uses Them?

    Let’s start with the basics. A screen reader is a piece of software that reads aloud the text displayed on a computer or mobile device screen. It’s a vital tool for people who are blind or have severe visual impairments. However, screen readers are also used by individuals with other disabilities, such as those with learning disabilities or certain cognitive impairments, who may find it easier to listen to content rather than read it.

    So, who exactly uses screen readers? The answer is billions of people around the world. In the United States alone, there are an estimated 12 million people over 40 with a visual disability. For these individuals, screen readers are essential for accessing the Internet, working, and communicating. Without screen readers, many websites would be entirely inaccessible to them.

    How Do Screen Reader Users Browse the Internet?

    Browsing the Internet with a screen reader is a completely different experience than browsing with sight. For starters, screen reader users don’t navigate web pages visually—they rely on audio cues and keyboard commands to get around.

    Here’s a simplified version of how it works:

    1. Screen Reader Starts Reading: When a screen reader user opens a webpage, the screen reader begins reading the content from top to bottom. It reads out the text, describes images (if alt text is provided), and announces the presence of links, buttons, and other interactive elements.
    2. Keyboard Navigation: Instead of using a mouse, screen reader users navigate through the website using keyboard commands. They might use the Tab key to move between links, headings, and form fields, or shortcuts to jump to specific sections of the page, such as the main content or a list of links.
    3. Listening for Context: Screen reader users often listen to the content at a much faster speed than normal. They also rely heavily on headings, landmarks, and other structural elements to understand the layout and flow of the page. For example, a user might jump from heading to heading to quickly scan the page and find the information they need.
    4. Interacting with Elements: When a user encounters a form field, button, or link, the screen reader announces what it is and sometimes gives instructions on how to interact with it. For example, if there’s a “Submit” button, the screen reader might say, “Button: Submit. Press Enter to activate.”

    For screen reader users, a well-structured, accessible website is key to having a smooth and efficient browsing experience. But if a website is not properly optimized for screen readers, it can become frustrating, confusing, or even impossible to use.

    Why is Screen Reader Testing Important?

    Now that you have a basic understanding of what screen readers are and how they’re used, let’s talk about why testing your website for screen reader compatibility is so important.

    Ensuring Digital Accessibility

    First and foremost, screen reader testing is crucial for ensuring digital accessibility. As a website owner, developer, or content creator, it’s your responsibility to make sure that your website is accessible to everyone, including people with disabilities. Screen reader testing helps you identify and fix issues that could prevent people who rely on these tools from accessing your content.

    Complying with Legal Requirements

    In the United States, websites are required by law to be accessible to people with disabilities. The Americans with Disabilities Act (ADA) Title II and Section 508 of the Rehabilitation Act are two key laws that apply to web accessibility. If your website is not accessible, you could be at risk of legal action, which could result in costly fines and damage to your reputation. By performing screen reader testing, you can ensure that your website complies with these laws.

    Improving User Experience

    Accessibility isn’t just about legal compliance—it’s also about providing a better user experience for everyone. When your website is accessible to screen reader users, it’s also likely to be more user-friendly for other visitors. For example, clear headings, logical page structure, and well-labeled buttons benefit all users, not just those with disabilities.

    Reaching a Wider Audience

    By making your website accessible to screen reader users, you’re opening it up to a wider audience. This can lead to more traffic, better SEO, and ultimately, more success for your business. Accessibility should be seen as an investment in your website’s future, not just a legal obligation.

    What Are the Different Approaches to Accessibility Testing?

    There are several different approaches to accessibility testing, each with its own advantages and disadvantages. To ensure that your website is fully accessible, it’s important to use a combination of these methods.

    Automated Testing

    Automated testing tools can scan your website for common accessibility issues, such as missing alt text, insufficient color contrast, and incorrect HTML structure. These tools are fast and can cover a lot of ground in a short amount of time. However, they can’t catch every issue—especially those related to screen reader compatibility.

    Some popular automated accessibility testing tools include:

    • WAVE: A web accessibility evaluation tool that highlights accessibility issues directly on your webpage.
    • Lighthouse: A tool built into Chrome that can audit your website for performance, SEO, and accessibility issues.

    While automated testing is a great starting point, it should never be the only method you use. Automated testing covers only 30-40% of accessibility guidelines and can miss more subtle or complex problems that require human judgment.

    Manual Testing

    Manual testing involves a human tester navigating your website and checking for accessibility issues. This approach is essential for catching issues that automated tools might miss, such as how well your website works with a screen reader. Manual testing can be more time-consuming and requires a deeper understanding of web accessibility, but it provides a more accurate picture of your website’s accessibility.

    During manual testing, you should:

    • Check Keyboard Navigation: Ensure that all interactive elements, such as links, buttons, and form fields, can be accessed and activated using only the keyboard.
    • Test with a Screen Reader: Use a screen reader to navigate your website and listen to how the content is announced. Pay attention to whether the screen reader correctly identifies headings, lists, buttons, and other elements.

    User Testing

    User testing involves real users with disabilities testing your website and providing feedback on their experience. This is the most effective way to identify and fix accessibility issues, as it provides insight into how your website works in the real world.

    To conduct user testing:

    • Recruit Testers: Find users who rely on screen readers and other assistive technologies to test your website. You can reach out to local organizations, online communities, or professional networks to find willing participants.
    • Observe and Take Notes: Watch how the testers interact with your website and take note of any issues they encounter. Pay attention to their feedback and use it to make improvements.
    • Iterate and Improve: After making changes based on user feedback, test again to ensure that the issues have been resolved.

    User testing can be more expensive and time-consuming than other methods, but it provides the most valuable insights.

    Not sure what form of accessibility testing is right for you? Check out our article, Choosing the Right Accessibility Audit for Your Goals, for more information.

    How to Perform Screen Reader Testing

    Screen reader testing is a crucial part of manual and user testing. Here’s a step-by-step guide to performing screen reader testing on your website.

    Choose Your Screen Readers

    There are several different screen readers available, each with its own unique features and quirks. The most commonly used screen readers in the United States are:

    • NVDA (NonVisual Desktop Access): A free and open-source screen reader for Windows.
    • JAWS (Job Access With Speech): A popular screen reader for Windows, often used in workplaces.
    • VoiceOver: The built-in screen reader for MacOS and iOS devices.
    • TalkBack: The built-in screen reader for Android devices.

    To ensure that your website is accessible to the widest audience possible, it’s important to test with more than one screen reader.

    Familiarize Yourself with Screen Reader Commands

    Screen readers are controlled through a series of keyboard commands. Before you start testing, take some time to familiarize yourself with the basic commands for the screen reader you’re using. Most screen readers have a “practice mode” where you can learn and try out different commands.

    For example, in NVDA, you can press Ctrl + Alt + N to start the screen reader, use the Tab key to move through links and buttons, and press H to jump between headings.

    Navigate Your Website

    Start by opening your website with the screen reader turned on. Listen to how the screen reader announces the content, and use keyboard commands to navigate through the site. Pay attention to the following:

    • Headings: Are they announced correctly? Do they provide a clear structure for the page?
    • Links and Buttons: Are they labeled correctly? Do they make sense out of context?
    • Forms: Are the form fields and labels announced clearly? Is it easy to fill out the form using only the keyboard?

    Identify and Fix Issues

    As you navigate your website, take note of any issues you encounter. For example, if the screen reader doesn’t announce a button’s label, it may be missing an aria-label attribute. If a heading is skipped, it might be due to incorrect HTML markup.

    Once you’ve identified the issues, go back and fix them in your website’s code. Then, test again to ensure that the problem has been resolved.

    Test on Different Devices

    Screen reader behavior can vary depending on the device and browser being used. After testing on your primary device, try testing on different devices and browsers to ensure a consistent experience for all users.

    Conclusion

    In today’s world, making your website accessible to everyone isn’t just a nice-to-have—it’s a must-do. Ensuring your site works smoothly with screen readers is a big part of that. By taking the time to test and optimize your website for screen readers, you’re not only complying with legal requirements but also creating a better experience for all users. Plus, you’re opening the doors to a wider audience, which is always good for business.

    If you’re ready to take the next step in making your website truly accessible, why not schedule a complimentary ADA Strategy Briefing with 216digital? We’re here to help you navigate the ins and outs of digital accessibility and ensure your site is welcoming to everyone. Let’s make the web a better place, one website at a time.

    Greg McNeil

    July 31, 2024
    WCAG Compliance
    assistive technology, digital accessibility, screen readers, Web Accessibility, web development, Website Accessibility
  • What Are The Most Accessible Shopify Themes?

    What Are The Most Accessible Shopify Themes?

    Hey there, Shopify store owners, developers, and content creators! If you’re reading this, having a stunning online store is critical to attracting customers. But have you ever thought about making your store accessible to everyone, including people with disabilities? In today’s digital age, digital accessibility is crucial and more than just a buzzword. It’s about ensuring everyone can enjoy your site, no matter their abilities. Let’s dive into accessible Shopify themes and why they matter.

    Understanding Digital Accessibility

    Digital accessibility means designing websites and digital tools so everyone, including people with disabilities, can use them. Disabilities can be visual, auditory, physical, speech, cognitive, or neurological. When your site is accessible, you’re not just following best practices but also reaching a broader audience, enhancing your SEO, and showing you care about all your visitors.

    Why Accessibility Matters for Shopify Stores

    Shopify is one of the best e-commerce platforms for creating beautiful online stores. But beauty isn’t everything. Accessibility matters because:

    1. Inclusivity: Making your site accessible ensures everyone can use it, including those with disabilities. This increases your potential customer base.
    2. Legal Compliance: In the US, websites must comply with the Americans with Disabilities Act (ADA). Not following these guidelines can lead to lawsuits.
    3. SEO Benefits: Accessible sites are often better optimized for search engines, meaning better rankings and more traffic.
    4. Better User Experience: An accessible site is usually more user-friendly, keeping customers returning.

    What Makes a Shopify Theme Accessible?

    So, what should you look for in an accessible Shopify theme? Here are some key features:

    1. Keyboard Navigation: Users should be able to perform actions on your site using just a keyboard.
    2. Screen Reader Compatibility: Your site should work well with screen readers, which helps visually impaired users navigate the web.
    3. Text Alternatives: All images should have alt text so screen readers can describe them to users.
    4. Color Contrast: Text should have enough contrast with the background to be easily readable.
    5. Resizing Text: Users should be able to zoom and resize text without breaking your site’s layout.
    6. Clear Labels and Instructions: Forms and buttons should be clearly labeled so users know what they’re for.

    Top Accessible Shopify Themes Compatible with Online Store 2.0

    Now, let’s get into some of the most accessible Shopify themes compatible with Online Store 2.0. These themes are designed with digital accessibility in mind, ensuring your store is usable for everyone.

    Dawn

    Dawn is Shopify’s flagship theme for Online Store 2.0 and is built with accessibility in mind.

    • Keyboard Navigation: Dawn is fully navigable via keyboard, making it accessible for users who can’t use a mouse.
    • Screen Reader Support: The theme is compatible with screen readers, ensuring visually impaired users can access all content.
    • High Contrast: Dawn offers excellent contrast between text and background, which helps users with low vision.

    Craft

    Craft is perfect for stores with a focus on aesthetics and usability.

    • Text Alternatives: Every image in Craft can have alt text, making it accessible for screen readers.
    • Flexible Design: The theme’s layout adjusts well when text is resized, ensuring it remains readable.
    • Clear Instructions: Forms and interactive elements in Craft are clearly labeled.

    Sense

    Sense is a clean and modern theme designed for ease of use and accessibility.

    • High Contrast Mode: Sense offers a high-contrast color scheme, improving readability for low-vision users.
    • Accessible Forms: Forms are well-labeled and easy to use, ensuring everyone can complete purchases without hassle.
    • Keyboard-Friendly: Like the others, Sense is designed to work well with keyboard navigation.

    Crave

    Crave is a stylish theme that combines modern design with robust accessibility features.

    • Responsive Design: Crave’s responsive design ensures it looks great and works well on all devices, which is crucial for accessibility.
    • Alt Text: All images can have alt text, which is essential for screen reader users.
    • Clear Navigation: The navigation is straightforward to use, making it accessible to everyone.

    Refresh

    Refresh is ideal for stores that want a clean, modern look without compromising on accessibility.

    • Keyboard Navigation: The theme supports full keyboard navigation, ensuring users with disabilities can easily browse.
    • High Contrast: Refresh uses high contrast in its design, improving readability.
    • Screen Reader Friendly: It’s built to work seamlessly with screen readers.

    Tips for Enhancing Accessibility on Your Shopify Store

    Choosing an accessible theme is just the first step. Here are some additional tips to make your Shopify store even more accessible:

    1. Add Alt Text to Images: Every image on your site should have alternative text. This action helps screen reader users understand what’s on your site.
    2. Use Descriptive Links: Instead of “click here,” use descriptive text like “view our latest collection.”
    3. Ensure Text Readability: Use large, clear fonts and high-contrast colors.
    4. Test Your Site: Regularly check your site with the WAVE Web Accessibility Evaluation Tool for accessibility issues.
    5. Provide Keyboard Shortcuts: Offer keyboard shortcuts for common actions to make navigation easier.
    6. Accessible Forms: Make sure forms are easy to use and clearly labeled.
    7. Regular Updates: Keep your site and theme updated to fix any accessibility issues.

    Conclusion

    Digital accessibility isn’t just about ticking a box; it’s about creating an inclusive and user-friendly experience for all your visitors. Choosing an accessible Shopify theme like Dawn, Craft, Sense, Crave, or Refresh is a great start.

    Remember, an accessible site broadens your customer base, boosts your SEO, and helps you comply with legal requirements. So, take the time to invest in digital accessibility—it’s worth it!

    Starting your web accessibility journey on Shopify has never been easier with 216digital by your side. Schedule a complimentary ADA Strategy Briefing with our experts to craft a tailored plan for integrating WCAG 2.1 compliance into your development roadmap. We’re here to guide you every step of the way, ensuring that your online store meets accessibility standards while you focus on growing your business.

    Happy selling, and here’s to a more inclusive web!

    Greg McNeil

    July 18, 2024
    WCAG Compliance
    Accessibility, digital accessibility, Shopify, Shopify Themes, web development, Website Accessibility
  • Unwrap Web Accessibility: A Gift for All Shoppers

    Unwrap Web Accessibility: A Gift for All Shoppers

    ‘Tis the season of joy, laughter, and, of course, holiday shopping! As the holiday spirit fills the air, retailers are gearing up to capture their share of the holiday shopping extravaganza. But in the midst of the twinkling lights, festive decor, and holiday cheer, there’s an aspect you may be overlooking – web accessibility.

    To add an extra dose of cheer to this season, our team at 216digital has put together a list of simple and immediate steps that every online retailer can take to ensure their online content caters to all shoppers.

    ‘Tis the Season for All Shoppers

    The holiday season is when people actively hunt for gifts and turn to online shopping in their quest for the perfect presents. However, many website owners are missing out on a massive, often overlooked market share: people with disabilities. 

    According to the World Health Organization, roughly 16% of the world’s population has some form of disability. When your website isn’t accessible, you’re closing the door on this large group of potential consumers.

    To put this into perspective, let’s consider some statistics:

    • In the United States, approximately 27% of adults have some form of disability. That’s more than 61 million people who could become your future customers.
    • Shoppers with disabilities have a combined disposable income of about $490 billion. By neglecting their needs, you are missing out on a substantial source of revenue.
    • Research has shown that 71% of disabled customers will leave a website if they find it difficult to use. Therefore, improving web accessibility can have a direct impact on your conversion rates.

    Holiday Shopping Challenges

    For people with disabilities, shopping online can pose challenges. According to WebAIM’s 2023 analysis of the top 1 million websites on the internet, a staggering 96.3% of them had severe accessibility issues. These issues included the inability to view product descriptions, make a purchase, or book an appointment.

    During the holiday shopping season, people with disabilities may face even more challenges while shopping online. For instance: 

    • Most holiday promotions are shared through email or social media, which can be challenging to access for some people with disabilities. 
    • Each website update, which often includes fresh branding, promotional banners, and product pages, presents an opportunity to introduce new accessibility barriers
    • The holiday rush can overwhelm customer service teams, making it more challenging for people with disabilities to receive the assistance they may need.

    So, how can you make your website accessible to all holiday shoppers?

    Understanding Web Accessibility

    Web accessibility is about making your website usable and navigable by people with disabilities. That means designing and developing your holiday content in a way that allows everyone to access and use your site effectively.

    Here are a few key aspects of web accessibility you should focus on this holiday season.

    Paint a Clear Picture with Alt Text

    During the holiday season, visuals play a significant role in attracting shoppers to your site. In fact, 75% of online shoppers rely on product photos when purchasing. However, some users may have visual impairments and rely on screen readers to navigate your website. To make sure they don’t miss out on your visually appealing content, it’s crucial to use image alternative text or alt text.

    What is Alt Text?

    Alt text is a description added to an image’s HTML code. It provides a textual alternative to the image, allowing screen readers to convey the image’s content and function to users who cannot see it. 

    When done right, it can help paint a picture of your products and services. Unfortunately, many businesses forget to provide alt text, or they treat it like a file naming system. For example, an image of a size chart with alt text that says “size chart.” It might as well not be there.

    You can write more helpful alt text by following these best practices:

    Be Descriptive

    When adding alt text to your images, be descriptive but concise. For instance, if you’re selling a holiday-themed sweater, the alt text could be “Cozy red holiday sweater with reindeer patterns.” This way, users with visual impairments understand the image’s content.

    Avoid Redundancy

    It might seem helpful but do not include phrases like “picture of” or “image of” in your alt text. Screen readers will know from the preceding HTML tag to announce the alt text as an image. Including these phrases in your description will only disrupt the user’s experience.

    Write for People, Not Search Engines

    It’s important to remember not to treat alt text as an SEO tool. Many content creators make the mistake of trying to include keywords in their site’s alt text. But while alt text can contribute to SEO, your priority should be accessibility and user experience. Remember, at the end of the day, you’re trying to sell a product to a person, not Google. So, focus on creating descriptive and concise alt text that helps users with visual impairments understand the image’s content.

    For more information on alt text, check out our article “Understanding Image Alt Text Descriptions.”

    Design for Sound Off Videos

    Videos are an engaging way to showcase your holiday products or promotions. However, videos often rely on visual and auditory elements, which can be problematic for those with hearing impairments. To make your videos more inclusive:

    • Invest in High-Quality Audio: If you use VoiceOvers or soundtracks in your videos, ensure that the audio quality is top-notch. Clear audio is essential for users who rely on sound to understand your content.
    • Use Audio Descriptions: For videos with crucial visual content, provide audio descriptions. Audio descriptions are narrations that explain what’s happening in the video. This helps users with visual impairments understand the context and content of the video.
    • Proof Captions by Hand: Automatic captioning can be unreliable, and errors in captions can lead to misunderstandings. Take the time to review and edit captions to ensure they accurately reflect the spoken content.

    Make Your Email Campaigns Web Accessible

    Email marketing is a powerful tool during the holiday season. However, most of the images used in email marketing lack accessibility.

    For instance, in many promotional emails, you’ll find special offers, product names, sale prices, and other important information. If all of this information is only presented in images, it excludes people who rely on screen readers.

    As a general rule, businesses should avoid using images as the sole content of their emails. And when images are used, they must include descriptive alt text. However, there’s more to email accessibility than just alt text. 

    To ensure that your emails reach and resonate with all potential customers, consider the following:

    • Set the Role Attribute of Every Table to “Presentation.”: Tables in emails can be challenging for screen readers to interpret. By setting the role attribute of every table to “presentation,” you tell assistive technologies that the table is for layout purposes only, making the email easier to navigate.
    • Underline Inline Links: When creating links in your emails, use descriptive link text. For example, instead of “Click here,” use “Shop our holiday collection now.” This provides clarity and context to users.
    • Make Sure Links are Descriptive: When creating links in your email content, use descriptive anchor text that indicates where the link leads. Avoid generic terms like “click here” and instead use specific text that tells users what to expect when they click.

    Heading Towards Holiday Content

    It’s that time of year when new content and blog articles are in full swing, highlighting future sales and this year’s latest products. However, the essential element of all good content is using headings. Headings aren’t just big, bold, decorative text. They’re the signposts that guide readers through your content from most to least important. 

    For instance, just like a tree has a trunk, main branches, and smaller branches, your content should have a main heading, subheadings, and further divisions if necessary. 

    • Here are a few pointers when you are generating your online content:
    • Write concise, meaningful headings that provide insight into the content.
    • Elements that are repeated across different pages within a site should maintain a consistent order. That one bold font may be more eye-catching, but that doesn’t mean you need to use it.
    • Headings and labels should aid shoppers in navigating content and understanding their current location by clearly describing the topic or objective. 

    Don’t Let Web Accessibility Be Your New Year’s Resolution

    The holiday season is the perfect time to implement these changes and make your website more accessible. So, don’t let web accessibility be your New Year’s resolution; make it a top priority for your online business now, and watch your holiday sales soar. 

    Ready to get started? Schedule a Complimentary ADA Strategy Briefing with the experts at 216digital. We will help you take the steps towards making your content web accessible on your terms by developing a strategy to integrate WCAG 2.1 compliance into your development roadmap.

    Greg McNeil

    December 8, 2023
    How-to Guides, The Benefits of Web Accessibility, WCAG Compliance
  • Does Your Image Need Alt Text to be Web Accessible?

    Does Your Image Need Alt Text to be Web Accessible?

    Images are the bread and butter for any website. You put a lot of time and effort into creating engaging visual content for your audiences. But that’s only half of the battle — making your content accessible to as many people as possible is the other half. 

    Despite the accelerated pace of the digital era, many businesses and organizations still lag behind in making their websites accessible to people with disabilities. This is partly due to the lack of awareness and/or technical knowledge of different web accessibility barriers and how to solve them. 

    What happens when your users have visual impairments? How do they receive and understand this visual information? 

    In this article, we answer one of the most commonly asked questions — does my image need alt text to be web accessible?

    Image Types And Alternative Text

    Before we analyze an image for web accessibility, we must first take a step back and think about its purpose. Is it to inform, evoke emotion, serve as a link, or just for visual appeal?

    To understand how to make the image accessible for users with assistive technologies (AT) like screen readers, ask:

    • “What is the message the image is trying to convey?”
    • “Is the message simple or complex, emotional or actionable?”

    An online tool like an image decision tree can help categorize your image. Or, think about if the image disappeared. Would you still understand the content’s meaning without it?

    If the answer is yes, the image is purely decorative. However, the image is necessary if the image provides the user with valuable information and context. 

    Once you determine what kind of image you are working with, there are some basic web accessibility guidelines to consider.

    Decorative Images

    There is a lot to consider when it comes to decorative images. If you find yourself saying, “But what about X? or “How about Y?” you might need to reevaluate your image as it might not be decorative. 

    One of the most challenging images to categorize tends to fall in the “emotional” or “mood” category since these images are more subjective. What one person considers decorative, another might consider informative. So, use your best judgment.

    Hiding Decorative Images

    While decorative images can enhance visual appeal, they don’t convey any meaningful information. If the image is decorative, then programmatically, the image needs to be hidden from assistive technology. 

    There are several ways to hide alternative text, including using empty or null alt (alt=””), using ARIA role=” presentation”, or implementing the image as a CSS background. This will signal the AT device to ignore this image as it is not vital to understanding the content. 

    However, it’s important to note that an empty or null alternative text attribute is not the same as a missing attribute. If the alternative text attribute is missing, the AT device might read the file name or surrounding content instead to provide the user with more information about the image. 

    While aria-hidden= “true” is an option, be cautious, as it will remove the entire element from the accessibility API.

    Informative Images

    If you decide your image is informative, there are a lot more things to consider. Visually impaired individuals often rely on screen readers to navigate the web. These devices read out textual content, but they can’t “see” images. To bridge this gap, we must have programmatically-discernible alternative text within the website’s HTML.

    Alt text is a brief description that conveys the essential information of an image. But having alternate text is not enough — it must also be meaningful. For example, the alt text for a picture of a woman baking might be” Woman baking” — does that convey the whole message? Instead, the alt text should be “Racheal Ray preparing chocolate chip cookies.”

    Of course, AT users will have to listen to your alternative text, so do not go overboard. While your descriptions should paint a vivid picture for the user, limiting the number of characters to only 150 is best practice. If you need to add more context to the image, you can use other, more descriptive methods to add more detail.

    To learn more about writing alt text, check out our blog post, Understanding Image Alt Text Descriptions.

    Charts, Graphs, and Other Complex Images

    Sometimes written copy is part of an image, such as in the case of charts, graphs, or diagrams. These images contain too much information to fit into an alt-text description. Instead, you need two parts to describe them. The first part is a short description to identify the image and, if required, the location of the long description. A long description is a textual representation of the essential information conveyed by the image.

    Description Containing Structured Information

    We can use the <figure> and <figcaption> to associate visible text with an image. When using <figure> and <figcaption>, the alt attribute can be more minimal, and the <figcaption> can be more expressive. 

    This approach provides a link next to the image that will send the user to a separate web page or a section containing a more detailed description of the image. However, the link text must clarify the destination and associate it with the image. The <figure> and <figcaption> elements can also be used for groups of images.

    To identify the complex image, we can also provide accessible names to the image programmatically using the aria-describedby attribute. AT devices will ignore the image’s alt text when these attributes are present and read the ARIA label instead without forcing the users to leave the page. However, this approach can only work if the long description is text-only and does not require structural information. 

    Meeting Image Accessibility Standards

    In an increasingly digital world, ensuring that every user, irrespective of their ability, can access and understand your content is paramount. Ignoring the significant segment of people with disabilities is not only a detriment to your brand’s inclusivity but also a missed opportunity for engagement and growth. 

    Partnering with 216digital takes the complexity out of the equation, providing expert guidance, tools, and techniques tailored to your needs. We understand that every aspect of your site requires thoughtful consideration, and we’re ready to assist you every step of the way. Don’t leave your web accessibility to chance; schedule a Complimentary ADA Strategy Briefing with our team today, and let us help you make your site truly accessible for everyone.

    Greg McNeil

    August 10, 2023
    How-to Guides, WCAG Compliance
    Accessibility, ADA Compliance, ADA Website Compliance, Alt text, Image Alt Text, Website Accessibility
  • Understanding WCAG for Better Digital Compliance

    Understanding WCAG for Better Digital Compliance

    The World Wide Web is an interconnected network of knowledge accessible to anyone with an internet connection. However, the term ‘anyone’ isn’t always accurate. Some individuals, particularly those with disabilities, may find it challenging to access information and services online.

    Fortunately, the Web Content Accessibility Guidelines (WCAG) are here to change this. WCAG can help websites follow the best practices of accessible design and eliminate accessibility barriers that could expose your business to the risk of legal action.

    But what is WCAG — and how does it apply to your online business? In this post, we answer these questions and provide a few tips for making your web content WCAG-compliant.

    The World Wide Web Consortium

    The World Wide Web Consortium (W3C) is an international organization committed to improving the web. In 1997, the W3C launched the Web Accessibility Initiative (WAI) with the goal of providing strategies, guidelines, and resources to make the web accessible to people with disabilities. This initiative includes technical specifications for HTML, CSS, XML, and other technologies used to build websites.

    Out of the WAI was born the Web Content Accessibility Guidelines or WCAG.

    What is WCAG?

    The Web Content Accessibility Guidelines, commonly known as WCAG, are a set of recommendations designed to make web content more accessible, primarily for people with disabilities. However, following these guidelines can also make your web content more accessible to all users, regardless of the device they’re using or their internet access circumstances.

    The initial version of WCAG, WCAG 1.0, was released in 1999 with 14 guidelines. Since then, it has undergone significant revisions to better address the needs of various users and keep pace with rapidly evolving technologies. The most recent version at the time of this writing, WCAG 2.1, was published in 2021. However, the WAI plans to introduce WCAG 2.2 in the fall of 2023. Learn more about WCAG 2.2 and the future of accessibility standards.

    WCAG Structure

    WCAG is organized around four fundamental principles, which state that all content must be Perceivable, Operable, Understandable, and Robust (POUR). These four principles are expanded upon by supporting guidelines and further divided into distinct Success Criteria. These Success Criteria serve as precise and verifiable requirements for accessibility.

    An Example of WCAG Success Criteria 

    Success Criterion 1.1.1 Non-text Content states: “All non-text content presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below…”

    This Success Criterion is one of the Success Criteria under Guideline 1.1 Text Alternatives: “Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols, or simpler language.”

    This Guideline is one of the Guidelines under Principle 1. Perceivable: “Information and user interface components must be presentable to users in ways they can perceive.”

    WCAG Conformance Levels

    WCAG success criteria are organized into three levels of conformance: Level A, Level AA, and Level AAA. Each Success Criterion is assigned a conformance level of A, AA, or AAA, with each Level including all success criteria from the lower levels.

    For instance, Level AA includes all Level A success criteria, while Level AAA includes both Level A and AA success criteria. To qualify as meeting a certain conformance level, all content on a website must fully meet at least that Level.

    While Level A conformance makes a website accessible, Level AA conformance of WCAG 2.0 or 2.1 is the most common. Websites that meet the Level AA requirements of the current version of WCAG are generally considered reasonably accessible to most users with disabilities.

    Achieving Level AA conformance means satisfying all Level A and AA Success Criteria. However, it’s important to note that meeting Level AAA is optional as it’s impossible for some content to meet all Level AAA Success Criteria.

    Understanding How WAI Maintains and Updates WCAG

    The WAI regularly updates the WCAG to keep up with advancements in technology and user needs, ensuring the guidelines remain relevant and effective.

    The WAI organizes this process through milestones, which are as follows:

    1. Working Draft: The WAI team publishes the document as a Working Draft to ask for review and input from the community. The team updates the draft based on feedback. Usually, multiple Working Drafts of a technical report are published.
    2. Wide Review Working Draft: Once all the comments and technical requirements have been addressed, it provides the complete document for community review. At this stage, members of the public are invited to leave comments.
    3. Candidate Recommendations: The main purpose of the Candidate Recommendation is to ensure that the technical report can be implemented. At this stage, developers are encouraged to use the new version of WCAG in their projects.
    4. Proposed Recommendation:  After implementing each feature of the technical report, the W3C announces it as a Proposed Recommendation for W3C membership endorsement
    5. W3C Recommendation: Once there is significant support for a new version of WCAG from the W3C Members, the W3C Director, and the public, it becomes an official W3C Recommendation. 

    It’s important to understand that WCAG is a living document, consistently updated to meet changing technology and digital accessibility needs. Hence, reaching each milestone takes time. WCAG needs to apply to different types of digital content and be reasonably future-proof.

    But which version of WCAG should you use to test your content?

    Which Version of WCAG Should I Use To Test My Content?

    WCAG offers businesses a straightforward way to test their web content for accessibility issues. Each version of WCAG is designed for backward compatibility, including all previous guidelines and adding new ones. While recent versions of WCAG extend the requirements of older versions, the old standards still apply.

    But which version of WCAG should you use for testing? When deciding which version of WCAG to use for testing your content, it’s generally recommended to use the latest version. Using the most recent version will ensure your website complies with the Americans with Disabilities Act (ADA) and other nondiscrimination laws, mitigating the risk of frivolous ADA lawsuits.

    Is WCAG a Legal Requirement?

    While WCAG is not legally binding in every country, many governments require compliance with its guidelines to ensure digital accessibility. For instance, in the US, federal websites must meet WCAG 2.1 Level A and AA requirements under Section 508 of the Rehabilitation Act.

    Similarly, Title III of the ADA applies to private businesses but doesn’t explicitly mention WCAG or provide technical standards for online content. However, the Department of Justice (DOJ) published guidance in 2022 confirming its position that the ADA applies to business 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.”

    – US Department of Justice | Guidance on Web Accessibility and the ADA (2022)

    The Rise of ADA Web Compliance Lawsuits

    Failure to meet these standards can expose businesses to legal challenges, as was the case with Domino’s Pizza in 2019. More recently, there has been a sharp increase in lawsuits related to website accessibility. For example, in 2022 alone, there were 2,387 web accessibility lawsuits filed in Federal Court and California State Court under the Unruh Act. This number doesn’t include the rising number of ADA legal complaints and ADA compliance demand letters sent to businesses with non-accessible websites.

    While WCAG conformance might not be legally required elsewhere, it’s still considered a best practice and can significantly improve the user experience for all visitors.

    Understanding What Conformance Means

    WCAG conformance means that your website meets the criteria set by the WCAG guidelines. This involves more than just ticking off a list of guidelines; it means ensuring your website is accessible and usable for people with various disabilities.

    W3C’s Understanding Conformance explains: “Conformance to a standard means that you meet or satisfy the ‘requirements’ of the standard.”

    There are five requirements for conformance, per W3C:

    1. Conformance Level:  Websites must fully meet Level A, AA, or AAA levels.
    2. Full Pages: Conformance and conformance levels account for the entire website or web page. It does not exclude a part of the website or a web page or evaluate each page individually.
    3. Complete Process:  If a web page is part of a multi-page process where a sequence of steps must be completed to accomplish an activity, all web pages must conform at the specified Level or better. Conformance can only be achieved if all pages in the sequence of steps conform at that Level or better.
    4. Only Accessibility-Supported Ways of Using Technologies: Accessibility-supported technologies must be used to satisfy the success criteria. Any information or functionality not supported must also be available in a way that is accessibility supported.
    5. Non-interference:  If technologies are used in a way that is not accessibility supported, or if they are used in a non-conforming way, they must not prevent users from accessing the rest of the page. Additional requirements may also apply.

    For more information, review W3C’s Understanding Conformance.

    Building a Strategy for WCAG Conformance 

    Every online business should commit to web accessibility. Thankfully, WCAG makes this process more manageable. By planning to test your content against WCAG Level AA, you can find and address barriers affecting your users.

    At 216digital, we’re dedicated to helping businesses achieve WCAG conformance. We can help develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms so you can focus on your other tasks.

    Would you like to know where your business stands today? Schedule a complimentary ADA Strategy Briefing with 216digital to get a free scan of any URL and uncover accessibility issues on your site.

    Greg McNeil

    July 10, 2023
    WCAG Compliance
    Accessibility, ADA Compliance, ADA non-compliance, ADA Website Compliance, WCAG, Website Accessibility
  • 5 Types of Assistive Technology Tools

    5 Types of Assistive Technology Tools

    The Internet is an essential resource for people worldwide. It provides access to information, entertainment, and services that make daily life easier. However, for people with disabilities, navigating the web can be a daunting task. That’s where assistive technology comes in. They help to bridge the gap and make the web more accessible for everyone.

    So, what does your online business need to know about assistive technologies, and how can you make sure your website is compatible? In this post, we’ll break down the following:

    • What Is Assistive Technology?
    • What are 5 Types of Assistive Technology Tools?
    • How Can I Make My Website Accessible?

    What Is Assistive Technology?

    Assistive technology(AT) is any tool or device that helps individuals with disabilities to access, navigate, and interact with web content. These tools can be hardware or software solutions that make it easier for people with various impairments to access and use websites and other digital resources. For example, a switch device using blinking or tapping can replace the need for a keyboard or mouse.

    Typically, four main types of disabilities need to be considered.

    • Visual: People who are blind, have low vision, or are color blind.
    • Auditory: People who are hard of hearing or deaf.
    • Motor: People who have limited fine motor control, muscle slowness, or tremors and spasms
    • Cognitive: Cognitive disabilities hinder the behavior and intellectual development of a person. This includes a broad range of disabilities, from mental illnesses to learning disabilities or old age.

    Different types of ATs are built to help each of these groups access web content. These tools are designed to bridge the gap between the users’ abilities and the demands of websites, making the web more accessible and inclusive.

    What are 5 Types of Assistive Technology Tools?

    With so many different types of assistive technology, it can be challenging to know where to start. So here are five of the most common types and how they help support people with disabilities browse the web:

    1. Screen Magnification Software

    Did you know that over 200 million people worldwide have a visual impairment that makes it difficult to read standard-sized text on a screen? Users with low vision often rely on magnification tools, such as screen magnifiers or browser zoom features, to make content legible or to reduce eye strain.

    Most web browsers can “zoom in” on content, but screen magnification software works differently. Tools like MAGic, Windows Magnifier, and Apple’s Zoom magnify a part of the screen at a time, preserving the web page’s layout.

    However, many users prefer to use the zoom function on their browsers. So don’t assume anyone with a visual impairment will only use screen magnification software when accessing your website.

    The Web Content Accessibility Guidelines (WCAG) are a set of intentionally shared standards for website accessibility. For example, WCAG’s “Resize Text” guideline requires content to be zoomed in at least 200% before losing content or functionality. 

    2. Screen Readers

    Screen readers are essential for users who are blind or have severe visual impairments. These software programs convert on-screen text into spoken words or braille output. As a result, users can navigate and interact with your website using only auditory feedback.

    Popular screen readers include JAWS (Job Access With Speech), NVDA (NonVisual Desktop Access), and VoiceOver (for Apple devices). Each screen reader has its capabilities and limitations for carrying out tasks. However, screen readers only work if websites are compliant.

    Here are a few examples of WCAG guidelines that are essential for screen readers:

    • Providing all non-text content (images, form fields, video, audio, etc.) with alternative text descriptions. For example, images should have a text description that explains the image’s purpose on the page.
    • Websites should use clear, descriptive headings and labels.
    • Websites can be navigated with a keyboard or an alternate keyboard only.

    3. Voice Recognition

    One of the growing advances in AT is voice recognition. Voice recognition technology lets users control their browsers, dictate text, and interact with websites using only their voices. By enabling voice commands, users can navigate, click on links, fill out forms, and perform other tasks without using their hands.

    Users should be able to use common commands such as “go to the homepage” to operate websites in predictable ways. However, web content must be designed and coded for users to use voice recognition tools.

    Here are a few WCAG guidelines that can help improve the browsing experience for speech recognition users:

    • Provide users with a clear visual indicator of which element is the current focus. Without focus indicators, users might not know what they’re controlling.
    • Use labels and identifiers for interactive elements. Each element’s programmatic label should match its visual presentation. For instance, if a user sees a “submit” button on a page form, they should be able to say “submit” to activate the control and complete the form.
    • Remove any keyboard traps that would prevent users from navigating your site after focusing on a certain element.

    4. Switch Devices

    A switch device is a specialized input tool that replaces the need for a keyboard or mouse. It is used by people with physical disabilities or fine motor impairments to access and control computers, smartphones, and other communication devices.

    However, switch devices vary based on the user’s mobility, preferences, and settings. This can include pressing a button, blowing into a tube, or even moving an eyebrow. For example, users can press a large, round button with their hand, foot, or whatever is most comfortable. Then, on the screen, a focus indicator will automatically cycle through different elements on the site, and the user can click to activate the switch.

    Like voice recognition AT, switch devices require similar WCAG standards to be implemented on a website for users to engage in the content.

    5. Closed Captioning Services

    Most of us are more familiar with closed captions, from streaming services and YouTube to video calls with Zoom. However, although it’s one of the more popular ATs, it is often overlooked.

    Closed captioning services provide on-screen text corresponding to video and multimedia presentations’ audio content. By providing accurate and synchronized text captions for your multimedia content, you’re allowing users who are deaf or hard of hearing to understand and engage with your website. For this reason, WCAG requires all pre-recorded audio content to be clearly labeled, except for media with an alternative text option. 

    However, while automatic caption tools are available, they are far from perfect. For instance, we have all watched a YouTube video where captions do not always align with the speaker’s words. If it was not for our ability to hear, the message’s meaning would be different based on what the auto caption filled in. Therefore, it is highly recommended to use closed captioning services that employ human transcribers to make captions and transcripts more accurate.

    How Can I Make My Website More Accessible?

    With so many different types of AT available, it can be hard to know where to start. But regardless of where you are on your accessibility journey, we’re here to help. At 216digital, we can help develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms. Providing an accessible browsing experience to all your users, including those with disabilities.

    To learn more about how the ADA experts at 216digital can help build an ADA WCAG 2.1 compliance strategy to achieve ongoing, real-world accessibility on your terms, schedule an ADA Strategy Briefing.

    Greg McNeil

    April 28, 2023
    WCAG Compliance
    Accessibility, ADA Compliance, ADA Website Compliance, Website Accessibility
  • What to Expect from WCAG 2.2

    What to Expect from WCAG 2.2

    Are you an online business or website owner? If so, you must be aware of the critical changes in the  Web Content Accessibility Guidelines (WCAG) 2.2! The World Wide Web Consortium (W3C) is expected to release the latest version of WCAG in May 2023. So stay ahead of the curve and ensure your website remains accessible to all users, including those with disabilities. Here’s what you need to know about the proposed changes — and how they will affect your current WCAG compliance. And remember, when WCAG 2.2 goes live, 216digital will be here to help.

    Why is WCAG Changing?

    WCAG is a set of guidelines designed to help make web content more accessible to people with disabilities. However, as technology and user preferences change, so must WCAG’s standards. Each new standard introduced is developed by the Web Accessibility Initiative (WAI). In 2021, WAI announced they were starting to work on the draft for WCAG 2.2, which is finally expected to be released sometime next month.

    WCAG can be changed to add new success criteria or to change a current guideline’s conformance level. But, it will not remove any guidelines or change any language. Currently, WCAG 2.2 is based on the same three conformance levels as the previous versions: Level A, AA, and AAA.

    Level A

    Level A is the lowest level of conformance and the easiest to achieve with minimal impact on a website’s structure or design. It allows websites to be broadly accessible as it addresses the most basic access issues.

    Level AA 

    By meeting the success criteria for Level AA, websites are considered reasonably accessible as they offer a higher level of conformity than Level A. AA is most often used as the compliance standard in lawsuits and is usable for most people.

    Level AAA

    Level AAA is the highest level of conformance and the most difficult to achieve. It is not often used as a goal to strive toward since it is not feasible for most websites to have the resources to meet this level.

    What’s Changing In WCAG 2.2?

    WCAG 2.2 introduces nine new success criteria along with minor changes to the instructions accompanying several established guidelines. However, each of these criteria is still up for feedback and changes, so there’s no guarantee that all of them will make it into the final version of WCAG 2.2.

    Here’s a quick overview of the new guidelines — and how each one can help address web accessibility issues:

    Guideline 2.4 Navigable

    2.4.11 Focus Appearance (Minimum)

    Level AA

    Focus Appearance builds on two existing WCAG criteria, specifying the minimum requirements for focus indicators. The new guideline ensures that keyboard focus indicators are visible and easily distinguishable. They must have a clear border, are not obscured by other content, and have at least a color contrast ratio of 3:1 against the unfocused state and all adjacent colors.

    The intent of WCAG 2.4.11  is to help low-vision users who use a keyboard for navigation. Users can quickly tell where they are on a page by ensuring the current focus point is visible.

    2.4.12 Focus Not Obscured (Minimum)

    Level AA

    Knowing the current focus point is essential for sighted users who use a keyboard or keyboard-like device. However, sticky headers, pop-ups, and other content can sometimes obscure focused elements while a user is browsing.

    However, Criterion 2.4.12 requires user interface components not to be entirely hidden from other content on the page. This lets users easily track the current focus point and avoid confusion.

    2.4.13 Focus Not Obscured (Enhanced)

    Level AAA

    Similar to 2.4.12, 2.4.13 requires that no part of the focus indicator is hidden by other content.

    Guideline 2.5 Input Modalities

    2.5.7 Dragging Movements

    Level AA

    Drag and drop movements can be difficult and error-prone for many website users. Therefore, WCAG 2.5.7 requires that any functionality that uses a dragging movement for operation can also be achieved in other ways, like clicking. For example, a user could use a single tap, double tap, long presses, or path-based gestures instead of dragging an item. However, a dragging action is allowed when it is essential to the functionality of the content.

    2.5.8 Target Size (Minimum)

    Level AA

    When buttons and other clickable elements are small, they can be challenging to interact with for people with fine motor impairments. The purpose of 2.5.8 is to ensure that when users select a target with a mouse or other device, they can do so easily without activating other nearby targets. Therefore, all clickable elements, such as links, must be at least 24 by 24 CSS pixels in size and spacing between adjacent targets.

    2.5.8 provides a level AA alternative to 2.5.5: Target Size (Enhanced), which was introduced as part of WCAG 2.1. However, 2.5.5 requires the target size for all clickable elements to be at least 44 by 44 CSS pixels.

    Guideline 3.2 Predictable

    3.2.6: Consistent Help

    Level A

    The goal of 3.2.6 is to ensure that all users can easily find help when completing tasks on a web page. For example, suppose a help feature — such as search bars and help buttons — is available on multiple pages of a website. In that case, it must appear in the same relative place an order on each of the pages where it appears. This is particularly beneficial for users with cognitive disabilities or limited web experience, as they can quickly access help when needed.

    Guideline 3.3 Input Assistance

    3.3.7 Redundant Entry

    Level A

    For people with cognitive disabilities, logging into a website or mobile app can be challenging. The 3.3.7  level AA guideline tackles authentication processes that require the user to remember, manipulate, or transcribe information. Websites that use cognitive function tests must provide at least one other authentication method.

    For instance, asking users to remember a password is a standard cognitive function test. But suppose the website allows entries from password manager browser extensions. In that case, the website has provided them with a mechanism to complete the process.

    3.3.8 Accessible Authentication (Minimum)

    Level AA

    3.3.8 takes 3.37 further by not allowing any exceptions for cognitive function tests. For multi-step processes, 3.3.8 requires websites to auto-populate fields or enable users to select the information that they’ve previously entered. For example, suppose a website’s form requires the user to enter their address multiple times. In that case, the second field should either provide users with an option to select their address from the previous entry or auto-populate.

    3.3.9: Redundant Entry ( Enhanced)

    Level AAA

    Similar to 3.3.7 and 3.3.8, 3.3.9 applies to the authentication process. However, 3.3.9 is a Level AAA guideline that does not require an authentication process unless that step provides an alternative authentication process or auto-populate.

    Getting Ready for WCAG 2.2

    While the full implementation of WCAG 2.2 may still be on the horizon, it’s never too early to start preparing. Here are some steps you can take to ensure a smooth transition:

    1. Familiarize yourself with the new success criteria and understand their implications for your website.
    2. Conduct an accessibility audit to identify areas that need improvement and align with WCAG 2.2 requirements.
    3. Update your website’s design, content, and functionality to address the new criteria and improve accessibility.
    4. Train your team on the importance of web accessibility and the new guidelines to ensure consistent implementation.

    How Will the Revisions Affect My Current WCAG Compliance?

    The transition from WCAG 2.1 to 2.2 will require some adjustments to your website, particularly in the areas of navigability, input modalities, predictability, and input assistance. However, these updates are designed to build upon the existing guidelines, so your current efforts will not be wasted. By proactively addressing these changes, you’ll ensure that your website remains compliant and accessible to all users.

    When WCAG 2.2 Goes Live, We’ll Be Here to Help

    When WCAG 2.2 goes live, you can count on  216digital to help you navigate the changes and maintain an accessible website. Our expert team will assess your website, provide recommendations, and implement the necessary adjustments to ensure your website meets the latest accessibility standards. Reach out to us today by scheduling a complementary ADA Strategy Briefing so that you can embrace the future of web accessibility with confidence.

    Greg McNeil

    April 28, 2023
    WCAG Compliance
    Accessibility, ADA Compliance, ADA Website Compliance, WCAG, WCAG 2.2, Website Accessibility
Previous Page
1 2 3 4 5
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.