Digital Marketing Tips and Strategies to Grow Your Business

A Guide to Web Accessibility Evaluation Tools
Creating a website that works for everyone isn’t just about ticking off legal checkboxes—it’s about ensuring every visitor, regardless of ability, can navigate your site with ease and enjoy their experience. Even if you’re familiar with web accessibility, it’s easy to wonder: Have I missed anything? Are there barriers I didn’t notice?

As digital inclusion becomes increasingly vital, ensuring your website is truly accessible is essential. So, how can you confidently create a welcoming space for all? That’s where web accessibility evaluation tools come in.

These tools simplify the process of identifying and addressing barriers, helping you build an inclusive website while enhancing the user experience. Let’s explore how they work, why they matter, and how to choose the right one for your needs.

What Are Web Accessibility Evaluation Tools?

Web accessibility evaluation tools are designed to analyze websites for accessibility issues. Think of these tools as the first line of defense in identifying problems that might hinder someone with visual, auditory, or cognitive impairments from fully engaging with your content.

These tools scan your website pinpointing issues like poor color contrast, missing alt text for images, or broken keyboard navigation. Some go further, offering continuous monitoring and integration with development workflows.

Why Are They Important?

Using a web accessibility evaluation tool is more than a technical step—it’s a commitment to inclusivity and compliance. Here’s why they’re indispensable:
- WCAG Compliance: Web Content Accessibility Guidelines (WCAG) standards are the backbone of digital accessibility. Tools help you identify and address non-compliance to avoid legal risks.
- User Experience: Accessibility isn’t just for people with disabilities; it improves usability for everyone. For example, captions benefit not only those who are deaf but also people in noisy environments.
- Boost Brand Reputation: An accessible website shows your commitment to inclusion, fostering goodwill and loyalty among your audience.
- Legal Protection: With lawsuits over inaccessible websites on the rise, staying compliant minimizes legal vulnerabilities.
Benefits of Using Web Accessibility Evaluation Tools
- Efficient Issue Detection: Automated tools can scan your website in minutes, identifying accessibility barriers that might take hours to find manually.
- Enhancing the User Journey: Accessibility issues often overlap with usability problems. Fixing these barriers creates a smoother and more enjoyable experience for all visitors.
- Avoiding Legal Issues: Addressing accessibility gaps proactively reduces the likelihood of being targeted by lawsuits related to digital accessibility.
- Cost-Effective Improvements: Automated tools are an affordable starting point for businesses that need to improve their websites without a major investment.
- Sustained Accessibility: Continuous monitoring ensures your website remains accessible even as you update or expand its content.
How to Choose the Right Accessibility Evaluation Tool

When selecting a tool, start by asking these questions:
- What’s my budget?
- Do I need ongoing monitoring or a one-time scan?
- How user-friendly does the tool need to be for my team?
For small businesses, look for tools with simple interfaces and strong customer support. Larger organizations may need advanced features like integrations and robust reporting.One tool worth considering is Accessibility Radar (a11y.Radar), which provides real-time monitoring, actionable insights, and scalable solutions for businesses of all sizes.

What to Look for in Web Accessibility Evaluation Tools

Not all tools are created equal. To get the most out of a web accessibility evaluation tool, focus on these features:
- Automated Scanning: Quickly detect common issues like missing ARIA labels or unstructured content to get a big-picture view of potential accessibility gaps.
- Real-Time Monitoring: For frequently updated websites, real-time monitoring ensures new issues are caught as they appear. Tools like a11y.Radar excel at providing continuous oversight.
- Integration Options: Choose tools that integrate seamlessly with your existing systems, such as your CMS, analytics platforms, or development tools.
- Actionable Reporting: Look for tools that provide clear, prioritized reports so your team knows where to focus their efforts.
- Customizability: Tailor the tool to address your site’s unique needs and align with relevant accessibility standards.
a11y.Radar ADA Monitoring

a11y.Radar is an automated recurring ADA web compliance auditing platform. Through our work in the trenches of the ADA web remediation space, we were able to reverse-engineer the process in which many of the prolific ADA non-compliance lawsuit firms identify their targets. We realized that the vast majority of cases are filed solely based on the results of automated scanning tools, so we developed Accessibility Radar as a hands-off method of keeping you out of their crosshairs.

How Does a11y.Radar ADA Monitoring Work?

a11y.Radar ADA monitoring service reports on your ongoing accessibility efforts, whether conducted by your internal digital teams or an outside web agency. Access enhanced dashboards and receive updates to content, code, and user experience that could pose potential blocks to users or threaten your accessibility standards. In addition, our seamless interface allows your team members to view current issues and manage pending adjustments.

Limitations of Automated Tools

It’s important to acknowledge that even the best web accessibility evaluation tool can’t catch everything. Automated tools are great for spotting obvious issues, but they might miss nuances that only a human can detect. For example, determining whether alt text appropriately describes an image often requires human judgment.

To bridge these gaps, combine automated tools with manual testing. This hands-on approach helps identify issues that software alone can’t catch. This means involving people—preferably those with disabilities or experts in web accessibility—in testing your website. Manual testing can uncover issues related to usability and user experience that automated tools might overlook.

Practical Tips for Using Accessibility Tools
- Start with an Automated Scan: Identify low-hanging fruit like fixing color contrast or adding alt text to images.
- Prioritize Fixes: Focus on the most significant barriers affecting users, such as navigation or text readability.
- Educate Your Team: Make sure your developers and content creators understand the tool’s insights and how to implement changes effectively.
- Schedule Regular Checks: Accessibility is an ongoing process, not a one-time task. Use tools to monitor your site periodically.
Make Accessibility a Priority

Digital accessibility isn’t just a legal consideration—it’s a business advantage. By using web accessibility evaluation tools like a11y.Radar, you can identify barriers, enhance user experience, and demonstrate your commitment to inclusivity.

Ready to take the next step toward a more accessible website? Schedule an ADA briefing with 216digital to learn how a11y.Radar can provide real-time monitoring and actionable insights tailored to your needs. Together, we’ll help you build an inclusive, user-friendly website that welcomes everyone.

By investing in accessibility, you’re investing in your audience and building a stronger, more inclusive brand. Don’t wait—reach out to 216digital today and make your website a space where everyone feels welcome.
Greg McNeil

November 25, 2024

Testing & Remediation, Web Accessibility Monitoring

Accessibility, Accessibility monitoring, Accessibility testing, evaluation tools, Website Accessibility, Website Accessibility Tools
Accessible Chatbots: Breaking Barriers in Support
Nowadays, customers have come to expect support and product help on-demand, 24 hours a day, 7 days a week. It is only possible for some businesses to provide human assistance at all times – that’s where chatbots come in. These tools can be invaluable to users and business owners alike, but it’s essential to ensure that people with disabilities can gain access to the same support. Let’s explore the concept of accessible chatbots.

Why Chatbot Accessibility Matters

Imagine trying to resolve an urgent issue on a website, only to find the chatbot—your primary source of help—completely unusable. For many people with disabilities, this scenario is all too common.

Accessible chatbots aren’t just about meeting legal requirements like ADA (Americans with Disabilities Act) compliance or adhering to WCAG (Web Content Accessibility Guidelines) standards; they’re about creating a seamless experience for everyone. When designed thoughtfully, chatbots can be a powerful tool for inclusivity. But when accessibility is overlooked, they can alienate an entire segment of your audience.

Common Barriers in AI Chatbots

Incompatible with Screen Readers

Many chatbots need more critical semantic HTML features like landmarks and incorrectly use HTML tags, causing a confusing or frustrating experience.

Keyboard Navigation Failures

Chatbots often lack keyboard support, requiring mouse clicks to open or interact. Users with disabilities rely on the ability to navigate content and functionality with alternative input methods like keyboards, voice commands, and gestures.

Unclear or Missing Focus Indicators

Focus indicators—the visual cues showing where a user is on a page—are often missing in chatbots. Without these, keyboard users may lose track of where they are in the conversation flow.

Overly Complex or Jumbled Responses

Chatbots tend to present information in long blocks of text or overly complicated formats. For users with cognitive disabilities, this can be overwhelming and hard to follow.

Time Constraints

Some chatbots automatically close after a period of inactivity, which can disadvantage users who need more time to read or type responses.

Lack of Alternative Communication Options

Chatbots often act as the sole method of contact, leaving users without alternative ways to reach support if they can’t use the chatbot.

How to Build an Accessible Chatbot

