216digital.
Web Accessibility

Phase 1
Web Remediation for Lawsuit Settlement & Prevention


Phase 2
Real-World Accessibility


a11y.Radar
Ongoing Monitoring and Maintenance


Consultation & Training

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

Web Design & Development

Marketing

PPC Management
Google & Social Media Ads


Professional SEO
Increase Organic Search Strength

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

About

Blog

Contact Us
  • WCAG: Web Accessible Coding 101

    Creating an inclusive online experience is more important than ever in today’s digital world. Accessible coding isn’t just a nice-to-have; it’s a must-have. But what does accessible coding mean, and why should you care? In this article, we’ll dive into the basics of accessible coding, explore seven fundamental principles with examples, and explain why following these guidelines benefits everyone.

    What is Web Accessibility?

    Web accessibility means making websites usable by everyone, including people who rely on assistive technologies like screen readers, people who can’t use a mouse, or those with visual or cognitive impairments. The Web Content Accessibility Guidelines (WCAG) offer a framework for creating accessible content. Adhering to WCAG helps ensure that your site is user-friendly for all.

    Why Accessible Coding is Important

    Accessible coding is crucial for a variety of reasons:

    • Wider Audience Reach: By making your site accessible, you expand your audience and enhance user experience for everyone.
    • SEO Benefits: Accessibility often overlaps with good SEO practices, boosting your website’s visibility.
    • Legal Requirements: Laws like the ADA in the U.S. require websites to be accessible, protecting you from potential legal issues.

    Now let’s dive into seven core principles of accessible coding and see how you can implement them in your website’s code.

    1.Provide Alt Text for Non-Text Components

    Alt text (short for “alternative text”) is one of the most basic, yet essential, components of web accessibility. According to WCAG 2.1 SC 1.1.1 (Non-text Content), it serves as a textual description for images and non-text content, enabling users who rely on screen readers to understand what the visual content represents.

    Why Alt Text is Important:

    • Screen Reader Accessibility: People with visual impairments use screen readers that read aloud the alt text. If an image lacks alt text, the user will miss out on important information.
    • SEO Benefits: Alt text improves SEO by giving search engines more information about the content of your images. Search engines can’t “see” images, but they can index alt text, helping your site rank better in image search results.

    Best Practices for Writing Alt Text:

    • Be Descriptive and Specific: Describe the content and purpose of the image. For example, instead of just saying “image of a tree,” say, “A large oak tree in a park during autumn.”
    • Keep it Concise: Alt text should typically be no longer than 125 characters. This keeps the description brief while still conveying necessary information.
    • Use Empty Alt Attributes for Decorative Images: For images that serve a purely decorative purpose (i.e., they don’t convey information or serve a functional purpose), use an empty alt attribute (alt=””). This prevents screen readers from wasting time on irrelevant content.

    Example:

    <img src="award-ceremony.jpg" alt="CEO receiving the 'Best Company Award' at the 2024 Business Awards" />

    In this example, the alt text describes the image in a way that conveys its significance. This provides context for users who cannot see the image and helps them understand its role on the page.

    For purely decorative images that don’t add meaning, you would use an empty alt attribute:

    <img src="border-decoration.png" alt="" />

    For more information about Alt text for images, check out our article Understanding Image Alt Text Descriptions.

    2. No Keyboard Traps

    Keyboard accessibility is critical for users who cannot use a mouse and instead rely on keyboard navigation. “Keyboard traps” occur when users get stuck in a particular interactive element (such as a form field or a modal window) and can’t navigate out using the keyboard alone.

    According to WCAG SC 2.1.1 Keyboard, websites need to be fully navigable using just a keyboard. This means that all buttons, links, and forms should be reachable and usable without a mouse. If a site doesn’t meet this standard, it can exclude many users and make it less accessible.

    How to Prevent Keyboard Traps:

    • Ensure All Interactive Elements Are Focusable: Elements like buttons, form fields, and links must be easily accessible via the keyboard’s “Tab” key.
    • Provide a Clear Way to Escape Modals: If using pop-ups or modal windows, ensure that users can exit using keyboard controls, typically the “Escape” key.

    Example:

    <a href="submit.html" id="submit-btn" tabindex="0">Submit</a>

    This code ensures that the “Submit” button can be accessed via keyboard. The tabindex="0" attribute allows it to be included in the natural tab order of the page.

    3. Allow Users to Resize Text

    People with visual impairments often need to increase the text size on websites. Accessible websites allow users to resize text up to 200% without breaking the page layout or losing content.

    How to Implement Text Resizing:

    • Use Relative Font Sizes: Avoid using fixed units like px for font size. Instead, use relative units such as em or percentages (%). This ensures that text can scale properly.
    • Test Text Scaling: After implementing relative font sizes, test your site by increasing text size to 200% in different browsers to ensure the content remains legible and the layout doesn’t break.

    Example:

    body {
    font-size: 100%; /* Base font size that scales */
    }
    h1 {
        font-size: 2em; /* 200% of the body text size */
    }

    In this example, the body text is set at a flexible 100%, and the headings use a relative size (2em) that will scale based on the user’s settings.

    4. Avoid Seizure Triggers

    Flashing elements or rapid changes in brightness can trigger seizures in people with photosensitive epilepsy. The WCAG SC 2.3.1 recommends that content should not flash more than three times per second.

    How to Prevent Seizure Triggers:

    • Avoid Fast Animations: If you need animations, make sure they don’t flash rapidly or use extreme changes in brightness.
    • Limit Flashing to Below 3 Hz: Ensure that any flashing or blinking elements do not exceed three flashes per second.

    Example:

    /* Safe animation with no rapid flashing */
    @keyframes safe-flash {
        0%, 100% { opacity: 1; }
        50% { opacity: 0.5; }
    }
    .flash-warning {
        animation: safe-flash 2s infinite;
    }

    This animation fades in and out at a safe pace, avoiding any rapid flashing that could trigger seizures.

    5. Follow a Logical Reading and Code Order

    Users who rely on screen readers navigate websites based on the underlying HTML code order, which means the structure of your code must match the logical flow of the content.

    According to WCAG Success Criterion 2.4.3, websites should be designed to allow users to navigate easily using links, headings, and other navigation tools. This means your website should allow users to effortlessly find what they’re looking for without feeling lost.

    How to Implement a Logical Code Order:

    • Use Semantic HTML Elements: Elements like <header>, <nav>, <main>, and <footer> create a well-structured HTML document that is easy for screen readers to understand.
    • Organize Content in a Meaningful Way: Ensure that headings, paragraphs, and sections appear in the correct order in your code, as this will directly impact the reading experience for users with assistive technology.

    Example:

    Here, the content is organized in a logical structure, making it easier for screen readers to understand and navigate.

      <header>
        <h1>Welcome to Our Store</h1>
        <nav>
            <ul>
                <li><a href="#home">Home</a></li>
                <li><a href="#shop">Shop</a></li>
                <li><a href="#contact">Contact Us</a></li>
            </ul>
        </nav>
    </header>
    <main>
        <section id="shop">
            <h2>Shop Our Latest Collection</h2>
            <p>Browse our new products for this season.</p>
        </section>
    </main>
    <footer>
        <p>&copy; 2024 Our Store</p>
    </footer>
    

    6. Use Headings Appropriately

    Headings are critical for organizing content and allowing users to quickly scan and understand the page structure. Screen readers rely on headings to navigate through content, making proper heading hierarchy essential.

    Best Practices for Headings:

    WCAG SC 1.3.1 Info and Relationships requires that content structure and relationships be programmatically determined or available in text. Proper use of headings and a clear content structure ensure that users can navigate and understand the content more easily.

    • Use Headings to Structure Content: Use <h1> for the main title of the page, <h2> for section titles, and so on. Don’t skip heading levels (i.e., don’t jump from <h1> to <h3>).
    • Avoid Using Headings Solely for Styling: Headings should not be used just to make text look bigger or bolder. Use them to represent the content hierarchy.

    Example:

    <h1>Guide to Accessible Coding</h1>
    <h2>Why Accessibility Matters</h2>
    <h3>Legal Requirements</h3>
    <h3>Improved User Experience</h3>

    In this example, the headings follow a logical order, making the content easy to navigate for users with screen readers.

    7. Use HTML Tags That Make Websites Accessible

    HTML provides several built-in tags that make websites more accessible. Using these elements correctly ensures that assistive technologies can understand and interact with the content.

    Key Accessible HTML Elements:

    • <label>: Associates a form field with a text description, making it easier for screen readers to understand.
    • <button>: Creates a clickable button that is accessible via keyboard and screen readers.
    • ARIA Attributes: These attributes, such as aria-label and aria-required, provide additional context for assistive technologies.

    Example:

    <form>
        <label for="email">Email Address:</label>
        <input type="email" id="email" name="email" aria-required="true">
    </form>

    In this example, the <label> tag clearly associates the input field with its description, while the aria-required="true" attribute informs screen readers that the field is mandatory.

    Don’t Just Code—Create a Welcome Mat for the Web

    Creating accessible websites isn’t just about meeting guidelines—it’s about making sure everyone has equal access to information and services online. Accessible coding improves user experience for everyone and can even boost your site’s search engine ranking. Plus, it shows that you care about all your users.

    By following these principles and using the resources provided, you can build websites that are welcoming and usable for everyone. Keep these guidelines in mind as you code, and your website will be a better place for all its visitors!

    For more information on web accessibility and coding best practices, you can visit the WCAG website.

    Greg McNeil

    September 10, 2024
    How-to Guides
    digital accessibility, How-to, WCAG, WCAG Compliance, Web Accessibility, web development
  • Web Accessibility Overlays: Myths vs. Reality

    Web Accessibility Overlays: Myths vs. Reality

    You’ve just added a shiny new widget to your website, promising instant accessibility and compliance with laws like the Americans with Disabilities Act (ADA). Sounds too good to be true, right? That’s because it often is. Many companies market web accessibility overlays as the magic solution to all your accessibility problems. They promise that with just a quick install, your site will be fully compliant and accessible to everyone. It sounds like the easiest fix in the world—but is it really?

    The truth is, while these overlays might seem like a simple answer, they don’t solve everything. From complex guidelines to ongoing legal risks, relying on an overlay alone can give you a false sense of security. In this article, we’ll dive into the real story behind these widgets and explore why genuine web accessibility requires more than just a quick fix. So, buckle up and let’s uncover the truth about web accessibility overlays and what it really takes to make your site inclusive for all users.

    Myth #1: Web Accessibility Overlays Fully Automate Web Accessibility Compliance

    One of the biggest misconceptions about web accessibility widgets is that they can fully automate compliance with web accessibility standards. Many companies selling these overlays promise that adding their widget to a site will instantly make it accessible and compliant with laws like the ADA or the Web Content Accessibility Guidelines (WCAG). This sounds great, right? A simple piece of code can fix all your accessibility problems in a matter of minutes!

    The Truth: Overlays Can’t Fix Everything

    Here’s the thing: overlays can’t fix everything. While they may assist with some accessibility needs—like text resizing or color contrast—they fall short of addressing complex issues that require thoughtful design and coding. Real accessibility involves:

    Complexity of WCAG Standards

    The WCAG guidelines cover a wide range of disabilities—visual, auditory, motor, and cognitive. Meeting these standards often requires more than what widgets can provide. For example, overlays might not solve issues such as:

    • Navigation menus that aren’t keyboard-friendly
    • Popups or modals that don’t properly capture focus
    • Logical tab order problems
    • Incorrectly labeled images, buttons, or form fields
    • Buttons made with non-interactive HTML tags

    While most of these issues are not visible to all users, these issues are significant barriers for users with disabilities. This means that while overlays might help with some parts of compliance, they can’t cover everything.

    Surface-Level Changes

    Many overlays offer features like enlarging text or adjusting color contrast. While these can be helpful, they only address surface-level issues. True compliance involves deeper changes to the website’s code and design—something they can’t provide.

    Dynamic Content Challenges

    Overlays may struggle with dynamic content like live updates or interactive features. These parts of a website that change often might not work well with overlays, leading to potential accessibility problems.

    Myth #2: Overlays Are a One-Size-Fits-All Solution

    Some believe that widgets are a one-size-fits-all solution for every website. The idea is that once you add an overlay, it will work for every visitor, no matter their needs. Marketing claims often suggest that they can solve accessibility issues for all types of disabilities.

    The Truth: Overlays Aren’t Universal Fixes

    Every website is unique, and so are its users’ needs. Here’s why overlays often fall short:

    Different Needs for Different Sites

    Websites come in various forms, from simple blogs to complex e-commerce sites. An overlay might offer basic features, but it might not be suitable for every site. For example, a shopping site with complex navigation might need specific accessibility adjustments that an overlay can’t provide.

    Incompatibility Issues

    Overlays can sometimes interfere with a site’s existing design or functions, especially for custom-built websites or those with complex interactive elements. Instead of helping, the overlay might cause problems or make the site less accessible.

    User Preferences

    Different users have different needs. While overlays might offer some customization options, like changing font size or color contrast, they can’t cater to all specific needs. For example, someone with a motor disability might need easy keyboard navigation, while someone with a cognitive disability might need simpler content. Overlays often lack the flexibility to address all these diverse needs.

    Myth #3: Overlays Improve Accessibility for All Users

    It’s easy to believe that if you add an overlay, you’ve made your website more accessible for everyone. This myth is particularly damaging because it can lead to a false sense of security. Site owners might think they’ve done enough and may not feel the need to make further efforts toward accessibility.

    The Truth: Overlays Can Create Barriers

    Overlays can actually create new barriers for some users. For example, screen readers—used by people who are blind or have low vision—might conflict with overlays, causing confusion or glitches. In some cases, users have reported that they make websites even harder to navigate. So, while widgets might help some users in certain situations, they can also cause new challenges for others.

    Myth#4: Overlays Are a Substitute for Genuine Accessibility Practices

    There’s a belief that adding an overlay is all you need to do for accessibility compliance. Some think this means they can skip the hard work of manual audits, coding standards, and user testing. After all, if the overlay claims to handle accessibility, why bother with anything else? But that’s far from the truth. Genuine accessibility takes more than just a quick fix.

    The Truth: Real Accessibility Requires Real Effort

    True web accessibility means creating an inclusive experience for everyone, which involves more than just using an overlay. Here’s why:

    Genuine Accessibility Takes Effort

    Accessibility involves a mix of automated tools and human effort. Overlays might be part of an accessibility strategy, but they aren’t a replacement for manual audits and user testing. Human testers, especially those with disabilities, can provide insights that automated tools can’t. Real accessibility requires following coding standards, testing with real users, and regularly updating the site based on feedback. It’s a continuous process, not a one-time fix.

    Myth #5: Web Accessibility Overlays Decrease Legal Liability

    There’s a common myth floating around that adding a web accessibility overlay to your website will reduce your legal liability for not meeting accessibility standards. The idea is that if you just slap on an overlay, you’re covered, and you won’t have to worry about being sued for accessibility issues. Sounds tempting, right? Especially if you’re looking for a quick fix to avoid legal trouble.

    The Truth: Overlays Don’t Eliminate Legal Risks

    Here’s the reality: using an overlay doesn’t guarantee you’re legally safe. While overlays might help with some features, they don’t always meet legal requirements or ensure full compliance with laws like the ADA.

    Incomplete Compliance

    Overlays might improve some aspects, but they often miss key parts of accessibility, like keyboard navigation or dynamic content. If your site doesn’t fully meet accessibility standards, it can still be considered non-compliant. Legal requirements ensure all users, including those with disabilities, can access and use your website properly.

    Ongoing Legal Risk

    There were 933 lawsuits last year against websites using these so-called “accessibility solutions,” and the number is growing. This year, we’re on track for over 1,100 lawsuits against sites with these ineffective widgets. In the first half of 2024 alone, 503 lawsuits targeted sites with active widgets, making up 20% of all accessibility-related lawsuits this year.

    Overlays in Settlement Agreements

    Recently, many settlement agreements have made it clear that using overlay solutions like AudioEye, AccessiBe, and Accessibility Spark doesn’t meet compliance standards. This shows the need for strong accessibility measures integrated into your site’s design.

    Overlays Can Make You a Target

    Businesses using overlays are facing a rise in copycat lawsuits. Lawyers target companies with third-party widgets, knowing these tools often fall short. Tools like BuiltWith can show which websites use specific tools, making it easy to target sites with these solutions.

    Why Genuine Accessibility Practices Matter

    Web accessibility is about more than just meeting legal requirements—it’s about making your site usable for everyone. Genuine accessibility practices, like following WCAG guidelines, conducting manual audits, and testing with real users, ensure your site is accessible to people with various disabilities. This not only helps avoid legal problems but also improves your website for all users.

    To truly reduce legal risk and provide a better experience for all users:

    • Adopt Comprehensive Accessibility Standards: Follow guidelines like WCAG to meet all user needs through thoughtful design and development.
    • Conduct Regular Audits and Testing: Perform manual audits and usability testing with real users, especially those with disabilities, to find and fix issues that overlays might miss.
    • Continuous Improvement: Regularly update your site and re-evaluate your accessibility practices to keep up with new standards and user needs.

    Final Thoughts

    While web accessibility overlays might seem like a quick and easy fix for making your website compliant with the ADA, they’re far from a complete solution. Overlays often fall short in addressing complex accessibility issues, and relying solely on them can lead to incomplete compliance and even create new barriers for users. Genuine web accessibility requires a thoughtful approach that includes adhering to comprehensive standards like WCAG, conducting manual audits, and testing with real users.

    If you’re serious about making your website truly accessible and reducing legal risks, consider scheduling an ADA briefing with 216digital. Our experts can help you understand the full scope of accessibility requirements and develop a strategy that goes beyond quick fixes. With our guidance, you’ll ensure your site meets all necessary standards and provides an inclusive experience for everyone. Don’t leave your website’s accessibility to chance—contact 216digital today to get started on a path to genuine compliance and better user experience.

    Greg McNeil

    September 9, 2024
    Legal Compliance
    digital accessibility, Overlay, Overlay widgets, Web Accessibility
  • How to Make Your Blog Accessible to All Readers

    How to Make Your Blog Accessible to All Readers

    Creating a blog that’s accessible to everyone isn’t just good for your readers—it’s also a win for your website’s success. When we talk about web accessibility, we mean making sure that people of all abilities can access and understand your content. This includes individuals with disabilities who may use assistive technologies like screen readers. And there’s an added bonus: making your blog accessible can also improve your SEO (Search Engine Optimization), boosting your site’s visibility in search engines.

    In this guide, we’ll explore several steps to ensure your blog is accessible to everyone, with a focus on improving usability and optimizing it for search engines. Whether you’re a website owner, developer, or content creator, these practical tips will help you reach a wider audience and provide a better experience for all users.

    How Accessible Content Helps SEO

    Let’s start with the big question: How does making your blog accessible help with SEO? Search engines, like Google, favor websites that provide a better user experience, and accessibility plays a big role in this.

    When your blog is accessible, it’s easier for search engines to understand the content. Things like descriptive image alt text, structured headings, and meaningful links all give search engines more information about what’s on your page. This helps your content rank higher in search results. And since more people (including those with disabilities) can interact with your site, you’ll have a broader audience—another positive signal for SEO.

    By making your blog accessible, you’ll not only help people who rely on assistive technology, but you’ll also make your content easier to find for everyone. It’s a win-win!

    Use Headings to Convey Meaning and Structure

    One of the easiest ways to make your blog more accessible is by using headings properly. Headings help break up your content and make it easier to follow. But they’re more than just big, bold text—they’re essential for screen readers to understand the structure of a page (per WCAG 1.3.1).

    When you use headings (H1, H2, H3, etc.), you’re telling both readers and search engines what’s important on the page. Your main title should be an H1, and any subtopics should be in descending order of importance using H2s and H3s. For example, in this article, “Use Headings to Convey Meaning and Structure” is an H2 because it’s a main section, while smaller points could be H3s.

    Headings allow users to skim your blog and quickly find the information they’re looking for. This is especially helpful for readers using assistive technology, as screen readers rely on heading tags to navigate a webpage.

    Keep Content Clear and Concise

    Nobody likes wading through long, complicated paragraphs. Most people scan online content rather than reading it word-for-word. That’s why it’s important to keep your writing clear, concise, and easy to digest (per WCAG 3.1.5).

    Simple, straightforward language isn’t just good for accessibility—it’s good for your readers in general. If someone lands on your blog and can quickly understand the point you’re making, they’re more likely to stick around.

    This is especially true for people with cognitive disabilities who may have difficulty processing complex information. Break up your text into short paragraphs, use bullet points or numbered lists where appropriate, and avoid using jargon unless absolutely necessary.

    Remember: the clearer your content, the more accessible it is to everyone.

    Describe Your Images

    Images add visual interest to your blog posts, but they can create barriers if not handled properly. For people who are blind or have low vision, images need to be described in a way that makes sense with the content (per WCAG 1.1.1).

    That’s where alt text comes in. Alt text is a short description of an image that is read aloud by screen readers. It should be clear and concise, describing the image’s purpose in the context of your blog post. For example, if you have a picture of a dog in a blog about pet care, your alt text might say “Golden retriever lying on grass” rather than just “dog.”

    Good alt text is essential for both accessibility and SEO. Search engines can’t “see” images, but they can read alt text. By describing your images accurately, you’re helping both users and search engines understand your content better.

    Make Link Text Meaningful

    “Click here” is a common phrase you’ll see in blogs, but it’s not very helpful for accessibility or SEO. Instead, make your link text descriptive and relevant to the page it’s pointing to (per WCAG 2.4.4).

    For instance, instead of writing “Click here for more information,” you could write “Learn more about web accessibility.” This is more meaningful for readers and screen readers alike because it gives them an idea of what they’ll find when they click the link.

    Meaningful link text also helps with SEO because it gives search engines more context about the linked content. It’s another small tweak that can make a big difference in accessibility and search visibility.

    Check the Comment Form—Is It Labeled Properly?

    If you allow comments on your blog, it’s important to make sure your comment form is accessible. Many standard comment forms aren’t labeled properly, which can be a problem for people using screen readers (per WCAG 1.3.1).

    Check that each field (like “Name,” “Email,” and “Comment”) has a label that screen readers can read aloud. This will make it easier for everyone to interact with your blog, and it shows that you care about your entire audience’s experience.

    If you’re using a popular blogging platform like WordPress, there are plugins that can help ensure your forms are accessible. But it’s always a good idea to double-check that everything is labeled correctly.

    Use Flexible Font Sizes

    Another way to make your blog accessible is by using flexible font sizes. Not everyone has perfect vision, and some users may need to increase the font size to read your content comfortably (per WCAG 1.4.4).

    Make sure your blog’s text can be resized without breaking the layout or making the page hard to navigate. You can do this by using relative units like “em” or percentages instead of fixed pixel sizes. This way, readers can adjust the font size according to their preferences.

    In addition, choose fonts that are easy to read. Avoid overly decorative fonts and make sure there’s enough contrast between your text and background.

    Put Your Blogroll on the Right-Hand Side

    Placing your blogroll or navigation bar on the right-hand side of the page can improve accessibility. Many users with screen readers or keyboard navigation tools scan content from left to right. By placing the most important content (your actual blog post) on the left side and your blogroll or other navigation elements on the right, you make it easier for people to access what they came for (per WCAG 2.4.3).

    It’s a small change, but it can significantly enhance the usability of your blog for people using assistive technology.

    Conclusion

    Making your blog accessible isn’t just about being inclusive—it also helps with SEO and makes your site easier to use. By using clear headings, adding alt text to images, writing simply, and making sure your site is easy to navigate, you’ll make your blog better for everyone.

    Accessibility can be simple. With a few easy updates, you can make your blog a welcoming place for everyone, including people with disabilities. Not only will this improve your SEO and grow your audience, but it will also make your site more user-friendly.

    If you’re unsure where to start or want to make sure you’re on the right track, schedule an ADA briefing with 216digital. We’re here to help you make your blog accessible and successful!

    Greg McNeil

    September 5, 2024
    How-to Guides
    Content Writing, digital accessibility, How-to, SEO, Web Accessibility
  • What to Ask When Choosing a Partner for Title II ADA Compliance

    What to Ask When Choosing a Partner for Title II ADA Compliance

    When ensuring your organization’s compliance with ADA Title II, selecting the right partner to guide you through the process is crucial. ADA Title II mandates that state and local governments, as well as any of their departments, agencies, or other instrumentalities, must not discriminate against individuals with disabilities. Compliance with these regulations safeguards your organization against legal risks and ensures your services are accessible to all individuals. To make an informed decision when choosing a partner for ADA Title II compliance, here are key questions you should ask.

    Have You Worked with ADA Title III Compliance Before?

    ADA Title II compliance shares similarities with ADA Title III, which focuses on public accommodations provided by private entities. A partner with experience in ADA Title III compliance will have a solid understanding of accessibility requirements across different sectors. While Title II and Title III address various types of entities, the underlying accessibility principles remain consistent. A partner with experience in both areas will bring a comprehensive understanding of the legal landscape, helping you navigate the complexities of ADA compliance more effectively.

    How Well Do You Know WCAG 2.1 A/AA Standards?

    The Web Content Accessibility Guidelines (WCAG) 2.1 are the most widely recognized standards for digital accessibility. They provide a framework for making web content more accessible to people with disabilities, including those with visual, auditory, cognitive, and motor impairments. Ensuring your partner has an in-depth knowledge of WCAG 2.1 A/AA standards is crucial because these guidelines serve as the benchmark for evaluating your organization’s digital accessibility. A knowledgeable partner can guide you through implementing these standards, ensuring that your digital properties meet or exceed compliance requirements.

    How Skilled is Your Team in Accessibility?

    The expertise of the team working on your ADA compliance project is a critical factor in your success. Ask about the qualifications and experience of the team members handling your account. Do they have certifications in accessibility, such as Certified Professional in Accessibility Core Competencies (CPACC) or Web Accessibility Specialist (WAS)? How many years of experience do they have in the field? A skilled team with a deep understanding of accessibility can assure you that your project will be handled with the utmost care and expertise.

    What is Your Process for Conducting Accessibility Audits?

    An accessibility audit is the foundation of any compliance effort. It identifies areas where your organization falls short of ADA requirements and provides a roadmap for remediation. Ask potential partners to explain their audit process in detail. How thorough is their approach? Do they conduct both automated and manual testing? How do they document their findings?

    Understanding their process will give you insight into the level of detail and accuracy you can expect in their audit reports. A rigorous audit process is essential for identifying all accessibility issues and ensuring nothing is overlooked.

    How Do You Prioritize and Address Accessibility Issues?

    Not all accessibility issues are created equal. Some may have a significant impact on users with disabilities, while others may be less critical. A competent partner should have a clear strategy for prioritizing and addressing accessibility issues. Ask them how they determine which issues to tackle and how to address them. Do they focus on issues that have the most significant impact on user experience first, or do they take a different approach? Understanding their prioritization process will help you resolve the most pressing issues promptly, reducing the risk of non-compliance.

    What Testing Methods Do You Use?

    Testing is a critical component of ensuring ADA compliance. Ask your potential partner about the testing methods they use to evaluate accessibility. Do they rely solely on automated tools, or do they also conduct manual testing?

    Automated tools are excellent for identifying specific issues but can’t catch everything. Manual testing by individuals with disabilities provides valuable insights into how real users experience your digital content. A combination of both methods is ideal for a comprehensive assessment of your organization’s accessibility.

    How Will You Help Us Maintain Accessibility Over Time?

    Achieving ADA compliance is not a one-time effort; it’s an ongoing process. Your digital content will evolve, and new accessibility challenges may arise. Ask your potential partner how they plan to help you maintain accessibility over time. Do they offer ongoing monitoring services to ensure your digital properties remain compliant as updates are made? How do they stay up to date with changes in accessibility standards and regulations? A partner committed to long-term support will help you remain compliant and avoid potential legal pitfalls in the future.

    What Technology and Tools Do You Use for Accessibility?

    The tools and technology your partner uses can significantly impact the effectiveness of their accessibility efforts. Ask about the specific tools they use for auditing, testing, and remediation. Do they use industry-standard tools such as WAVE or JAWS? How do they leverage these tools to identify and resolve accessibility issues? Additionally, ask about any proprietary tools they may have developed. A partner with advanced technology and tools will be better equipped to handle complex accessibility challenges and deliver effective solutions.

    Do You Offer Training?

    Training is a vital component of sustaining ADA compliance. Your staff needs to be educated on accessibility best practices to ensure your digital content remains compliant as it evolves. Ask your potential partner if they offer training services. Do they provide customized training sessions tailored to your organization’s needs? Do they offer resources and support for your team to continue learning about accessibility?

    A partner who offers comprehensive training will empower your organization to maintain accessibility independently, reducing the need for constant external intervention.

    Conclusion

    Choosing the right partner for ADA Title II compliance is a crucial decision that can have long-lasting implications for your organization. By asking the right questions, you can ensure that your partner has the expertise, experience, and resources needed to guide you through the complexities of ADA compliance. A knowledgeable and skilled partner will help you achieve and maintain compliance, mitigating legal risks and ensuring that your services are accessible to all individuals, regardless of their abilities. Prioritize partners who demonstrate a deep understanding of accessibility, a commitment to ongoing support, and a comprehensive approach to testing and remediation.

    At 216digital, we specialize in helping organizations like yours successfully navigate ADA compliance with expert guidance, tailored solutions, and ongoing support. Schedule an ADA compliance briefing with our team today to learn how we can help you stay ahead of regulations, reduce legal risks, and build an inclusive digital experience. Let’s work together to ensure your organization meets and exceeds accessibility standards.

    Kayla Laganiere

    September 4, 2024
    Testing & Remediation
    ADA Compliance, ADA Website Compliance, digital accessibility, Title II, Web Accessibility
  • The Legal Pitfalls of Web Accessibility Overlays

    The Legal Pitfalls of Web Accessibility Overlays

    Web accessibility overlays have been popping up everywhere, promising to make websites accessible with just a quick fix. These tools, often marketed as a simple solution, claim to solve accessibility issues with just a few clicks. But are they really the answer? Unfortunately, relying on an overlay might not be the quick fix it seems. Instead, it could lead to even more problems down the road, including legal trouble. Let’s take a closer look at what overlays are and the risks involved depending on them.

    What Are Web Accessibility Overlays?

    First, let’s break down what web accessibility overlays actually are. Overlays are tools that use a snippet of JavaScript to change a website’s code. They often come in the form of toolbars, plugins, apps, or widgets. These overlays claim to detect and fix accessibility problems on a website automatically. However, they don’t actually fix the website’s original source code. Instead, they identify basic accessibility issues, like color contrast and text size, and make adjustments. While these features are important for accessibility, the real issue is how overlays are used and depended upon.

    The Legal Landscape: Recent Lawsuits and Challenges

    Now that you know what overlays are and what they aim to do, let’s dive into the legal implications surrounding their use. In recent years, web accessibility overlays have faced growing scrutiny in U.S. courts. You might have heard about the recent class action lawsuit against accessiBe—one of the most popular accessibility widget providers. If you haven’t, this could be a game-changer for you.

    Case Study: Tribeca Skin Care vs. accessiBe

    On June 24, 2024, Tribeca Skin Care, a small dermatology practice in New York City, filed a class action lawsuit against accessiBe. Even though Tribeca used accessiBe’s overlay, a blind person still sued the practice, claiming their website didn’t meet ADA requirements. This case clearly shows the serious risks of relying solely on these tools for web accessibility.

    Problems and Risks with Overlays

    So, what’s the problem? Overlays like accessiBe promise to fix accessibility issues with just a few lines of code. But in reality, they can sometimes create new barriers instead of removing them. As we look at more legal cases, it becomes evident that courts are increasingly siding with plaintiffs who argue that these overlays aren’t a real substitute for having accessibility built directly into a website’s code. By mid-2024, over 20% of web accessibility lawsuits were filed against companies using these widgets. This raises a big question: Can overlay vendors really deliver the protection from lawsuits or the ADA compliance they promise?

    Copycat Lawsuits: A Growing Threat

    To make things even more challenging, businesses using overlays are now facing a new wave of copycat lawsuits. These lawsuits come from a new wave of ambulance chasers targeting companies that rely on third-party overlays. They know these tools often fall short of providing true accessibility. Tools like BuiltWith make it easy for anyone to see what a website is built with. With just a click, you can access a full list of websites using a specific tool—like AccessiBe or another accessibility overlay.

    Exploitation of Overlay Data

    What are the chances that these serial lawsuit-filing firms are using data like this to find new targets? Especially when they see success in filing lawsuits or sending demand letters against websites using overlays.

    The legal argument is straightforward: if an overlay doesn’t fully meet accessibility standards, then the website is still not compliant with the Americans with Disabilities Act (ADA) and other regulations. As a result, businesses that thought they were protecting themselves with an overlay end up in court, dealing with expensive settlements and damage to their reputation.

    Why Overlays Aren’t a Solution

    So, why are overlays so problematic? The answer lies in their limitations. Overlays are designed to be a one-size-fits-all solution, but accessibility needs are diverse and complex. No single tool can address every issue, especially when it comes to accommodating users with different types of disabilities. For instance, while an overlay might help someone with mild visual impairments by adjusting contrast, it can’t add quality alt-text to images, or ensure that you’re using descriptive link text, for example.

    Additionally, overlays are often implemented as a quick fix rather than a comprehensive solution. This can lead to a false sense of security, where businesses believe they are fully compliant with accessibility laws when, in reality, they are not. This false confidence can backfire when a lawsuit reveals the shortcomings of the overlay, leading to financial and legal repercussions.

    What Can Business Owners Do Instead?

    Given the risks associated with overlays, what should business owners do instead to ensure their websites are accessible? The answer lies in taking a proactive and comprehensive approach to web accessibility. Here are some steps to consider:

    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 informed about any changes and make updates to your website as necessary to remain compliant.
    5. Ongoing Monitoring: Compliance is not a one-time task with 216digital’s a11y.Radar service provides ongoing monitoring of your website or app to detect any new accessibility issues that may arise over time. This proactive approach helps prevent potential violations before they lead to costly lawsuits.

    Overlays Are Not a Shortcut

    Web accessibility overlays might appear to be a quick solution, but they come with significant legal risks. Recent lawsuits have demonstrated that these tools often fall short of meeting the required standards, leaving businesses exposed to potential legal issues. Instead of opting for an overlay, invest in a comprehensive approach to web accessibility. By integrating accessibility from the ground up, you can avoid the pitfalls of overlays and ensure that your site is genuinely welcoming and usable for all visitors.

    True accessibility is about more than just sidestepping legal troubles—it’s about creating a web experience that everyone can use and enjoy. Don’t settle for a temporary fix. Invest in building a fully accessible website that serves all users effectively.

    Team Up with 216digital

    Ready to take the next step? Whether you want to protect against a frivolous ADA accessibility lawsuit or become WCAG 2.1 AA compliant, 216digital has you covered. Our team of accessibility experts can also develop strategies to integrate WCAG 2.1 compliance into your development roadmap on your terms. 

    Don’t wait for a lawsuit to push you into action. Schedule a complimentary ADA strategy briefing with 216digital to take the first step toward website accessibility.

    Greg McNeil

    September 3, 2024
    Legal Compliance
    ADA Compliance, digital accessibility, Overlay, Overlay widgets, Web Accessibility
  • Why Your Navigation Menu Needs Accessibility

    When you visit a website, one of the first things you probably notice is the navigation menu. It’s usually at the top or on the side of the page, guiding you to different parts of the site. Think of it as the roadmap to all the good stuff a website has to offer. But what happens if that roadmap isn’t clear? This is where accessible navigation menus come into play.

    Let’s dive into what a web navigation menu is, common accessibility challenges, why they matter, and how you can make yours more accessible!

    What is a Website Navigation Menu & Structure?

    A navigation menu is a list of links or buttons usually found at the top or side of a website. These links guide users to different sections of the site, like the homepage, about page, blog, or contact page. Think of it as a roadmap that helps visitors get where they want to go without wandering aimlessly.

    The structure of a navigation menu can vary from simple to complex, depending on the size and type of website. Most websites use one or more of these types of menus:

    • Horizontal Menus: Commonly found at the top of a webpage.
    • Vertical Menus: Often located on the left or right side of a webpage.
    • Dropdown Menus: This appears when you hover over or click a menu item.
    • Hamburger Menus: Those three stacked lines you see on mobile websites or apps.

    The structure needs to be clear and intuitive so users can find what they’re looking for quickly and easily. For example, if you’re on an online store’s website, you’d expect to find “Products” in the main menu, not buried under “About Us.”

    When the navigation is well-organized, visitors can explore your site and enjoy their experience. But if it’s confusing or hard to use, people might leave — and that’s not good for any website.

    Common Accessibility Challenges with Navigation Menus

    Creating a navigation menu might seem simple, but there are a few common accessibility challenges that can make it tricky for some users to navigate. Here are a few examples:

    • Keyboard Navigation: Not everyone uses a mouse. Some people rely on a keyboard or other assistive devices to move around a website. If your menu isn’t keyboard-friendly, it can be impossible for these users to access parts of your site.
    • Screen Readers: Screen readers are tools that help people with visual impairments by reading the text on the screen out loud. If your menu isn’t designed with screen readers in mind, it might not make sense to the user.
    • Color Contrast: If the text in your menu doesn’t have enough contrast with the background, it can be hard for people with visual impairments to read. For example, light gray text on a white background might look sleek, but it’s not easy for everyone to see.
    • Dropdown Menus: Dropdown menus are those extra links that appear when you hover over a main menu item. They can be challenging for screen readers and keyboard users if not properly coded.

    Why Are Accessible Navigation Menus Important?

    Accessible navigation menus aren’t just about being kind or doing the right thing—they’re also good for business. When your site is accessible, it’s usable by everyone, including people with disabilities. This means you’re not excluding potential customers or visitors, which can lead to a better return on investment (ROI).

    Additionally, accessibility is a legal requirement under the Americans with Disabilities Act (ADA) in the United States. Websites that don’t comply with these guidelines can face lawsuits, which can be costly and damage your brand’s reputation.

    Simply put, investing in web accessibility isn’t just good ethics—it’s good business.

    Features of an Accessible Navigation Menu

    To make sure your navigation menu is accessible, you should include several features. These features align with Web Content Accessibility Guidelines (WCAG), the go-to standards for web accessibility.

    1. Keyboard Accessibility (WCAG 2.1.1 – Keyboard Accessible):

    Keyboard accessibility is one of the most critical aspects of web accessibility. Some users may not be able to use a mouse due to motor disabilities, repetitive strain injuries, or personal preference. For these users, navigating a website entirely via the keyboard is essential. Here’s how you can make your navigation menu keyboard-friendly:

    • Tab Order: Ensure that users can navigate through all menu items using the Tab key. The order should be logical and follow the visual flow of the website.
    • Enter and Arrow Keys: When a menu item has a dropdown, users should be able to expand or collapse it using the Enter or Arrow keys. Once expanded, users should be able to navigate through the submenu items using the Arrow keys.
    • Focus Management: Users should always know where they are on the page. Make sure that when a user opens a dropdown, the focus shifts to the first item in that dropdown.

    Here’s an example of how you can make a simple navigation menu keyboard accessible:

    <nav>
      <ul>
        <li><a href="#home" tabindex="0">Home</a></li>
        <li><a href="#about" tabindex="0">About</a></li>
        <li><a href="#services" tabindex="0">Services</a></li>
        <li><a href="#contact" tabindex="0">Contact</a></li>
      </ul>
    </nav>

      

    2. Visible Focus Indicator (WCAG 2.4.7 – Focus Visible):

    Focus indicators show users where they are on a webpage when they navigate using a keyboard. Without a visible focus indicator, users can get lost, particularly if they are relying solely on the keyboard. The WCAG guidelines require that the focus indicator be clearly visible when users navigate through menu items.

    Styling Focus Indicators

    Customize the default focus style to make it more visible. You can use CSS to create a more prominent outline or make a background change. For example:

    a:focus {
      outline: 3px solid #ff9800; /* Orange border for focused links */
      background-color: #f0f0f0; /* Light gray background for contrast */
    }

      

    Accessible Color Choices

    Ensure that the color of the focus indicator has enough contrast with the background to be easily noticeable.

    3. ARIA Roles and Attributes (WCAG 4.1.2 – Name, Role, Value):

    ARIA (Accessible Rich Internet Applications) roles and attributes provide extra information to assistive technologies like screen readers, helping users understand the purpose and state of navigation elements. This is especially important for menus that have complex structures, such as dropdowns.

    ARIA Roles

    Use roles like role= “navigation” to indicate the navigation region and role= “menu” or role= “menuitem” to define menus and items within them. For example:

    <nav role="navigation" aria-label="Main Navigation">
      <ul role="menubar">
        <li role="none"><a href="#home" role="menuitem">Home</a></li>
        <li role="none"><a href="#about" role="menuitem">About</a></li>
        <!-- Other menu items -->
      </ul>
    </nav>

    ARIA Attributes for State

    Use aria-expanded to indicate if a dropdown is expanded or collapsed. This helps users who rely on screen readers understand whether they can interact further with the menu item.

    <button aria-expanded="false" aria-controls="submenu">Services</button>
    <ul id="submenu" role="menu">
      <li role="none"><a href="#design" role="menuitem">Design</a></li>
      <li role="none"><a href="#development" role="menuitem">Development</a></li>
    </ul>

    When the button is clicked to expand the menu, JavaScript should change aria-expanded= “true”.

    4. Color Contrast (WCAG 1.4.3 – Contrast (Minimum)):

    Ensuring sufficient color contrast is vital for users with visual impairments, including color blindness. The contrast ratio between the text and its background should be at least 4.5:1 for normal text and 3:1 for large text.

    • Choosing Accessible Colors: Use online tools like the WebAIM Contrast Checker to ensure your menu items meet the WCAG color contrast standards.
    • Avoid Low-Contrast Hover States: While hover effects can be helpful, make sure they don’t reduce the text’s visibility. For example, avoid light text on light backgrounds.

    5. Responsive and Mobile-Friendly Design (WCAG 1.4.10 – Reflow):

    Navigation menus must be accessible across different devices and screen sizes. This is especially important given the widespread use of mobile devices.

    • Responsive Design Techniques: Ensure that the menu collapses into a mobile-friendly version, like a hamburger menu, without losing accessibility features.
    • Mobile Screen Readers: Make sure mobile screen readers can read and navigate the menu. Test with VoiceOver on iOS and TalkBack on Android to ensure compatibility.

    6. Skip Navigation Links (WCAG 2.4.1 – Bypass Blocks):

    A “Skip to Content” link allows users to bypass repetitive navigation links and go straight to the main content. This is crucial for users who rely on keyboard navigation.

    <a href=”#maincontent” class=”skip-link”>Skip to Content</a>

    When the page loads, users can press Tab to immediately focus on this link, skipping the menu altogether.

    7. Clear and Descriptive Labels (WCAG 3.3.2 – Labels or Instructions):

    Menu items should be labeled clearly to describe what users can expect when they click on them. This reduces confusion and ensures all users, including those with cognitive disabilities, can easily navigate the site.

    • Avoid Vague Labels: Instead of “Explore,” use something like “Our Services” to make it clearer what users will find.

    Tips for Creating an Effective Accessibility Navigation Menu

    Creating an accessible navigation menu isn’t just about meeting the guidelines—it’s about creating a better experience for everyone. Here are some tips to help:

    1. Keep it Simple: A clear and straightforward menu structure is easier for all users to navigate.
    2. Use Clear Labels: Avoid jargon and use common terms. For example, instead of “Explore Our Solutions,” just use “Services.”
    3. Include Skip Links: A “Skip to content” link allows keyboard users to skip repetitive navigation links.
    4. Test with Real Users: Get feedback from people with different disabilities to understand how accessible your menu really is.
    5. Provide Descriptive Anchor Text: Use anchor text that tells users where they’re going. For example, use “About Us” instead of “Click Here.”

    Testing for an Accessible Menu

    Once you’ve built your navigation menu, you need to test it for accessibility. Here are a few ways to do that:

    • Keyboard Navigation: Try navigating your site using only the keyboard. Can you access all the menu items? Are dropdowns easy to use?
    • Screen Readers: Use a screen reader like NVDA (NonVisual Desktop Access) or JAWS (Job Access With Speech) to navigate your site. Does the menu make sense when read aloud?
    • Color Contrast Tools: Use color contrast checkers to make sure your text stands out against the background.
    • Real User Testing: Consider asking users with disabilities to test your site and provide feedback on the navigation menu. This real-world input can be invaluable.

    Conclusion

    Creating a web-accessible navigation menu isn’t just about checking a box; it’s about making your website easy for everyone to use. When you improve accessibility, you also boost user experience and even your ROI. By learning about the best practices and challenges of accessible navigation menus, you can make your website more welcoming to all visitors.

    Remember, accessibility is not a one-time fix. It’s important to regularly test and update your navigation menu to keep it user-friendly. If you want to take the next step in making your website more inclusive, consider scheduling an ADA compliance briefing with 216digital. Our team can help you ensure your site is accessible to everyone.

    Greg McNeil

    August 30, 2024
    How-to Guides
    digital accessibility, How-to, navigation menu, Web Accessibility, web development
  • Understanding HB 21-1110: Colorado’s Web Accessibility Law

    Colorado has always been a leader in creating inclusive policies, and it was one of the first states to make web accessibility a law.

    On July 1, 2021, House Bill 21-1110 was passed, outlining clear steps for state agencies and other organizations to ensure their websites and communication platforms are accessible to everyone.

    So, what does this mean for you? How can you tell if this law affects you? And what does it mean to meet WCAG 2.1 at Level AA?

    Understanding these questions is important—not just because it’s a legal requirement, but also to make sure everyone, including people with disabilities, can access digital content. This guide will explain everything you need to know about complying with HB 21-1110 and making your digital content accessible.

    What is House Bill 21-1110?

    House Bill 21-1110 is a major law in Colorado that requires all state and local government websites to follow digital accessibility standards. Signed by Governor Jared Polis on June 30, 2021, this bill builds on the Americans with Disabilities Act (ADA) and gives the Chief Information Officer (CIO) of the Office of Information Technology (OIT) a key role in making sure these standards are met.

    One of the biggest changes with this bill is that people can now file accessibility lawsuits not only in federal courts but also in state courts. This means more opportunities to challenge government websites that aren’t meeting accessibility standards.

    The Deadline for Compliance

    House Bill 21-1110 set a deadline of July 1, 2024, for all state and local government websites in Colorado to meet WCAG 2.1 Level AA standards for digital accessibility. The CIO is responsible for creating guidelines based on the latest Web Content Accessibility Guidelines (WCAG).

    If government agencies don’t meet these standards by the deadline, they could face legal action from individuals with disabilities who can now file suits directly in Colorado state courts. This bill impacts over 4,000 local government entities in Colorado, pushing them to make web accessibility a priority.

    Extension Grant Introduced in May 2024

    In May 2024, Colorado introduced an extension for some government entities that might not meet the July deadline. These agencies could extend their compliance deadline until July 2025, but they had to show a good-faith effort toward meeting digital accessibility standards by July 19, 2024. This includes:

    • Creating a detailed progress report on their websites and updating it quarterly.
    • Providing an easy-to-find way for visitors to report accessibility issues, with clear contact information on public-facing pages.

    Who Does HB 21-1110 Apply To?

    HB 21-1110 applies to all state and local government entities in Colorado, including:

    • State agencies
    • Local governments (cities and counties)
    • Content owners managing government websites

    Any public entity providing digital services or information must comply, ensuring that people with disabilities can access government resources.

    What About Non-Government Entities?

    Currently, HB 21-1110 only applies to government websites. However, if you run a private business, you may still need to follow the ADA. Many U.S. courts apply the ADA to websites and use WCAG as the standard for web accessibility. It’s a good idea to make sure your site is accessible.

    How Can You Know if Your Website is Compliant with HB 21-1110?

    To comply with HB 21-1110, websites need to be audited for digital accessibility. This means checking the site’s content, structure, and design against WCAG 2.1 Level AA standards. While automated tools can help, it’s best to work with digital accessibility experts who can catch issues automated tools might miss, like keyboard navigation or color contrast problems.

    After the audit, you’ll need to make updates, such as adding alt text to images, captioning videos, improving content structure, and enhancing form navigation.

    Steps to Ensure HB 21-1110 Compliance

    Here’s a simple guide to help you comply with House Bill 21-1110:

    1. Conduct a Website Audit: Check your site against WCAG 2.1 Level AA standards, focusing on readability, navigation, and multimedia accessibility. Consulting with a specialist firm like 216digital to conduct a thorough audit can also be a wise investment.
    2. Develop a Remediation Plan: Create a plan based on your audit to address the most pressing accessibility issues.
    3. Make Necessary Updates: Work with a web development team or hire accessibility experts to implement fixes like adding alt text or improving keyboard navigation.
    4. Test for Compliance: After updates, test your site again to ensure it meets the standards. It’s also helpful to get feedback from users with disabilities.
    5. Monitor Accessibility Regularly: Keep auditing your site as you add new content or make changes to ensure continued compliance. 216digital’s a11y. Radar service provides ongoing monitoring of your website or app to detect any new accessibility issues that may arise over time. This proactive approach helps prevent potential violations before they lead to costly lawsuits.
    6. Train Your Staff: Ensure your team understands how to create accessible content, such as writing proper alt text and making PDFs accessible.

    What Are the Consequences of Non-Compliance?

    If a government entity doesn’t meet the OIT’s digital accessibility standards, it could face:

    • Court orders
    • Monetary damages
    • Fines of $3,500 per violation
    • Loss of funding
    • Public backlash

    To avoid these penalties, it’s crucial to take action now. If you haven’t started working toward compliance, now is the time to focus on digital accessibility.

    Conclusion

    While House Bill 21-1110 currently applies only to state and local governments, private businesses should be proactive about preparing for future changes in digital accessibility requirements. If your business falls under Title III, now is a great time to schedule an ADA briefing with 216digital. Staying ahead of digital accessibility standards will help protect your business and ensure your website is accessible to all. Don’t wait Don’the laws to catch up—start planning today!

    Kayla Laganiere

    August 29, 2024
    Legal Compliance
    digital accessibility, HB 21-1110, House Bill 21-1110, Web Accessibility
  • Senators Push for Section 508 Update

    In recent news, U.S. senators have advocated for an update to Section 508, a vital law ensuring federal websites and digital resources are accessible to all individuals, particularly those with disabilities. But why does this matter to you as a website owner, developer, or content creator? Let’s break down what Section 508 is, why web ADA compliance matters, and how an update could reshape the digital accessibility landscape.

    What is Section 508?

    Section 508, part of the Rehabilitation Act of 1973, is a law focused on barriers for people with disabilities. In 1998, when the internet became crucial in everyday life, Section 508 was updated to require federal government entities to make their digital services accessible to people with disabilities. Section 508 guides everything from websites and apps to PDFs and videos.

    At its core, Section 508 ensures that government websites and digital content are navigable and usable for individuals with disabilities. Some examples of accessibility improvements are implementing features like screen readers for visually impaired users, captioning for those with hearing impairments, or ensuring that people with motor disabilities can navigate websites using only a keyboard.

    Check out our article “A Closer Look at Section 508” for more info on Section 508.

    What is Web ADA Compliance?

    While Section 508 applies specifically to federal agencies, it overlaps with the Americans with Disabilities Act (ADA), particularly when it comes to website accessibility. The ADA, enacted in 1990, requires public accommodations (including businesses and organizations) to be accessible to people with disabilities. Although the ADA doesn’t mention websites, courts have increasingly interpreted its provisions to apply to the digital world.

    Now, let’s introduce web ADA compliance. Website owners, especially businesses, are increasingly expected to ensure their digital spaces are as accessible as their physical ones. Some examples of accessibility improvements include ensuring websites meet specific standards, such as providing text descriptions for images (alt text), creating keyboard-friendly navigation, and ensuring that users can zoom in on text without losing content functionality.

    If your website isn’t compliant, you may be at risk of legal action, not to mention alienating potential customers or clients who are unable to access your site.

    Why the Push for an Update to Section 508?

    The internet and technology have evolved significantly since 1998, and while Section 508 has received updates over the years, many argue that it still falls short when ensuring comprehensive digital accessibility. A U.S. Government Accountability Office report found that 48% of federal websites still fail to meet basic accessibility standards.

    This failure highlights the growing need for more robust, precise guidelines reflecting the rapidly changing digital landscape. U.S. Senators Bob Casey (D-PA), Chairman of the U.S. Senate Special Committee on Aging, Ron Wyden (D-OR), Chairman of the U.S. Senate Finance Committee, John Fetterman (D-PA), and Tammy Duckworth (D-IL) are advocating for an update to Section 508. They are pushing for modernized standards that consider the latest web technologies and accessibility tools in the Section 508 Refresh Act.

    For example, the original guidelines didn’t account for mobile devices or advanced multimedia content, now everyday parts of online experiences. By updating Section 508, the government hopes to set a more potent example for digital accessibility that private sector websites can follow.

    Section 508 Refresh Act Proposed Updates

    The Section 508 Refresh Act will bring much-needed updates to the law. Here’s what the bill will do:

    • Involve People with Disabilities: Federal departments and agencies will now have to include people with disabilities—both as users of government services and information, and as government employees—in the process of acquiring and testing federal technology for accessibility.
    • Improve the Complaint Process: The act will reform how complaints under Section 508 are handled and set up a new process for deciding which federal technology gets purchased, with strict accountability to ensure the technology is accessible.
    • Require Regular Testing: Federal departments and agencies will need to regularly test their technology to make sure it’s accessible to both federal workers and all Americans who use federal programs and information.
    • Appoint Compliance Officers: Each federal department and agency will be required to have qualified, dedicated Section 508 compliance officers to ensure the technology they buy and use is accessible.

    How Does Section 508 Affect Your Website?

    Although Section 508 primarily applies to federal agencies, its standards can serve as a guideline for businesses and organizations striving to meet web ADA compliance. Here’s how the push for a Section 508 update could affect website owners like you:

    Rising Accessibility Expectations

    The conversation around digital accessibility is growing, and consumers are becoming more educated about their rights. A more substantial Section 508 could raise the bar for accessibility standards, creating a ripple effect in the private sector. While your business may not be legally bound by Section 508, failing to meet modern accessibility standards can cause a loss of revenue and costly legal engagements.

    Avoiding Legal Risks

    Over the past few years, ADA-related website lawsuits have increased. Big and small businesses have received expensive lawsuits for not providing accessible websites. An update to Section 508 could bring more attention to web ADA compliance, meaning your business might face heightened scrutiny. To protect yourself, it’s a good idea to stay ahead of any legal requirements by ensuring your website is accessible to all. 216digital offers complimentary ADA risk assessments.

    Improving Usability for All Users

    Let’s face it: accessibility isn’t just about meeting legal standards. It’s about making your website better for everyone. When your website is accessible, it’s easier to navigate, more user-friendly, and more likely to attract a wider audience. An update to Section 508 could bring more explicit guidelines and tools that can help website owners like you make necessary improvements to usability.

    What Does Digital Accessibility Look Like?

    Now that you understand why the push for a Section 508 update is essential let’s dive into what digital accessibility looks like. Ensuring your website is accessible means implementing changes that benefit users with disabilities, including those who are blind, deaf, or have mobility impairments. However, these changes often improve the experience for all users.

    Here are a few key accessibility features to consider for your website:

    Alt Text for Images

    People using screen readers rely on descriptive text for images to understand the content on the page. Someone visually impaired would only know what the image is about with alt text. Adding alt text for images isn’t just a best practice for accessibility—it’s also good for SEO, helping your images rank better in search engines.

    Keyboard Navigation

    Not all users can use a mouse. Many people with mobility impairments rely on keyboard navigation to move through websites. Testing for keyboard navigability (with features like tabbing and clear focus indicators) is critical for accessibility.

    Captioning for Videos

    People who are deaf or hard of hearing rely on captions to understand video content. Providing captions for all videos on your site is a must for web ADA compliance. Fortunately, many video platforms, like YouTube, offer automated captioning services that you can edit to improve accuracy.

    Text Resizing

    For users with low vision, being able to zoom in on text is essential. Test your site by zooming pages to 200% and ensure your content adjusts accordingly without breaking the layout. Text resizing is especially important for mobile users who often zoom in to read content on small screens.

    Readable Fonts and Colors

    Some users need help with reading specific fonts or color combinations. Use simple, easy-to-read fonts and ensure adequate contrast between text and background colors. Contrast improvements will help users with vision impairments and make your website more accessible to read for everyone.

    What Can You Do as a Website Owner?

    With all this in mind, what steps can you take to ensure your website meets digital accessibility standards and remains web ADA compliant?

    Run an Accessibility Audit

    Several online tools, such as 216digital’s Accessibility Radar, can help you identify accessibility issues on your website. By running an audit, you’ll see where your site falls short and what areas need improvement.

    Learn About WCAG

    The Web Content Accessibility Guidelines (WCAG) is the gold standard for digital accessibility. Familiarizing yourself with WCAG 2.2, the latest version, can be a guideline for site improvements. These guidelines cover everything from text alternatives for non-text content to ensuring your site is compatible with assistive technologies.

    Work with an Accessibility Expert

    If you’re unsure how to start or need help making significant changes, consider hiring an accessibility experts like 216digital. They can help ensure your website meets Section 508 and web ADA compliance standards, reducing your risk of legal issues and improving your overall user experience.

    Regularly Update Your Site

    Web accessibility requires ongoing maintenance. As your site grows and changes, continually check for accessibility issues. Whether adding new content, launching a redesign, or building new features, accessibility should always be a priority.

    Stay Ahead of the Game

    With senators pushing for an update to Section 508, there’s never been a better time to focus on digital accessibility. Not only will improving your website’s accessibility help you avoid legal risks, but it will also create a better experience for all users. Staying on top of accessibility trends and best practices is essential for any website owner, developer, or content creator. So take the time now to ensure your site is accessible—it’s not just the right thing to do; it’s good business.

    Schedule a complimentary ADA Strategy Briefing to talk with one of our accessibility experts and take the next step with confidence into web accessibility.

    Greg McNeil

    August 28, 2024
    Legal Compliance
    digital accessibility, Section 508, Web Accessibility, web compliance, Website 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
  • Understanding the Limitations for Unruh Act

    Understanding the Limitations for Unruh Act

    The Unruh Civil Rights Act (Unruh Act) is a critical piece of California legislation that ensures everyone is entitled to full and equal accommodations, advantages, facilities, privileges, or services in all business establishments. Initially passed in 1959, it is a cornerstone of California’s commitment to prohibiting discrimination based on sex, race, color, religion, ancestry, national origin, disability, medical condition, genetic information, marital status, or sexual orientation.

    With the increasing number of online transactions and the expansion of e-commerce, there has been a notable rise in Unruh Act claims related to web accessibility, making it more important than ever for businesses to understand their legal obligations.

    Expansion to Online Businesses

    While the act initially focused on physical spaces like hotels, restaurants, and stores, its application has expanded to cover online businesses. Many online businesses, particularly those that have recently moved into the digital space, may not fully realize that their websites and apps are considered ‘places of public accommodation’ under the Unruh Act. This oversight can lead to unintentional violations and subsequent legal action.

    Common Scenarios for Unruh Act Claims

    Businesses that fail to comply with the Unruh Act can face serious legal consequences. The act allows individuals who have experienced discrimination to file lawsuits against offending businesses. In recent years, one of the most prominent areas of litigation under the Unruh Act has been web accessibility. Here’s a closer look at a landmark case:

    Robles v. Domino’s Pizza

    One of the most notable cases involving the Unruh Act is Robles v. Domino’s Pizza. In this case, Guillermo Robles, a blind man, sued Domino’s Pizza, claiming that the company’s website and mobile app were inaccessible to visually impaired users who rely on screen readers. Robles argued that this lack of accessibility violated both the Americans with Disabilities Act (ADA) and the Unruh Act.

    The case eventually made its way to the Ninth Circuit Court of Appeals, which ruled in favor of Robles. The court affirmed that websites and mobile apps are considered places of public accommodation under both the ADA and the Unruh Act.

    The Robles case has set a significant precedent, leading to increased scrutiny of businesses’ digital accessibility efforts. Since this ruling, numerous lawsuits have been filed against companies that fail to provide accessible online services, highlighting the importance of proactive compliance.

    Statute of Limitations for Unruh Act Claims

    In legal terms, the statute of limitations is a set period during which a person must file a lawsuit or claim after an event occurs. It helps protect both sides: the person bringing the case (plaintiff) and the person being sued (defendant). This time limit ensures that cases are addressed in a reasonable amount of time and prevents legal actions from dragging on forever.

    Timeframes for Filing Claims

    In California, the timeframe for filing a claim under the Unruh Act depends on how the claim is handled.

    • Through the California Civil Rights Department (CRD): If a plaintiff wants to file a claim through the CRD, they must do so within one year from the date of the alleged discrimination.
    • Privately: If the claim is filed privately, not through the CRD, the timeframe extends to two years from the date of the discriminatory act.

    Consequences of Missing the Deadline

    Missing the statute of limitations for an Unruh Act claim can have significant consequences. For plaintiffs, it means the loss of the opportunity to seek compensation for the harm they have suffered. This could include financial damages and the chance to force a business to change its discriminatory practices.

    Missing the deadline does not absolve businesses of the underlying issue. While they may avoid a particular lawsuit, the continued failure to comply with the Unruh Act leaves them vulnerable to future claims. Moreover, the reputational damage associated with non-compliance can negatively impact customer trust and loyalty.

    It’s also worth noting that businesses that repeatedly fail to comply with the Unruh Act may become targets for serial litigants—individuals who seek out violations specifically to file lawsuits. This can result in multiple lawsuits, leading to substantial legal fees, settlements, and other costs.

    Protecting Your Online Business

    Given the complexities and potential risks associated with the Unruh Act, online businesses must take proactive steps to ensure compliance. This is where partnering with a knowledgeable and experienced firm like 216digital can make a significant difference.

    216digital’s Accessibility Services

    At 216digital, we specialize in web accessibility and compliance services designed to protect businesses from the legal risks associated with the Unruh Act and other similar regulations. Our comprehensive approach includes:

    • Accessibility Audits: We conduct thorough accessibility audits of your website or app to identify potential issues that could lead to Unruh Act claims. Our audits cover both automated and manual testing methods to ensure that all aspects of accessibility are addressed.
    • Remediation Services: Once issues are identified, we provide expert remediation services to bring your digital properties into compliance. This includes making necessary code changes, optimizing for assistive technologies, and ensuring all content is accessible.
    • Ongoing Monitoring: Compliance is not a one-time task with 216digital’s a11y.Radar service provides ongoing monitoring of your website or app to detect any new accessibility issues that may arise over time. This proactive approach helps prevent potential violations before they lead to costly lawsuits.
    • Consulting and Training: We offer consulting services to help your team understand the requirements of the Unruh Act and other accessibility laws. Additionally, we provide training to ensure your team maintains compliance as you update and expand your digital presence.

    By partnering with 216digital, you can protect your business from the risks of Unruh Act claims and demonstrate your commitment to inclusivity and accessibility, which can enhance your brand reputation and customer loyalty.

    Wrapping Up

    The Unruh Civil Rights Act is a powerful tool for protecting the rights of individuals in California, and its application to online businesses underscores the importance of web accessibility. Understanding the limitations of the Unruh Act, including the statute of limitations for filing claims, is essential for both individuals seeking to enforce their rights and businesses aiming to avoid legal pitfalls.

    For businesses, the best defense against Unruh Act claims is a proactive approach to web accessibility. By working with an expert partner like 216digital, you can ensure that your online presence fully complies with the law, protecting your business from legal risks while enhancing the user experience for all visitors.

    Greg McNeil

    August 26, 2024
    Legal Compliance
    digital accessibility, Unruh Act, Unruh Civil Rights Act, Web Accessibility, Website Accessibility
Previous Page
1 2 3 4
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.