Making your chatbot accessible doesn’t have to be daunting. By following WCAG guidelines and implementing these best practices, you can create a more inclusive experience:

Use Semantic HTML for Chatbot Elements

Building an accessible chatbot does not require any specialized experience – you can apply the same general best practices to achieve accessible elements. Use the correct semantic HTML tags for each component you create, such as button or input elements.

Here’s an example of an accessible chatbot button:
```
<button aria-label="Open chatbot" id="chatbot-open-button">  
  Chat with us  
</button>
```
The aria-label ensures that screen readers convey the button’s purpose to users.

Support Keyboard Navigation

Your chatbot should be fully functional with just a keyboard. Test whether users can open, navigate, and interact with the chatbot using the Tab and arrow keys.

For example, ensure focus moves logically through the chatbot interface:
```
document.querySelector('#chatbot-input').focus();  
```
Provide Descriptive ARIA Labels

ARIA (Accessible Rich Internet Applications) roles and attributes can bridge gaps in accessibility, but they must be used carefully. Assign roles like aria-live to update users on dynamic content.
```
<div role="alert" aria-live="polite" id="chatbot-messages">  
  Welcome! How can I assist you today?  
</div>  
```
Using aria-live ensures that screen readers announce new messages in real time.

Design with Simplicity in Mind

Avoid overwhelming users with large blocks of text. Break responses into smaller chunks and provide clear, concise answers.

Allow for Adjustable Timing

Let users control the session duration. If the chatbot times out, allow them to restart the session without losing previous messages.
```
setTimeout(() => {  
  alert('The chatbot session has timed out. Click to resume.');  
}, 300000);   
```
Include Accessible Focus Indicators

Make sure users can see which element is currently focused. Use CSS to style focus indicators:
```
button:focus {  
  outline: 2px solid #005fcc;  
  outline-offset: 2px;  
}  
```
Provide Alternatives to Chatbots

Not everyone can—or wants to—use a chatbot. Always include alternative ways to contact your business, like email or phone.

Testing Chatbot Accessibility

Testing is critical for identifying and fixing accessibility issues. Here are some methods to ensure your chatbot meets accessibility standards:

Manual Testing with Screen Readers

Test the chatbot using screen readers like NVDA or JAWS. Check if labels, navigation, and dynamic updates work as intended.

Keyboard Navigation Tests

Navigate the entire chatbot interface using only a keyboard. Make sure the focus moves logically, and that all interactions are possible.

Automated Tools

Use tools like Lighthouse to identify accessibility issues in your chatbot’s code.

User Feedback

Invite users with disabilities to test the chatbot and provide feedback. Their real-world experiences will highlight areas you may have missed.

Meeting WCAG Standards for Chatbots

The Web Content Accessibility Guidelines (WCAG) provide a roadmap for making chatbots more inclusive. Key criteria to consider include:
- 1.3.1: Info and Relationships
- Ensure that chatbot components are semantically structured and that relationships between elements are apparent.
- 2.1.1: Keyboard Accessibility
- All chatbot functions must be accessible via keyboard.
- 2.4.7: Focus Visible
- Ensure users can see where they are within the chatbot interface.
- 4.1.2: Name, Role, Value
- Use ARIA roles and labels to make interactive elements understandable to assistive technologies.
Wrapping Up

All the functionality on your website is helpful in some way to your users, or else you wouldn’t include it on your site. All functionality on your website should be accessible to everyone, especially chatbots.

Remember to test your chatbot with screen readers, ensure keyboard compatibility, and always provide alternative ways to connect. Inclusive design benefits your business by reaching a broader audience and creating a better user experience for all.

If you’re unsure if your chatbot is accessible to everyone, reach out to 216digital using the contact form below.
Greg McNeil

November 22, 2024

How-to Guides

Accessibility, Chatbots, web developers, web development, Website Accessibility
Skip Links: Improve Web Accessibility & Navigation
More and more, digital accessibility has become a major talking point when browsing the web. One of the key components that improve accessibility for users with disabilities is something many users might not even notice: skip links.

These simple yet powerful tools can make a huge difference in the web experience for individuals relying on keyboard-only interaction, screen readers, or other assistive technologies. In this article, we’ll explore the importance of skip links, their technical mechanics, and how you can implement them effectively on your website.

What Are Skip Links and Why Are They Important?

Skip links are navigational links that allow users to skip over repetitive content such as headers, navigation menus, or other elements they’ve already seen. For users relying on assistive technologies like screen readers, keyboard navigation, or switch devices, skip links enable them to jump directly to the main content of the page.

When navigating a website using a keyboard (by pressing the Tab key), users typically encounter all of the page’s links and elements in a set order. This often means they have to cycle through the same menus, headers, and other repetitive content every time they visit a new page or reload an existing one. Skip links solve this problem by providing an easy way to bypass these elements, saving time and frustration for those who need alternative navigation methods.

For example, imagine you’re using a screen reader to navigate a website. Without skip links, you might be forced to listen to the same navigation menu and header over and over again, even though you’re only trying to get to the main body of the page. Skip links allow you to bypass this content, going straight to the part of the page you want.

The Key Benefits of Skip Links

Improved Navigation for Keyboard-Only Users

Many people with disabilities, including those with limited mobility or dexterity, use keyboards or alternative input devices to navigate the web. Skip links let users quickly navigate to the main content, bypassing headers, footers, and menus that they may have already accessed.

Enhanced Experience for Screen Reader Users

Screen readers announce every element on a webpage in the order they are tabbed through. Without skip links, users would have to hear the same menus and links repeatedly, making navigation time-consuming and tedious. Skip links streamline the experience by providing a shortcut to the main content.

Better Usability for Assistive Technologies

Skip links are a simple yet effective tool that benefits various assistive technologies, enhancing the overall usability of your website for a wide range of users.

Increased Accessibility Compliance

Many countries and regions have laws requiring websites to be accessible. For example, in the United States, the Americans with Disabilities Act (ADA) mandates that websites must be accessible to all users, including those with disabilities. Implementing skip links helps ensure your website is compliant with accessibility guidelines like Web Content Accessibility Guidelines (WCAG).

How Do Skip Links Work?

Skip links work by creating a link that, when activated, allows the user to bypass parts of the webpage and move directly to a more relevant section. These links are typically placed at the top of the page, visible only when the user navigates using the keyboard (by pressing the Tab key). The link itself usually says something like “Skip to main content,” “Skip to navigation,” or “Skip to footer,” depending on which section the user wants to bypass.

The Technical Mechanics of Skip Links

To create a skip link, you use basic HTML along with some helpful attributes to control the behavior and accessibility of the link. Here’s an overview of the technical aspects of skip links:

HTML Structure with <a href> Tags

The primary way to implement skip links is with the <a> (anchor) tag, which creates hyperlinks. These links should point to specific elements within the webpage, often with id attributes to mark the sections users can skip to.

tabindex Attribute

The tabindex attribute is used to control the tab order of elements. By default, links and form controls are included in the tab order. However, for skip links to work properly, they need to be made focusable before other content is tabbed through.

aria-label and aria-hidden Attributes

The aria-label attribute can be used to provide screen readers with a more descriptive label for the skip link. For example, you can use it to define a more readable label like “Skip to main content,” ensuring that screen readers announce the skip link’s purpose clearly. On the other hand, the aria-hidden attribute can be used to hide elements from assistive technologies when needed.

A Simple Skip Link Example

Here’s a simple HTML example of a skip link that allows users to skip directly to the main content of a webpage:
```
<a href="#main-content" class="skip-link" tabindex="0" aria-label="Skip to main content">Skip to main content</a>
<header>
<nav>  </nav>
</header>
<main id="main-content">
<h1>Welcome to Our Website</h1>
<p>This is the main content of the page...</p>
</main>
```
In this example:
- The skip link (<a href="#main-content">) is placed at the top of the page and links to the main-content section identified by the id="main-content".
- The tabindex="0" ensures that the skip link is focusable and can be reached when using the Tab key.
- The aria-label="Skip to main content" helps screen reader users understand what the link does.
Styling Skip Links

While skip links are crucial for accessibility, they’re not always visually appealing by default. To make skip links blend in with your design, you’ll likely want to hide them until they’re needed and style them for better usability. Here’s how you can style skip links using CSS:
```
.skip-link {
position: absolute;
top: -40px; /* Hide the link off-screen */
left: 0;
background-color: #000;
color: #fff;
padding: 10px;
z-index: 100;
}
.skip-link:focus {
top: 10px; /* Bring the link into view when focused */
}
```
In this example:
- The .skip-link class hides the skip link off-screen with top: -40px until it’s needed.
- When the link is focused (i.e., when the user tabs to it), it becomes visible by setting top: 10px.
- You can customize the background color, text color, padding, and positioning to match your website’s design.
JavaScript for Enhanced Skip Link Functionality

In some cases, you may want to enhance the behavior of your skip link using JavaScript. For example, you might want to automatically focus the main content once the skip link is activated. Here’s how you can do that:
```
document.querySelector('.skip-link').addEventListener('click', function(e) {
e.preventDefault();
document.querySelector('#main-content').focus();
});
```
This script listens for a click on the skip link and prevents the default action (i.e., jumping to the href target). Instead, it uses JavaScript to focus on the main content section, making it even easier for users to access.

Testing Skip Links for Accessibility

Once you’ve implemented skip links, it’s essential to test them to ensure they’re working as expected. Here are a few key tips for testing your skip links:
1. Keyboard Navigation: Use the Tab key to cycle through the elements on your page. Ensure the skip link is the first item that can be focused and that it jumps you to the main content.
2. Screen Reader Testing: Test your skip links with a screen reader (such as NVDA or VoiceOver) to ensure the skip links are announced correctly and work as expected.
3. Cross-Browser Compatibility: Make sure your skip links work across different browsers and devices. Some older browsers might have quirks that affect the behavior of tabindex or CSS styling, so testing across multiple platforms is critical.
4. Accessibility Tools: Use automated accessibility tools like Lighthouse to check for accessibility issues on your website. These tools can help identify missing or misused attributes related to skip links.
Challenges with Skip Links

While skip links are an essential tool for accessibility, there are some challenges you might encounter when implementing them:
- Browser Inconsistencies: Different browsers and devices may render skip links or handle focus management differently. It’s important to test across various platforms to ensure consistent behavior.
- Visibility and Styling: Skip links should be visible when needed but unobtrusive when not. Ensuring they are easily accessible but don’t clutter the design can require some careful styling.
- Managing Focus Order: If your page has dynamic content (like modals or sticky headers), you may need to adjust the focus order or ensure that skip links still work as expected when these elements are present.
Skip Ahead to Success

Skip links are a simple but vital tool in improving the accessibility of your website. They help keyboard-only users, screen reader users, and others navigate your site more efficiently by skipping over repetitive content and jumping straight to the main sections of the page. By implementing skip links with proper HTML, CSS, and JavaScript, you can enhance the user experience for a wider audience, making your site more inclusive and accessible.

If you’re ready to make your website ADA-compliant and accessible to everyone, schedule an ADA briefing with 216digital. Our team of experts will walk you through the process, address any questions, and help you create an inclusive, compliant, and user-friendly web experience. Don’t wait—take the first step toward a more accessible digital presence today.
Greg McNeil

November 21, 2024

How-to Guides

Accessibility, How-to, skip link, Web Accessibility, web developers, web development
How Accessibility Widgets Can Put Businesses at Risk
Web-accessibility overlays, also known as accessibility widgets, promise an easy, one-click solution to achieving compliance with web-accessibility standards like the Web Content Accessibility Guidelines (WCAG). These widgets often claim to make websites instantly accessible to people with disabilities while shielding businesses from legal action.

However, this promise is often too good to be true. Overlays have significant limitations, and relying solely on them can expose businesses to legal, reputational, and financial risks. This article will explore why overlays fall short, the dangers of assuming they are sufficient, and why companies need a more comprehensive approach to web-accessibility.

What Are Website Accessibility Overlays?

Accessibility overlays are third-party tools or scripts integrated into a website. They offer text resizing, color contrast adjustments, screen reader compatibility, and keyboard navigation. For businesses seeking quick solutions, these widgets appear convenient and cost-effective.

Yet, accessibility experts and advocacy groups frequently criticize overlays for failing to address core accessibility issues. Many users with disabilities report that these tools do not work as advertised and often create more barriers than they remove.

Legal Risks of Accessibility Overlays

The legal landscape surrounding web-accessibility has become increasingly complex. Businesses in the United States are required to provide equal access under laws like the Americans with Disabilities Act (ADA) and, in some cases, the Rehabilitation Act. Non-compliance can result in lawsuits, financial penalties, and settlement costs.

Here’s how overlays contribute to legal risks:

False Sense of Compliance

Overlays often give businesses a false sense of security by claiming compliance with WCAG standards. However, these widgets rarely fix underlying issues in the website’s code, which is the root of most accessibility barriers.

Courts have consistently ruled that overlays are not a substitute for full compliance. For example, in cases like Robles v. Domino’s Pizza, the courts emphasized that businesses must address accessibility holistically, not rely on third-party fixes.

Increased Legal Vulnerability

Recent lawsuits have specifically targeted companies that rely on overlays. Plaintiffs argue that these tools fail to provide meaningful access and do not meet legal standards. Businesses using overlays can face repeat litigation from multiple plaintiffs or “copycat” lawsuits.

Misleading Claims

Overlays that advertise themselves as ADA-compliant solutions may expose businesses to additional liability under consumer protection laws for misleading claims.

Reputational Risks of Accessibility Overlays

In today’s socially conscious marketplace, accessibility is not just a legal requirement but a moral and ethical imperative. Failing to address accessibility authentically can damage a business’s reputation.

Negative Feedback from Users

Many individuals with disabilities report that overlays interfere with assistive technologies like screen readers and fail to improve their browsing experience. Frustrated users often take to social media to share their negative experiences, leading to bad publicity.

Advocacy Group Backlash

Disability advocacy groups are increasingly vocal about the ineffectiveness of overlays. A public campaign against a company for using a widget as a “quick fix” can tarnish its brand and alienate customers who value inclusivity.

Erosion of Trust

Businesses relying on overlays signal a lack of commitment to genuine accessibility. This can lead to diminished trust among consumers, especially in industries like retail, education, and healthcare, where accessibility expectations are high.

Financial Risks of Accessibility Overlays

The financial consequences of relying on accessibility overlays extend beyond potential lawsuits. They can lead to hidden costs that outweigh their initial affordability.

Recurring Costs Without Long-Term Benefits

Overlays typically operate on a subscription model, requiring ongoing payments. Despite these recurring costs, they fail to deliver permanent solutions, forcing businesses to invest in comprehensive remediation eventually.

Cost of Legal Defense

Defending against accessibility lawsuits is costly, even if a case doesn’t reach trial. Businesses relying on overlays may face higher legal expenses due to their inability to demonstrate genuine efforts toward compliance.

Lost Revenue from Alienated Customers

Accessibility barriers can drive away potential customers, especially in e-commerce. An inaccessible website limits the purchasing power of individuals with disabilities, who collectively control over $490 billion in disposable income in the United States alone.

The Limitations of Accessibility Overlays

Accessibility overlays are inherently limited because they address only surface-level issues. They do not fix the underlying structural problems in a website’s code. Key limitations include:
- Incompatibility with Assistive Technology: Many widgets fail to work seamlessly with screen readers, keyboard navigation, or voice recognition software.
- Partial Coverage: Overlays often address only a narrow set of accessibility issues, leaving gaps that continue to exclude users with disabilities.
- Unintended Consequences: Some overlays introduce new barriers, such as excessive pop-ups, poor usability, or errors that disrupt the browsing experience.
These limitations highlight why overlays cannot replace a robust accessibility strategy.

A More Authentic Approach to Web-Accessibility

To truly achieve accessibility, businesses must move beyond quick fixes and invest in comprehensive, authentic solutions. A holistic approach includes:

Accessibility Audits

Conducting thorough manual and automated audits to identify all accessibility barriers on a website. An audit provides a clear roadmap for remediation.

Remediation of Core Issues

Fixing the underlying code to ensure compliance with WCAG standards. This involves addressing issues like semantic HTML, proper labeling of forms, and ensuring content is perceivable, operable, understandable, and robust (POUR principles).

Ongoing Maintenance

Accessibility is not a one-time project. Regular updates, testing, and monitoring ensure that websites remain compliant as technology evolves.

User-Centered Design

Involving users with disabilities in the design and testing process ensures that solutions meet real-world needs.

Expert Partnerships

Partnering with accessibility experts helps businesses navigate complex legal requirements and implement effective solutions. Services like 216digital’s a11y.Radar provides ongoing monitoring to maintain compliance and reduce the risk of lawsuits.

Why Businesses Should Avoid the Widget Trap

While accessibility overlays may seem like a quick fix, their limitations and associated risks make them a poor choice for businesses serious about accessibility. A genuine commitment to accessibility requires addressing the root causes of inaccessibility, not just the symptoms.

Schedule an ADA Briefing with 216digital

If you’re ready to move beyond widgets and take meaningful steps toward true web-accessibility, schedule an ADA briefing with 216digital. Our team of experts will guide you through understanding accessibility standards, identifying areas for improvement, and implementing solutions tailored to your business. With tools like our a11y.Radar service for ongoing monitoring, we’ll help ensure that your website not only meets compliance requirements but also provides a user-friendly experience for everyone.

By investing in a robust and authentic approach, businesses can avoid the legal, reputational, and financial pitfalls of relying on overlays. More importantly, they can create an inclusive digital experience that serves all users, regardless of ability.
Greg McNeil

November 20, 2024

Legal Compliance

Accessibility, ADA Compliance, Overlay, Overlay widgets, Website Accessibility, Widgets
Is ADA Compliance the Same as 508 Compliance?
If you’ve worked on a website or digital content, you know accessibility isn’t just important—it’s essential. But here’s a common question that trips up even seasoned professionals: Are ADA compliance and Section 508 compliance the same thing? While they may seem similar at first glance—both aim to make digital experiences accessible—their differences are crucial, and misunderstanding them could mean focusing on the wrong standards for your audience or business.

In this article, we’ll unpack the distinctions and overlaps between ADA and Section 508 compliance. By the end, you’ll not only understand what sets them apart but also how to use this knowledge to make your website truly accessible.

What is ADA Compliance?

ADA stands for the Americans with Disabilities Act, a landmark law passed in 1990 to ensure that people with disabilities have the same rights and opportunities as everyone else. The ADA covers a wide range of accessibility issues, from physical spaces (like ramps and elevators in buildings) to digital spaces (like websites and online services). In the context of websites, ADA compliance means making sure your website is accessible to people with disabilities.

For websites, ADA compliance means ensuring accessibility for people with disabilities. This includes making your site usable for:
- Visually impaired individuals using screen readers.
- Deaf or hard-of-hearing users who rely on captions or transcripts.
- People with motor disabilities who may use keyboards or alternative input devices instead of a mouse.
While the ADA itself doesn’t give specific rules for websites, it requires businesses to ensure that their digital services are accessible. This is where guidelines like the Web Content Accessibility Guidelines (WCAG) come into play. The WCAG provides a set of standards for making websites accessible to everyone, including people with various disabilities.

What is Section 508 Compliance?

Section 508 is part of the Rehabilitation Act of 1973, a law designed to improve access for people with disabilities, especially in the workplace and in government. Section 508 specifically focuses on ensuring that federal agencies and contractors make their electronic and information technology (EIT) accessible. This includes websites, software, videos, and other forms of digital content used by government employees and the public.

Section 508 compliance is more specific than ADA compliance because it lays out detailed technical standards for web accessibility. Unlike the ADA, which applies to all public and private entities, Section 508 is focused specifically on federal government entities and those that do business with the government.

The Key Differences Between ADA and Section 508 Compliance

Now that we have a basic understanding of both standards let’s take a look at some of the key differences:

Scope of Applicability

ADA compliance applies to all businesses, government entities, and organizations that provide public services, including websites, regardless of whether they are working with the federal government.

On the other hand, Section 508 only applies to federal agencies, federal contractors, and any organizations or companies that receive federal funding or contracts. In other words, Section 508 is more narrow in scope than ADA compliance.

Specificity of Standards

ADA compliance serves as a general guideline rather than providing specific technical or legal instructions for web accessibility. Its primary focus is on the principle of accessibility, encouraging the design of websites that are usable by individuals with a variety of disabilities. By prioritizing inclusivity, ADA compliance aims to ensure that everyone can effectively access online content. ADA compliance often refers to the WCAG guidelines for web content accessibility.

Section 508 compliance is more prescriptive, offering clear technical guidelines for web accessibility. These standards focus on things like screen reader compatibility, color contrast, keyboard navigation, and other specific details.

Enforcement

ADA compliance can be enforced through private lawsuits, meaning that individuals with disabilities or advocacy groups can take legal action if a website is not accessible. This has led to a number of high-profile lawsuits in recent years, where businesses were sued for failing to make their websites accessible.

Section 508 compliance is enforced primarily through audits and inspections conducted by the federal government. If a government agency or contractor is found to be non-compliant, they could lose funding and contracts or be excluded from future government work.

Similarities Between ADA and Section 508 Compliance

Even though there are some important differences, both ADA compliance and Section 508 compliance share several key similarities:

The Goal of Accessibility

Both ADA and Section 508 aim to make the digital world more accessible to people with disabilities. This means ensuring that websites, online services, and content are usable by people who have visual, auditory, cognitive, or motor impairments.

Use of WCAG Guidelines

Both ADA and Section 508 compliance often refer to WCAG as a standard for making websites accessible. While Section 508 has its own set of technical requirements, these overlap with many of the WCAG principles. So, if you’re working on a website, it’s helpful to familiarize yourself with WCAG standards, whether you are concerned with ADA or Section 508 compliance.

Testing for Accessibility

Both ADA and Section 508 compliance require you to test your website for accessibility. This can include using screen readers, testing keyboard navigation, checking for proper color contrast, and making sure your site works with assistive technologies like voice recognition software.

Practical Tips for Testing Your Website for Accessibility

Whether you’re aiming to meet ADA or Section 508 compliance, here are some practical steps you can take to test and improve the accessibility of your website:

Use Automated Tools

There are a number of tools that can help you check for accessibility issues, like WAVE or Lighthouse. These tools scan your site for common accessibility issues like missing alt text for images, poor color contrast, and improper heading structure. While automated tools are helpful, they shouldn’t be your only testing method.

Manual Testing

Automated tools can catch some issues, but manual testing is also essential. This might include navigating your site with a keyboard (without using a mouse) or testing your site with a screen reader like NVDA or VoiceOver to see how it works for visually impaired users.

Get Feedback from Users

If possible, have people with disabilities test your site. Getting feedback from real users is one of the best ways to identify issues you might not have thought of. You can reach out to local accessibility organizations or use user testing platforms to gather feedback.

Review Your Content

Make sure your website’s content is accessible, too. This means providing text alternatives for images, videos with captions, or transcripts and using simple, easy-to-read language.

Which Should You Focus On?

Understanding the distinctions between ADA and Section 508 compliance is critical for creating an inclusive, accessible website that meets legal standards. If you’re a business owner, ADA compliance should be your primary concern. Federal contractors and agencies, on the other hand, must adhere to Section 508 requirements.

The good news? Improving accessibility benefits everyone—not just your users, but your organization too.

Navigating these regulations can feel daunting, but you don’t have to go it alone. At 216digital, we specialize in tailored accessibility solutions to help you meet both ADA and Section 508 standards. From comprehensive audits to ongoing monitoring, we’re here to guide you every step of the way.

Ready to make your website accessible to everyone? Schedule an ADA briefing with 216digital and take the first step toward compliance and inclusivity.
Greg McNeil

November 19, 2024

Legal Compliance

Accessibility, ADA, ADA Compliance, Section 508, Web Accessibility
POURing Effort into Web Accessibility
Creating an inclusive digital world isn’t just a nice-to-have—it’s a necessity. For many people, accessing information online isn’t as simple as opening a website and scrolling through content. Visual impairments, mobility challenges, cognitive disabilities, and other barriers can make navigating the internet difficult without proper accommodations. That’s where the Web Content Accessibility Guidelines (WCAG) come in.

WCAG provides a roadmap for making web content accessible to all users, regardless of their abilities. Central to these guidelines are four foundational principles known by the acronym POUR: Perceivable, Operable, Understandable, and Robust. In this article, we’ll explore what POUR means, why it’s important, and how you can apply these principles to create a more accessible user experience.

What Is POUR?

At the heart of WCAG are the four foundational principles known as POUR: Perceivable, Operable, Understandable, and Robust. These principles serve as the pillars of accessible design, guiding developers and designers to create web experiences that accommodate a wide range of abilities and preferences.

POUR ensures that digital content is not only accessible but also functional and user-friendly. Adhering to these principles helps remove barriers and allows everyone—regardless of physical, sensory, or cognitive abilities—to engage with web content fully and independently.

In the following sections, we’ll take a closer look at each of the POUR principles, their practical applications, and how they make web content more inclusive.

Perceivable: Making Content Accessible to the Senses

The principle of perceivability focuses on ensuring that all users can access and process the information presented on a website. This means content must be adaptable to a variety of sensory modalities, such as vision, hearing, or touch. Without perceivable content, users with sensory disabilities may be completely excluded from accessing critical information.

What Does Perceivable Mean in Practice?
1. Text Alternatives for Non-Text Content: Every image, icon, and multimedia element must include a text equivalent, such as alt text for images or transcripts for audio content. For example, if a website features a graph, it should include a detailed description of the data for visually impaired users.
2. Captions and Audio Descriptions: Videos should have captions for users who are deaf or hard of hearing and audio descriptions for users who are blind, ensuring everyone can understand the content.
3. Readable Text Content: Font size, color contrast, and spacing should make text readable for users with visual impairments or dyslexia. For instance, using a high-contrast color scheme helps users with low vision differentiate between text and background.
Common Mistakes That Violate Perceivable Standards
- Using images without alt text or vague descriptions like “image123.jpg.”
- Not adding captions to video content makes it difficult for people with hearing impairments to follow along.
- Designing web content that relies heavily on color to convey information can be problematic for color-blind users.
Operable: Ensuring Users Can Navigate and Interact

Operability is about giving users the ability to interact with and navigate a website effectively. Websites should cater to diverse input methods, including keyboards, mice, touchscreens, and assistive technologies like screen readers or sip-and-puff devices.

What Does Operable Mean in Practice?
1. Keyboard Accessibility: All interactive elements—such as buttons, forms, and menus—must be usable via a keyboard. For example, users should be able to navigate a website using the Tab key to move between elements and the Enter key to select options.
2. Adjustable Time Limits: Users must be given enough time to complete tasks like filling out forms. If a time limit is necessary, users should have the option to extend it or pause the timer.
3. Avoiding Traps: Design interactive elements like pop-ups or carousels to ensure users don’t become “trapped.” For example, make it easy for keyboard users to close a pop-up.
Common Mistakes That Violate Operable Standards
- Creating drop-down menus or interactive elements that are difficult to navigate with a keyboard.
- Designing forms that reset if not completed within a set time frustrates users who may need extra time.
- Using auto-scrolling content that cannot be paused or stopped.
Understandable: Keeping Content Clear and Predictable

The principle of understandability ensures that users can easily comprehend both the information and the functionality of a website. Content should be presented in a logical, consistent, and intuitive manner.

What Does Understandable Mean in Practice?
1. Plain Language: Avoid jargon and use simple, clear language. For example, instead of saying, “Click here to access the comprehensive compendium of resources,” simply say, “Click here to access the resource guide.”
2. Predictable Interactions: Elements like navigation menus and buttons should behave consistently throughout the site. For example, a menu that expands when clicked should work the same way on every page.
3. Error Feedback and Recovery: Forms and other interactive elements should provide clear feedback when users make errors. For instance, if a user forgets to fill out a required field in a form, the website should provide an error message that explains what’s missing and how to correct it.
Common Mistakes That Violate Understandable Standards
- Using complicated words or phrases without explanations makes it hard for users to comprehend the content.
- Having links or buttons that perform unexpected actions confuses the user.
- Need to highlight input errors clearly or explain how to fix them.
Robust: Ensuring Compatibility with Current and Future Technologies

Robustness focuses on ensuring that websites are compatible with a wide range of technologies, including assistive devices. This principle ensures content remains accessible even as technology evolves.

What Does Robust Mean in Practice?
1. Standards-Compliant Code: Using clean, valid HTML and CSS ensures that web content is compatible with different browsers and assistive technologies. For example, screen readers can more easily interpret properly coded content.
2. Accessible ARIA Attributes: ARIA (Accessible Rich Internet Applications) roles and properties enhance dynamic content and make it usable for assistive technologies. For example, adding aria-live attributes to alerts ensures screen readers announce changes in real time.
3. Cross-Device Testing: Websites should be tested on various devices, operating systems, and browsers to ensure compatibility.
Common Mistakes That Violate Robust Standards
- Using outdated or non-standard HTML code can break some browsers or assistive technologies.
- Labeling form elements properly makes it easier for screen readers to convey relevant information to the user.
Bringing POUR Principles Together

While each POUR principle addresses a specific aspect of accessibility, they work together to create a seamless and inclusive user experience. Let’s look at an example of how all four principles might be applied:

Example: An E-Commerce Website
1. Perceivable: Images of products include descriptive alt text, and videos showcasing features have captions and audio descriptions.
2. Operable: Users can navigate the site with a keyboard and use the Tab key to add items to their cart.
3. Understandable: The checkout process uses plain language and provides clear instructions for completing forms.
4. Robust: The site is tested with assistive technologies like screen readers and works smoothly on mobile devices.
By aligning with all four POUR principles, the website ensures that users of all abilities can browse, shop, and complete their purchases effortlessly.

Putting POUR into Practice

Applying the POUR principles isn’t just about avoiding mistakes; it’s about creating a truly inclusive web experience. Here’s how you can start:
1. Audit Your Site: Conduct an accessibility review to identify areas where your site falls short of POUR.
2. Incorporate accessibility from the Start: Build POUR into your web development and design process rather than trying to retrofit accessibility later.
3. Test with Real Users: Engage users with disabilities to test your site and provide feedback.
By focusing on POUR, you not only improve accessibility but also enhance usability for all visitors, creating a better overall user experience.

POURing Effort into Accessibility

The four principles of WCAG—Perceivable, Operable, Understandable, and Robust—offer a solid foundation for building an accessible web. These principles are not just guidelines; they represent a commitment to inclusivity and respect for all users.

Accessibility isn’t a one-time task—it’s an ongoing effort to create a web that works for everyone. By applying POUR to your digital content, you’re taking meaningful steps toward a more inclusive future. Start today by reviewing your site, learning from accessibility experts, and embracing WCAG principles to make a difference in the lives of your users.

If you’re ready to take the next step toward making your website ADA-compliant and ensuring accessibility for all, schedule an ADA briefing with 216digital. Our team of experts will guide you through the process, answer your questions, and help you create a web experience that’s inclusive, compliant, and user-friendly. Don’t wait—start building a more accessible digital presence today.
Greg McNeil

November 18, 2024

WCAG Compliance

Accessibility, WCAG, WCAG conformance, Website Accessibility
WCAG Conformance Levels: How High Should You Aim?
When you’re building a website, it’s easy to get caught up in the details of design, functionality, and making everything look just right. But what about accessibility? That’s where the Web Content Accessibility Guidelines (WCAG) come in. Think of WCAG as your go-to checklist for making sure your website is open and usable for everyone, including people with disabilities.

Accessibility isn’t just a “nice-to-have” anymore—it’s essential. Whether you’re trying to avoid lawsuits, comply with laws like the ADA, or make your site more welcoming, understanding WCAG conformance levels can help you figure out how high you should aim. Let’s break down the basics, explore the three levels—A, AA, and AAA—and help you find the sweet spot for your website.

What is WCAG?

WCAG stands for Web Content Accessibility Guidelines, but don’t let the formal name intimidate you. These guidelines are basically a roadmap for making websites, apps, and digital content work for everyone—whether someone has a disability or not. Developed by the World Wide Web Consortium (W3C), WCAG focuses on four key principles: making content perceivable, operable, understandable, and robust (POUR). Think of it as a checklist to ensure your site is usable for as many people as possible.

And it’s not just for developers! WCAG applies to everyone involved in building a website—from designers to writers—because accessibility goes beyond code. Whether it’s adding captions to videos, ensuring color contrast, or simplifying navigation, these small changes can make a huge difference in how people experience your site. At its core, WCAG is about creating a better internet for everyone.

Why Should You Care About WCAG Conformance?

So, why should WCAG be on your radar? For starters, it’s about reaching more people. Accessibility isn’t just for those with disabilities—it benefits everyone. Captions help folks watching a video on mute, high contrast is great for users in bright sunlight, and clear navigation makes life easier for anyone trying to find what they need. In other words, an accessible website is just a better website.

Then there’s the legal side of things. If you’re in the U.S., laws like the Americans with Disabilities Act (ADA) expect your site to meet certain accessibility standards, and WCAG is the go-to guide for that. Ignoring these guidelines could land you in hot water with lawsuits or fines—and let’s face it, no one wants that kind of stress.

But it’s not just about avoiding trouble. Prioritizing accessibility can actually boost your brand, build trust, and improve your site’s performance overall. Making your website accessible shows your users you care, and that can set you apart in a big way.

Breaking Down the WCAG Conformance Levels

WCAG isn’t a one-size-fits-all situation. It’s divided into three levels—A, AA, and AAA—each with its own set of requirements. Here’s what you need to know about each one:

Level A: Covering the Basics

Level A is like the starter pack for accessibility. It focuses on the most basic barriers that prevent people from accessing your site. For example:
- Adding alternative text (alt text) to images.
- Making sure everything can be used with just a keyboard.
- Avoiding flashing content that could trigger seizures.
If your website meets Level A, you’re covering the bare minimum. But let’s be real—it’s not enough to provide a great experience for most users. Think of Level A as the foundation you build on, not the end goal.

Level AA: The Sweet Spot

Level AA is where things start to get serious. It’s the most widely recommended level and is often what the law requires. With Level AA, you’re tackling more detailed issues like:
- Make sure the text has enough contrast with the background so it’s easy to read.
- Ensuring your navigation is consistent and clear.
- Providing captions for videos so they’re accessible to people with hearing impairments.
For most websites, Level AA hits the perfect balance—it’s achievable, practical, and covers a wide range of accessibility needs. If you’re wondering how high to aim, this is probably your answer.

Level AAA: The Extra Mile

Level AAA is like the platinum package. It’s the highest level of accessibility, but it’s also the hardest to achieve. Some of the requirements include:
- Offering sign language interpretation for video content.
- Make sure your site works well even under very specific conditions, like extreme contrast ratios.
While Level AAA is an amazing goal, it’s not realistic for every website. Even the W3C acknowledges that hitting this level for all content isn’t always possible. Instead, focus on what’s achievable for your site and audience, and aim for AAA features where you can.

How High Should You Aim?

So, where should you set your sights? For most organizations, Level AA is the way to go. It’s the legal standard in many places, including the U.S., and it covers most accessibility needs without overcomplicating things.

However, your target might depend on your audience and industry. For example:
- Government Websites: Usually aim for Level AA or higher since they serve a broad, diverse audience.
- Online Stores: Need to make sure people can easily browse and buy products, so Level AA is essential.
- Educational Platforms: Sometimes, we need to go beyond Level AA to ensure equitable access to learning materials.
If you’re running a small business or personal site, don’t stress about hitting Level AAA. Instead, focus on meeting Level AA and improving over time. Remember, accessibility is a journey, not a one-and-done task.

What Makes Level AAA So Hard?

Achieving Level AAA isn’t just difficult—it often forces you to make compromises that can impact your site’s usability and aesthetics. For example, meeting AAA contrast requirements might mean overhauling your brand’s carefully chosen color scheme. Or you might have to simplify complex content so much that it loses its original value or appeal.

It’s a delicate balancing act. On one hand, you want your site to be as accessible as possible. On the other hand, you need to ensure it remains engaging, functional, and true to your brand. For most organizations, focusing on Level AA strikes the best balance, ensuring broad accessibility without requiring sacrifices that could alienate other users or disrupt the site’s purpose.

That said, Level AAA isn’t all or nothing. While it may not be practical to achieve across the board, incorporating some AAA features—like avoiding overly complicated language or providing additional customization options—can still enhance your site and make it more inclusive. The key is to aim high without losing sight of what works best for your audience and goals.

Keeping Your Website WCAG Compliant

Meeting WCAG standards isn’t a one-time thing. Websites evolve, and so do accessibility needs. Here’s how you can stay on top of it:

Regularly Audit Your Site

Run accessibility audits often to catch issues early. Tools like Google Lighthouse or WAVE are a great start, but don’t stop there—getting feedback from actual users with disabilities can give you insights you won’t find anywhere else.

Train Your Team

Accessibility isn’t just for developers. Designers, content creators, and even marketers should understand the basics of WCAG. The more your team knows, the easier it’ll be to stay compliant.

Make Accessibility Part of Your Process

Don’t wait until the end of a project to think about accessibility. Include it in every step—from planning and design to testing and deployment.

Use Accessibility Tools

Tools like screen readers and color contrast analyzers can help you spot problems before they become major issues. These tools are easy to use and can make a big difference.

Stay Up-to-Date

WCAG updates from time to time to reflect new technology and user needs. Keep an eye on these changes and adjust your strategy as needed.

Achieve WCAG Conformance with 216digital

When it comes to WCAG conformance, aiming for Level AA is usually the smart move. It’s realistic, effective, and ensures you’re meeting the needs of most users. If you can, sprinkle in some Level AAA features to go the extra mile.

Making your website accessible isn’t just about ticking off a checklist—it’s about creating a welcoming space for everyone. With regular updates, audits, and a commitment to accessibility, you’ll not only meet the standards but also build a site people love to use.

If you’re unsure where to begin or want to check your progress, 216digital is here to help. Schedule an ADA briefing with our team to learn how we can help you achieve WCAG conformance, lower your legal risks, and create a better experience for all your users.

Take the first step today—because accessibility isn’t just a requirement, it’s an opportunity to make your website better for everyone.
Greg McNeil

November 15, 2024

WCAG Compliance

Accessibility, WCAG, WCAG conformance, Website Accessibility
Should Designers Hit Pause on Animation?
Animation can bring a website to life, but have you ever considered how it impacts all users? While animations and gifs can make a site feel more dynamic, they can also cause some visitors discomfort—or worse—. Let’s explore why animations can be tricky from an accessibility standpoint and how you can design them to be both engaging and inclusive.

Why Animation Can Be Problematic

Animations aren’t just flashy extras—they can deeply affect how users experience your website, and not always in a good way.
- Motion Sensitivity: Some people have vestibular disorders that make them sensitive to movement on screens. Animations like parallax scrolling or sliding elements can trigger dizziness, vertigo, or nausea.
- Seizures: Flashing lights or strobing effects can be dangerous for users with photosensitive epilepsy. Even subtle flickers can cause issues.
- Cognitive Overload: Busy or overly complex animations can overwhelm users with cognitive impairments, making it hard for them to focus or understand the content.
- Assistive Technology Interference: Screen readers and other tools can struggle with animations that change content dynamically, leading to confusion.
These challenges highlight why designers need to think critically about when and how they use animations.

Does Your Design Really Need Animation?

Not every project calls for animation. Before you add that fancy effect, ask yourself:
- Does it serve a purpose?
- Will it help users navigate or understand the site?
- Could it distract or overwhelm someone?
Animations should always have a clear function, like drawing attention to a call-to-action or giving feedback on an interaction. If the animation doesn’t improve usability, it might be best to skip it.

Making Animations Accessible

If you must use an animation, here are some tips to ensure it doesn’t cause issues for people with cognitive or visual impairments:
1. Keep It Simple: Avoid overly elaborate or decorative effects. Subtle transitions or fades can be just as effective without being overwhelming.
2. Mind the Timing: Speed matters. Too fast, and users might get lost; too slow, and they could grow impatient. Aim for a balance that feels natural.
3. Give Users Control: All animations should have visual and accessible controls to pause and play the animation. Always respect the prefers-reduced-motion media query.
4. Focus on Purpose: Every animation should add value. Whether it’s guiding users or making content clearer, make sure it serves a meaningful purpose.
A Quick Fix with prefers-reduced-motion

One of the easiest ways to address motion sensitivity is by using the prefers-reduced-motion media query. This CSS feature checks if a user has reduced motion enabled on their device and adjusts animations accordingly.

Here’s how you can tone down animations for users who prefer less motion:
```
@media (prefers-reduced-motion: reduce) {  
  .animated-element {  
    animation: none;  
    transition: none;  
  }  
}  
```
Want to simplify rather than completely disable? Try this:
```
@media (prefers-reduced-motion: reduce) {  
  .fade-in {  
    animation: fade-in 0.5s linear;  
  }  
}  
@keyframes fade-in {  
  from { opacity: 0; }  
  to { opacity: 1; }  
}  
```
This approach keeps your design functional while reducing the risk of discomfort for sensitive users.

What Does WCAG Say About Animation?

The Web Content Accessibility Guidelines (WCAG) offer clear rules about animations. Two of the most relevant criteria are:
- 2.3.1: Three Flashes or Below Threshold
- Avoid animations that flash more than three times per second. It’s a crucial step in reducing the risk of seizures.
- 2.3.3: Animation from Interactions
- If animations are triggered by user actions, make sure they can be disabled without affecting functionality.
Following these guidelines helps ensure your site is usable for everyone.

Testing Your Animations

Testing is an essential part of designing accessible animations. Here’s how to do it effectively:
- Check Motion Settings: Turn on the “reduce motion” setting on your device (available on macOS, Windows, iOS, and Android) and see how your site responds.
- Try Keyboard Navigation: Ensure animations don’t interfere with keyboard functionality. Can users still tab through links and buttons smoothly?
- Use Automated Tools: Tools like Lighthouse can catch accessibility issues related to animations.
- Gather Feedback: Get input from real users, especially those with disabilities. They’ll provide insights you might not have considered.
Accessible Animation with JavaScript

Sometimes, you’ll need JavaScript to handle animations. You can still make them accessible by pairing JavaScript with prefers-reduced-motion.

Here’s a quick example:
```
const reduceMotion = window.matchMedia('(prefers-reduced-motion: reduce)');  
if (reduceMotion.matches) {  
  // Turn off animations for users who prefer reduced motion  
  document.querySelector('.animated-element').style.animation = 'none';  
} else {  
  // Keep animations for everyone else  
  document.querySelector('.animated-element').classList.add('run-animation');  
}   
```
This snippet ensures your animations adapt to user preferences without requiring manual toggles.

Wrapping It Up

Animations can be a powerful tool for creating engaging, interactive websites—but they should never come at the expense of accessibility. By keeping animations simple, purposeful, and user-controlled, you can deliver a better experience for all your visitors.

Don’t forget to test your designs with real users and tools, and make use of features like prefers-reduced-motion to accommodate different needs. Thoughtful design is inclusive design, and accessible animations are a small change that can make a big difference. If you’re unsure if the animations on your website are accessible or would like an expert partner to help you get started, reach out to 216digital using the contact form below.
Bobby

November 14, 2024

How-to Guides

Accessibility, animation, How-to, web developers, web development, Website Accessibility
Understanding Focus Outlines for Web Accessibility
Have you ever tried navigating a website without a mouse, relying only on your keyboard? It might seem unusual, but for many people with motor disabilities or visual impairments, this is their everyday reality. Focus outlines—the visual markers that highlight where you are on a page—are essential tools that make this possible.

Unfortunately, these outlines often get overlooked or even removed during web design, leaving a significant number of users struggling to navigate sites effectively. Let’s break down what focus outlines are, why they matter, and how you can implement them to make your website more inclusive.

What Is a Focus Outline?

A focus outline is a visual indicator, often a highlighted border or underline, that appears around a web element when it gains keyboard focus. This outline helps users understand which interactive element they are currently on, whether it’s a link, button, form field, or other focusable component. For example, when a user tabs through a webpage, the focus outline moves from one element to the next, providing a visual cue about their current location on the page.

This feedback is essential for users who cannot use a mouse and instead navigate by pressing the “Tab” key to move forward and “Shift + Tab” to move backward. For those relying on screen readers, focus outlines further aid in understanding the structure of a page, confirming the position on the screen, and reducing the cognitive load required to navigate the web effectively.

Why Focus Outlines Matter for Accessibility

Focus outlines aren’t just nice to have—they’re a must-have for accessibility. According to the Web Content Accessibility Guidelines (WCAG), specifically criterion 2.4.7: Focus Visible, mandate that any keyboard-operable interface must have a visible focus indicator. This ensures that users relying on keyboard navigation always know where they are on the page.

Who Benefits from Focus Outlines?

For users with motor disabilities, such as those who have difficulty controlling fine motor movements or are unable to use a mouse, keyboard navigation is a primary means of interacting with digital content. The focus outline serves as a reliable marker of where they are on the page, making navigation smooth and efficient. People with low vision or visual impairments who use high-contrast settings also rely on focus outlines for an additional layer of navigation support, enabling them to visually follow along.

Legal and Ethical Responsibilities

Beyond enhancing the user experience, implementing visible focus outlines is a legal and ethical responsibility for organizations. Without them, websites may fail to meet accessibility standards, putting them at risk of non-compliance with the WCAG guidelines. For organizations, following WCAG isn’t just about adhering to regulations; it’s about creating an inclusive experience that all users can navigate.

How to Create Accessible Focus Outlines

Making focus outlines accessible and noticeable is all about ensuring they stand out. Here are some tips:
- Use Sufficient Color Contrast: Choose colors that contrast well with both the element and the background.
- Choose a Noticeable Style: Solid, dotted, or dashed lines can all work, as long as they’re easily visible.
- Adjust Thickness: A thicker outline can be more eye-catching and easier to see.
How to Style Focus States Using CSS

Outlines can be solid, dotted, or dashed lines, as long as they are visible. Adjusting the thickness can also make the outline more noticeable.

Example: Basic Focus Outline with CSS
```
button:focus,
a:focus {
  outline: 3px solid #007acc;
}
```
In this example, we’ve applied a 3-pixel solid blue outline to buttons and links when they’re focused. Before finalizing colors, use tools like the WebAIM Contrast Checker to ensure they meet the recommended contrast ratio of at least 3:1 for user interface components.

Add Background Effects

For a more custom look, consider adding a background color or shadow effect:
```
button:focus {
  outline: none;
  box-shadow: 0 0 5px 2px rgba(0, 122, 204, 0.8);
}
```
This replaces the default outline with a subtle glow, making the focused element stand out without clashing with your design. Just remember to test these styles to ensure they’re visible to everyone, including users with visual impairments.

Avoiding Common Mistakes with Focus Outlines

One of the most common pitfalls in web design is removing focus outlines entirely. Designers sometimes find default focus outlines unattractive and may remove them without providing a suitable replacement. While this might make the site look cleaner, it creates significant accessibility barriers for users relying on keyboard navigation. WCAG guideline 2.4.7 requires focus indicators for compliance, so removing focus outlines can result in a failure to meet accessibility standards.

If you’re tempted to hide the default outline, remember that it’s better to customize it than to remove it. Replacing the outline with a custom design can enhance the aesthetics of your website without sacrificing accessibility. Just ensure that your custom design maintains a strong visual presence and sufficient color contrast.

Another common mistake is creating focus outlines that blend too closely with the background. This can happen when designers use colors that don’t contrast well with surrounding elements or backgrounds. Remember, users with low vision may struggle to differentiate between similar shades, so it’s essential to test the visibility of focus outlines across various screens and devices.

Testing Focus Visibility

Testing is a crucial step to ensure your focus outlines are effective:
1. Navigate Your Site Using Only the Keyboard: Press the “Tab” key to move through interactive elements and observe the focus outline.
2. Check Every Interactive Element: Ensure that links, buttons, form fields, and other focusable components have a visible focus state.
3. Assess Visibility and Consistency: The focus outline should be easily noticeable and consistent across your site.
4. Accessibility Tools: Tools like Google Lighthouse or WAVE can check WCAG compliance, including focus outlines.
Make Focus Outlines a Priority

Focus outlines aren’t just a design detail—they’re a vital part of creating an inclusive web experience. By ensuring your site has clear and consistent focus indicators, you can make your website more accessible for everyone. So, take action today to ensure your website is accessible. Your customers—and your bottom line—will thank you!

For personalized guidance on making your website ADA compliant, reach out to 216digital for an ADA briefing. Our experts are here to help you navigate the complexities of web accessibility and secure your business against potential legal risks.
Kayla Laganiere

November 13, 2024

How-to Guides

Accessibility, focus outlines, How-to, web developers, web development, Website Accessibility
Accessibility Checklist: Your Guide to Compliance
Creating an accessible website goes beyond just checking a few boxes—it’s about enabling everyone, including people with disabilities, to engage with your content smoothly. A well-structured accessibility checklist can help you address common barriers, test thoroughly, prioritize fixes, and ensure ongoing compliance with accessibility standards.

Here’s a comprehensive web accessibility checklist to guide you through essential steps:

Understand and Set Your Accessibility Goals

Define accessibility goals based on WCAG (Web Content Accessibility Guidelines) standards.

Before diving into specific changes, remember that your accessibility improvements should align with recognized standards, particularly WCAG 2.1 A/AA levels. Setting these goals from the start ensures your site meets both legal requirements (like ADA compliance in the U.S.) and the diverse needs of your users. Following an accessibility checklist can help ensure each goal is met.

Audit Your Website for Accessibility Gaps

Conduct an initial audit to identify accessibility issues.

An audit gives a clear view of your website’s current accessibility status, spotlighting areas that need attention. Use tools like automated scanners, manual audits, and assistive technologies (AT) such as screen readers to uncover common barriers. An accessibility checklist is helpful here to document each area tested, including:
- Keyboard Navigation: Verify that users can navigate your site without a mouse, using keyboard commands only.
- Color Contrast: Use a contrast checker to ensure text is readable for people with low vision.
- Alt Text for Images: Check that all images have descriptive alt attributes, making content accessible for visually impaired users.
Ensure Keyboard Navigation is Intuitive

Ensure users can navigate your site fully with a keyboard.

Keyboard navigation is essential for users who don’t use a mouse. This includes making sure all interactive elements like buttons, forms, and links are accessible with the “Tab” and “Enter” keys.
- Focus States: Make sure focus states (visual indicators for keyboard users) are visible and defined.
- Logical Order: Verify that the tab order follows a logical sequence, mirroring the visual layout.
To learn more about keyboard navigation, check out our article, “What is Keyboard Navigation?”

Implement Proper Use of Alt Text for Images

Add descriptive alt text to all informative images.

Alt text serves as an alternative to images, allowing screen readers to describe visuals to visually impaired users.
- Functional vs. Decorative: Use alt text for images conveying essential information. Use alt=”” for decorative images to prevent screen readers from reading unnecessary details.
- Descriptive Text: Avoid vague descriptions like “image” and offer concise, informative details to convey the image’s purpose.
For additional information about alt text, read our article “Understanding Image Alt Text Descriptions.”

Ensure Sufficient Color Contrast

Check and adjust color contrast to meet accessibility standards.

Adequate contrast between text and background ensures readability, especially for users with visual impairments. WCAG recommends a minimum contrast ratio of 4.5:1 for regular text and 3:1 for larger text.
- Tools: Use WebAIM’s Contrast Checker to verify compliance.
- Avoid Color-Only Cues: Avoid relying solely on color to convey important information, as colorblind users might miss these cues. Pair colors with other indicators, like icons or text labels.
Use Semantic HTML Structure

Build a well-structured HTML hierarchy for better accessibility.

A clear HTML structure is essential for screen readers and other assistive devices. Proper tags help convey the structure and purpose of your content.
- Headings: Use heading tags (<h1>, <h2>, etc.) in a logical order, guiding users through content.
- Landmarks: Include ARIA landmarks like role= “navigation” and role= “main” for easier page navigation.
- Lists and Tables: Use HTML lists for lists and tables for data, not layout purposes.
Check out our articles, “How Semantic HTML Improves Your Accessibility & SEO?” or “How to Implement ARIA Landmarks and Roles for Better Accessibility” for a deeper dive into semantic HTML and ARIA landmarks.

Test with Assistive Technologies

Test your website with various assistive technologies.

Testing with AT tools like screen readers, voice recognition, and magnification provides insights into your site’s accessibility. Common screen readers include JAWS, NVDA, and VoiceOver.
- Screen Reader Testing: Check that all text, buttons, and links are accessible with screen readers.
- Voice Navigation: Confirm that users can navigate all interactive elements using voice commands.
- Magnification Tools: Ensure that the design remains usable when zoomed to 200%.
Incorporate Accessible Forms

Design forms with clear labels and error messages.

Accessible forms enable users to enter information accurately and with ease.
- Labels and Instructions: Each form field should have a visible label. Use placeholder text sparingly.
- Error Handling: Provide clear error messages when input is invalid. Describe what went wrong and how to fix it.
- Field Focus: Ensure that after submission, the keyboard focus moves to the first field needing correction.
Conduct Remediation Based on Prioritized Issues

Address identified accessibility issues based on their impact.

After auditing, prioritize fixes by severity and frequency. Address critical issues first, especially those that affect navigation and content comprehension.

Implement Continuous Monitoring with Tools Like a11y.Radar

Set up ongoing accessibility monitoring to maintain compliance.

Web accessibility is a continuous effort. New content or design changes can create new barriers, so ongoing monitoring tools like a11y.Radar can be part of your accessibility checklist, alerting you to real-time issues.
- Real-Time Alerts: Get notifications for new issues, allowing for prompt fixes.
- Automated Reports: Schedule regular accessibility reports to stay aware of your compliance status.
Conduct Routine Manual and Automated Testing

Schedule consistent accessibility testing intervals.

Automated tools are helpful for common issues, but manual testing finds more complex accessibility gaps. A mix of both ensures a thorough evaluation.
- Automated Testing: Use tools like Google Lighthouse or WAVE for quick assessments.
- Manual Testing: Focus on custom components that automated tools may not fully catch.
Keep Up-to-Date with WCAG Guidelines

Stay current on WCAG updates and best practices.

Accessibility standards evolve to meet new needs. KRegularly updating your accessibility checklist ensures compliance with the latest WCAG guidelines, like WCAG 2.2 or 3.0.
- Review WCAG Changes: Familiarize yourself with new criteria.
- Align with a11y.Radar: Ensure your monitoring tools adapt to updates, maintaining continuous compliance.
Take the First Step Towards Accessibility

Creating an accessible website is essential not only for compliance but for providing a truly inclusive experience for all users. By following a structured approach to accessibility—setting goals, auditing your site, prioritizing fixes, and maintaining continuous monitoring—you’re laying a solid foundation for an accessible, user-friendly site.

If you’re ready to make accessibility a priority but need guidance on how to navigate ADA compliance, consider scheduling an ADA briefing with 216digital. Our team can help you navigate accessibility standards, pinpoint key areas for improvement, and develop a checklist tailored to your site’s needs. Take the first step toward making your website accessible to all—schedule your ADA briefing with 216digital today and ensure your digital presence is compliant, inclusive, and welcoming.
Greg McNeil

November 12, 2024

How-to Guides

Accessibility, accessible checklist, How-to, Website Accessibility

What Are Web Accessibility Evaluation Tools?

Why Are They Important?

Benefits of Using Web Accessibility Evaluation Tools

How to Choose the Right Accessibility Evaluation Tool

What to Look for in Web Accessibility Evaluation Tools

a11y.Radar ADA Monitoring

How Does a11y.Radar ADA Monitoring Work?

Limitations of Automated Tools

Practical Tips for Using Accessibility Tools

Make Accessibility a Priority

Why Chatbot Accessibility Matters

Common Barriers in AI Chatbots

Incompatible with Screen Readers

Keyboard Navigation Failures

Unclear or Missing Focus Indicators

Overly Complex or Jumbled Responses

Time Constraints

Lack of Alternative Communication Options

How to Build an Accessible Chatbot

Use Semantic HTML for Chatbot Elements

Support Keyboard Navigation

Provide Descriptive ARIA Labels

Design with Simplicity in Mind

Allow for Adjustable Timing

Include Accessible Focus Indicators

Provide Alternatives to Chatbots

Testing Chatbot Accessibility

Manual Testing with Screen Readers

Keyboard Navigation Tests

Automated Tools

User Feedback

Meeting WCAG Standards for Chatbots

Wrapping Up

What Are Skip Links and Why Are They Important?

The Key Benefits of Skip Links

Improved Navigation for Keyboard-Only Users

Enhanced Experience for Screen Reader Users

Better Usability for Assistive Technologies

Increased Accessibility Compliance

How Do Skip Links Work?

The Technical Mechanics of Skip Links

HTML Structure with <a href> Tags

tabindex Attribute

aria-label and aria-hidden Attributes

A Simple Skip Link Example

Styling Skip Links

JavaScript for Enhanced Skip Link Functionality

Testing Skip Links for Accessibility

Challenges with Skip Links

Skip Ahead to Success

What Are Website Accessibility Overlays?

Legal Risks of Accessibility Overlays

False Sense of Compliance

Increased Legal Vulnerability

Misleading Claims

Reputational Risks of Accessibility Overlays

Negative Feedback from Users

Advocacy Group Backlash

Erosion of Trust

Financial Risks of Accessibility Overlays

Recurring Costs Without Long-Term Benefits

Cost of Legal Defense

Lost Revenue from Alienated Customers

The Limitations of Accessibility Overlays

A More Authentic Approach to Web-Accessibility

Accessibility Audits

Remediation of Core Issues

Ongoing Maintenance

User-Centered Design

Expert Partnerships

Why Businesses Should Avoid the Widget Trap

Schedule an ADA Briefing with 216digital

What is ADA Compliance?

What is Section 508 Compliance?

The Key Differences Between ADA and Section 508 Compliance

Scope of Applicability

Specificity of Standards

Enforcement

Similarities Between ADA and Section 508 Compliance

The Goal of Accessibility

HTML Structure with `<a href>` Tags

`tabindex` Attribute

`aria-lab`el and `aria-hidde`n Attributes