Digital Marketing Tips and Strategies to Grow Your Business

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 Retailers Can Expect if They Aren’t Accessible
In today’s digital marketplace, overlooking the accessibility of your website isn’t just a technical oversight—it’s a legal and financial pitfall that could jeopardize your entire business. As consumers increasingly flock to online shopping, retailers have a critical responsibility to ensure their websites are accessible to everyone, including people with disabilities. Failing to meet ADA compliance requirements isn’t just non-compliance; it’s an open invitation to lawsuits, hefty fines, and damaging publicity. The clock is ticking, and the stakes have never been higher. Is your business prepared to face the consequences of an inaccessible website?

Understanding ADA Compliance and Accessibility Laws

The Americans with Disabilities Act (ADA) was passed in 1990 to ensure that individuals with disabilities have equal access to public spaces. While the law was initially focused on physical spaces, such as stores and offices, the scope has expanded with the rise of the Internet. Today, many courts interpret the ADA as applying to websites, meaning retailers’ websites must be accessible to people with disabilities, including those who are blind, deaf, or have other impairments.

ADA Guidelines for Web Accessibility

Under ADA guidelines, businesses must make reasonable accommodations for disabled individuals by ensuring that their websites are usable by people who rely on screen readers, text-to-speech software, and other assistive technologies. If your website doesn’t meet these requirements, you might find yourself at risk for a lawsuit.

What Are the Legal Risks for Retailers?

If your website isn’t accessible, your business could be exposed to legal action. Retailers face the possibility of demand letters from law firms representing plaintiffs with disabilities. These letters often demand that companies make changes to their websites and may include a settlement request to avoid a lawsuit. A formal lawsuit could follow if these demands are ignored or if the retailer refuses to comply with ADA compliance.

Common Accessibility Issues in Lawsuits
- Images without Alt Text: Alt text describes the content of an image for screen readers. Missing alt text excludes visually impaired users from critical information.
- Unlabelled Form Fields: Forms need clear labels and instructions for accessibility. Missing labels can lead to frustration and abandoned purchases.
- Unclear or Missing Headings: Headings help organize content, making it easier for visually impaired users to navigate.
- Non-Keyboard Accessible Navigation: Some users rely on keyboard shortcuts instead of a mouse. Websites not designed for keyboard navigation can exclude these users.
The Cost of Non-Compliance

So, what happens when a retailer faces a lawsuit or demand letter for not meeting ADA compliance?

Legal Costs

Defending against a lawsuit can be expensive, even if you ultimately win. The average cost of defending a web accessibility lawsuit can run tens of thousands of dollars. This does not include legal fees for settlements or necessary website updates.

Settlements

Many retailers choose to settle lawsuits rather than risk the expense and uncertainty of court. Settlement amounts can vary but often reach six figures. Additionally, companies must typically commit to updating their website for compliance, further adding to costs.

Fines

While the ADA itself doesn’t specify fines, related laws, like the Rehabilitation Act, require federal agencies to ensure accessibility. Violations can lead to significant fines, especially for businesses that accept federal funds or contracts.

Damage to Brand Reputation

Beyond legal costs, lawsuits over website accessibility can damage a brand’s reputation. A public lawsuit can erode consumer trust, lead to negative media coverage, and even cause loyal customers to lose faith in the inclusivity of your business.

Loss of Customers and Sales

The financial impact doesn’t stop with legal costs. Inaccessible websites exclude millions of potential customers, especially those with visual impairments. Poor user experiences can lead to lost sales and customer frustration.

Big Brands, Bigger Penalties

Web accessibility is no longer a theoretical risk—it’s a pressing reality affecting retailers across industries. In recent years, well-known brands have faced significant legal challenges for not meeting ADA compliance standards, underscoring the tangible consequences of non-compliance. Notable cases include:

Target Corporation Settlement

In a landmark 2006 case, the National Federation of the Blind (NFB) sued Target Corporation, arguing that its website’s inaccessibility violated the ADA, barring blind users from equal access to online services. This case culminated in a $6 million settlement in 2008, with Target committing to WCAG 2.0 standards. The settlement set a powerful precedent, establishing that websites are indeed extensions of physical stores and must comply with ADA standards.

Beyoncé’s Parkwood Entertainment

In 2019, a lawsuit against Parkwood Entertainment—the company managing Beyoncé’s official website—brought celebrity and entertainment sites into the accessibility spotlight. The case highlighted key issues, like missing alt text and inaccessible navigation, underlining that ADA compliance requirements extend to all online sectors.

Dick’s Sporting Goods

In 2021, Dick’s Sporting Goods faced a lawsuit over a lack of accessible design elements, from missing alt text to insufficient screen reader support. This case reaffirmed that even leading retailers are vulnerable if they overlook essential accessibility features.

A Surge in Accessibility Lawsuits and the E-Commerce Sector

The growing number of lawsuits drives home the urgency for retailers to proactively address web accessibility. According to Useablenet in 2023 alone, more than 4,600 ADA-related website accessibility cases were filed, with 82% targeting the retail sector. As consumers increasingly rely on online shopping, accessibility becomes essential for retailers to stay competitive and inclusive.

Why E-Commerce Faces Elevated Legal Risks

Retailers with online sales channels, particularly in e-commerce, face intensified scrutiny as customers with disabilities encounter persistent barriers to shopping online. According to the U.S. Center of Disease Control, 7.6 million Americans with visual impairments struggle with inaccessible websites, translating to missed revenue opportunities. By not prioritizing accessibility, e-commerce retailers risk losing out on an estimated $7 trillion in annual spending from the global disability market.

The message is clear: the cost of non-compliance is high, and accessibility lawsuits are on the rise. For retailers, these cases underscore the importance of making accessibility a strategic priority to safeguard brand reputation and revenue alike.

How to Avoid the Legal Pitfalls

If you’re a retailer, the best way to avoid legal issues is to proactively make your website accessible. Here’s how to get started:

Conduct an Accessibility Audit

Use accessibility tools or hire an expert to evaluate your website. Many free and paid tools are available to help identify common accessibility issues.

Follow WCAG Guidelines

The Web Content Accessibility Guidelines (WCAG) set the standard for web accessibility, covering elements like text readability, video captioning, and more.

Train Your Team

Ensure that your website’s content managers are trained in accessibility best practices, helping you avoid common errors and keep your site compliant with updates.

Stay Informed

Accessibility laws and best practices are evolving, so it’s essential to stay updated on the latest requirements and trends.

Secure Your Website’s Future

ADA compliance isn’t just a legal obligation—it’s an opportunity to make your website more inclusive and accessible to a wider audience. Retailers who fail to make their websites accessible face serious legal risks, including lawsuits, legal fees, and damage to their brand’s reputation. On the flip side, ensuring your website is accessible to all users can boost customer trust, loyalty, and, ultimately, sales. By taking the necessary steps to make your website compliant with ADA standards, you protect your business and demonstrate your commitment to inclusivity.

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.
Greg McNeil

November 11, 2024

Legal Compliance

Accessibility, ADA Compliance, ecommerce website, Retail, Web Accessibility
Why Touch Targets Impacts Accessibility
Imagine this: a customer visits your website, excited to snag a deal on their holiday shopping list. They’re scrolling through your page on their phone, ready to click “add to cart,”—but then they hit a roadblock. The buttons are too small, links are crowded together, and navigating your site becomes a frustrating game of “tap and hope.” Now imagine if that customer has limited dexterity or relies on assistive technology. For them, those tiny buttons and cramped links aren’t just an inconvenience; they’re a barrier.

Accessibility issues like these don’t just affect your users’ experience—they impact your bottom line and even your legal compliance. Making sure your site’s touch targets are easy to interact with is one of the simplest yet most impactful changes you can make. In this guide, we’ll cover why large, accessible touch targets matter, how they boost usability for everyone, and what steps you can take to ensure your site is welcoming to all.

What Are Touch Targets and Why Are They Important?

Touch targets are interactive elements—such as buttons, links, and form controls—that users engage with as they navigate your website. The size and spacing of these elements can make or break the experience, especially for users on mobile devices or those with physical limitations. If touch targets are too small or closely spaced, users may struggle to click or tap accurately, leading to frustration and a poor experience. This can be particularly challenging for older adults and individuals with limited dexterity.

Making touch targets sufficiently large and spaced out allows everyone to navigate and interact with your site more easily, enhancing both usability and inclusivity. This is a foundational aspect of web accessibility that ensures your website works well for all.

WCAG Guidelines: Key Standards for Touch Target Size

To provide clear guidance on accessible touch target sizes, the Web Content Accessibility Guidelines (WCAG) have established several success criteria. WCAG 2.1 and the updated WCAG 2.2 outline standards to help developers make online content accessible, mainly through adequately sized touch targets.

Success Criterion 2.5.5 (Target Size)

In WCAG 2.1, Criterion 2.5.5 specifies that interactive elements should meet a minimum touch target size of 44×44 pixels, making it easier for users with limited motor skills or assistive technology to select the right element.

Success Criterion 2.5.8 (Target Size – Enhanced)

WCAG 2.2 expands on this with Criterion 2.5.8, recommending even larger touch targets when interactive elements are positioned close together. This helps users avoid accidentally tapping the wrong element, especially on mobile devices or when using screen readers.

These guidelines establish a foundation for accessible design, giving developers clear targets to create user-friendly, inclusive sites that reduce errors and improve the overall user experience.

Best Practices for Designing Accessible Touch Targets

With WCAG standards in mind, you can take steps to create touch targets that enhance usability. Here are some essential practices for implementing accessible interactive elements:

Use Adequate Padding and Margin

Padding and margins around buttons and links help ensure they meet minimum size requirements while maintaining a clean visual layout. For example:
```
button {
  padding: 12px 20px; /* Increases padding for larger touch target */
  font-size: 16px;
}
```
Ensure Minimum Width and Height

Using min-width and min-height properties guarantees that buttons and other elements stay at least 44×44 pixels, even when the element content is smaller. This maintains accessibility across different screen sizes.
```
button {
  min-width: 44px;
  min-height: 44px;
}
```
Space Out Interactive Elements

Placing enough space between buttons and links prevents mis-taps and ensures usability for all users, especially those on mobile devices or using assistive technologies.
```
button, a {
  margin: 10px;
}
```
Add ARIA Attributes for Enhanced Accessibility

ARIA attributes (Accessible Rich Internet Applications) add context to interactive elements for users relying on assistive devices. For instance, using aria-expanded or aria-haspopup on a menu button helps screen reader users understand its function.
```
<button aria-expanded="false" aria-haspopup="true">Menu</button>
```
Responsive Design: Ensure Touch Target Size Across Devices

Since many users rely on mobile devices for browsing, it’s essential to make touch targets easily accessible on smaller screens. Using responsive CSS ensures that touch targets adapt to various screen sizes:
```
@media (max-width: 600px) {
  button {
    padding: 15px 25px; /* Larger padding on smaller screens */
  }
}
```
Testing Touch Target Accessibility

Once you’ve optimized your touch targets, testing is essential to ensure they’re functional and accessible. Here are a few testing strategies to confirm usability:
- Manual Testing: Test your site on various devices (desktop, tablet, mobile) to ensure touch targets are easy to access and use.
- Accessibility Tools: Tools like Google Lighthouse or WAVE can check WCAG compliance, including touch target sizes.
- User Testing: Feedback from real users, particularly those with disabilities, is invaluable for assessing how accessible and user-friendly your touch targets are.
Wrapping Up

Improving touch target accessibility is just one of many steps toward making your website genuinely inclusive and user-friendly. By focusing on accessible design, you not only enhance the experience for users with mobility challenges and those using assistive technologies but also build a site that’s welcoming and intuitive for everyone. Following WCAG guidelines, using best coding practices, and regular testing are essential—but navigating these standards alone can be overwhelming.

If you’re ready to take accessibility seriously and want to ensure your site is fully ADA-compliant, consider scheduling an ADA briefing with 216digital. Our team of accessibility experts can help you identify potential compliance issues, create actionable solutions, and guide you through the process of building a more accessible and inclusive website. Reach out today to learn how we can help safeguard your site and open new opportunities with ADA compliance.
Greg McNeil

November 8, 2024

How-to Guides

Accessibility, How-to, touch targets, web developers, web development, Website Accessibility
Web Accessibility for Senior Citizens: A Business Case

Have you ever stopped to think about how accessible your website is for senior citizens? You might imagine accessibility only in terms of helping people with visual or hearing impairments, but what about the growing number of seniors who are online every day? Seniors often face unique challenges when navigating websites—things like vision loss, reduced motor skills, and even cognitive decline. As their online presence continues to increase, it’s crucial to ask: Do you have an accessible site? The answer might surprise you.

Making your website senior-friendly isn’t just the right thing to do—it’s a smart business move that can bring both legal and financial rewards. Let’s explore why investing in web accessibility for seniors is a move you can’t afford to overlook.

What Is Web Accessibility?

Web accessibility refers to the practice of designing websites and digital content so that they can be easily accessed and used by all people, including those with disabilities. It’s not just about compliance with regulations or making sure that people with visual or hearing impairments can use your site. Accessibility also benefits people with other challenges, such as limited mobility or cognitive impairments.

Why Does It Matter for Senior Citizens?

Senior citizens—particularly those over 65—are a growing segment of internet users. In fact, according to a study by the Pew Research Center, 73% of people aged 65 and older are now online, and 61% of them use the internet every day. However, many older adults face unique challenges when using websites, such as vision loss, hearing impairments, reduced fine motor skills, and cognitive decline. This is where web accessibility plays a crucial role.

By ensuring your website is accessible to seniors, you’re not just creating a better user experience for them—you’re opening your business up to a larger market with significant spending power.

The Legal Landscape: ADA and Accessibility

In the United States, businesses are legally required to ensure that their websites are accessible to people with disabilities. The Americans with Disabilities Act (ADA), passed in 1990, mandates that public accommodations—such as businesses, government entities, and nonprofit organizations—provide equal access to their services for people with disabilities. While the law doesn’t explicitly mention websites, courts have increasingly interpreted it to apply to digital spaces.

Legal Risks of Non-Compliance

This means that if your website is not accessible to people with disabilities—including older adults—you could be at risk for legal action. Many businesses have been sued over accessibility violations, with settlements reaching millions of dollars. Even if you’re a small business owner or running a personal blog, failing to provide an accessible experience could open you up to potential lawsuits, fines, or reputational damage.

For example, large companies like Target and Domino’s Pizza have faced high-profile lawsuits for not having accessible sites. These cases highlight the importance of taking accessibility seriously, not just as a moral or ethical issue but as a business risk.

Financial Benefits: Reaching a Larger, Wealthy Audience

One of the most compelling reasons to focus on web accessibility for seniors is the financial advantage. Seniors, particularly those in the 65+ age range, wield significant purchasing power. According to the AARP, people over 50 account for more than $8 trillion in economic activity in the U.S. every year. That’s a massive market—one that’s only going to grow as the senior population continues to expand.

How Accessibility Boosts Your Bottom Line

However, many businesses fail to recognize the importance of this demographic when designing their websites. If your website isn’t accessible, you’re essentially alienating an entire group of people who might have the money and the intent to buy from you. In contrast, an accessible site can tap into this valuable market by ensuring that seniors have a seamless, positive experience when browsing and making purchases online.

Here are some key ways web accessibility can boost your bottom line:

Improved Conversion Rates on Accessible Sites

When seniors can easily navigate your site, understand your content, and complete purchases without frustration, you’ll see higher conversion rates. Research shows that accessibility improvements can lead to better engagement, longer time spent on the site, and more frequent purchases. Whether you run an e-commerce store or offer a service, providing an accessible site can lead to more successful transactions.

Expanding Your Reach

Web accessibility isn’t just about meeting the needs of those with disabilities—it’s also about creating a better experience for everyone. Simple improvements, like larger fonts, clearer color contrast, or the ability to adjust text size, benefit not just seniors but a wide range of users. As your website becomes more accessible to navigate for seniors, you’re also making it more user-friendly for all visitors, which can attract more people and boost your website traffic.

Reducing Bounce Rates

A website that’s hard to use leads to frustrated visitors, and frustrated visitors often leave. If seniors (or anyone else) find your site difficult to navigate or read, they’re likely to abandon it in favor of a competitor’s site. Ensuring your site is accessible makes it more likely that users will stay longer, browse more pages, and return again.

Brand Loyalty and Word-of-Mouth

By demonstrating your commitment to accessibility, you’re sending a powerful message to your customers that you care about inclusivity. This can lead to stronger brand loyalty and positive word-of-mouth referrals. Seniors, like all customers, appreciate brands that make an effort to meet their needs, and they are more likely to become repeat customers. This loyalty can help your business grow over time.

Social Benefits: Building an Inclusive Brand

In today’s competitive market, inclusivity is more than just a buzzword—it’s an expectation. Consumers increasingly expect companies to be socially responsible, and that includes providing accessible sites for people with disabilities. When your website is accessible to seniors, you’re showing that your brand is forward-thinking, compassionate, and dedicated to serving everyone.

This kind of brand identity can strengthen your reputation and create emotional connections with your customers. A business that values diversity and inclusivity is more likely to resonate with socially conscious consumers, not just seniors.

Corporate Social Responsibility (CSR)

Investing in web accessibility shows that your company is taking steps to fulfill its corporate social responsibility. By ensuring that all people, regardless of age or ability, can engage with your business, you’re positioning yourself as a leader in social responsibility. Consumers are increasingly making decisions based on their values, and a company that prioritizes accessibility can stand out in a crowded marketplace.

Fostering a Positive Reputation

The world is becoming more focused on accessibility, and businesses that lead the charge will be seen as industry pioneers. If you prioritize accessibility, you’re likely to gain recognition and respect for your commitment to inclusivity, both from customers and from the broader business community.

Stay Ahead of the Curve with an Accessible Site

As the senior population continues to grow, the demand for accessible sites will only increase. By taking proactive steps now to make your website accessible, you’re positioning your business to meet future needs. Businesses that adapt early will have a competitive edge over those that wait until accessibility is a legal requirement or until they lose customers because of accessibility issues.

Furthermore, accessibility features that are beneficial for seniors—such as voice recognition, screen readers, or simple navigation—are often beneficial to younger audiences as well. This means that your investment in accessibility has the potential to benefit a wide range of users, not just seniors.

A Forward-Thinking Investment

Web accessibility for senior citizens is not just about compliance; it’s a strategic business move that can expand your market reach, boost conversion rates, and strengthen your brand’s inclusivity. With the financial, social, and legal benefits clear—and a growing senior population—now is the perfect time to make your website accessible to all.

Ready to take the next step? Schedule an ADA briefing with 216digital today. Our team of experts will guide you through the process of enhancing your website’s accessibility, ensuring you meet legal requirements while providing an exceptional user experience for all visitors. Don’t miss this opportunity to future-proof your business and tap into a wider audience.

Greg McNeil

November 7, 2024

The Benefits of Web Accessibility

ADA Compliance, Benefits of Web Accessibility, business case for web accessibility, Web Accessibility
How to Build Accessible React Applications
Building an accessible React application means designing a site that everyone, including people with disabilities, can use and enjoy. Accessibility in web apps isn’t just a legal or ethical responsibility—it’s also a best practice that improves user experience for everyone. React, with its dynamic and component-based nature, offers much flexibility, but without careful planning, accessibility can fall through the cracks. This guide will walk you through critical practices to build a more accessible React app, covering essential tools, effective HTML and ARIA usage, keyboard accessibility, and screen reader management.

Why Accessibility in React Matters

An accessible React app does not create obstacles for people who rely on assistive technology like screen readers, keyboards, or other devices. According to Web Content Accessibility Guidelines (WCAG), making web content accessible means people of all abilities can navigate, understand, and interact with your content. With tools and techniques tailored for React, you can ensure that users with disabilities get the best experience possible.

Setting Up an Accessibility-Friendly Development Environment

Setting up your React environment to catch accessibility issues early is a powerful way to build accessible applications. A highly recommended tool for React is eslint-plugin-jsx-a11y, which catches JSX-specific accessibility issues directly in your code editor.

Installing eslint-plugin-jsx-a11y

Install the plugin:
```
npm install eslint-plugin-jsx-a11y --save-dev
```
Configure ESLint: Add the plugin to your ESLint configuration file.
```
{
  "plugins": ["jsx-a11y"],
  "extends": [
    "eslint:recommended",
    "plugin:jsx-a11y/recommended"
  ]
}
```
This plugin identifies accessibility issues in JSX, such as missing ARIA roles, empty <alt> attributes on images, and improper keyboard handling.

The Power of Semantic HTML in React

When it comes to accessibility, semantic HTML is your best friend. Semantic elements like <button>, <header>, and <nav> are designed to convey meaning and functionality to both browsers and screen readers. This minimizes the need for ARIA roles and additional attributes, as semantic HTML elements come with built-in keyboard accessibility and screen reader support.

Examples of Semantic HTML in React

Using semantic elements directly in React makes components accessible by default. For example:
```
import React from 'react';
function AppHeader() {
  return (
    <header>
      <h1>Welcome to My Store</h1>
      <nav>
        <a href="#home">Home</a>
        <a href="#products">Products</a>
        <a href="#contact">Contact</a>
      </nav>
    </header>
  );
}
export default AppHeader;
```
Avoid Using <div> and <span> for Interactive Elements

Avoid using generic elements like <div> and <span> to create buttons or links, as these don’t include native keyboard or accessibility functionality. Instead, use <button> and <a> elements to ensure proper accessibility and functionality. For example:
```
function IconButton() {
  return <button aria-label="Open settings" onClick={() => alert('Settings')}>⚙️</button>;
}
```
Enhancing Accessibility with ARIA Roles (But Use Them Wisely)

ARIA (Accessible Rich Internet Applications) can make custom elements accessible when there’s no HTML equivalent. However, it’s essential to use ARIA roles to enhance existing semantic elements rather than replace them.

Using aria-label for Accessibility

Sometimes, buttons or icons need additional context for screen readers. The aria-label attribute provides descriptive text to communicate functionality.
```
function IconButton() {
  return <button aria-label="Open settings" onClick={() => alert('Settings')}>⚙️</button>;
}
```
Dynamic Updates with aria-live

React apps often have dynamic content. Use aria-live regions to notify screen readers about important changes.
```
function AlertMessage({ message }) {
  return (
    <div aria-live="assertive">
      {message}
    </div>
  );
}
```
Keyboard Accessibility and Focus Management

Keyboard accessibility ensures users can navigate your app without a mouse, which is crucial for many assistive technology users. In React, managing keyboard focus is straightforward with hooks like useRef and useEffect.

Setting Focus with useRef and useEffect

You can use useRef to target an element and useEffect to set focus when a component mounts. This is useful for elements like modals, which should receive focus when they appear.
```
import React, { useRef, useEffect } from 'react';
function Modal({ isOpen, onClose }) {
  const closeButtonRef = useRef(null);
  useEffect(() => {
    if (isOpen) {
      closeButtonRef.current.focus();
    }
  }, [isOpen]);
  return (
    isOpen && (
      <div role="dialog" aria-modal="true">
        <p>Modal content here</p>
        <button ref={closeButtonRef} onClick={onClose}>Close</button>
      </div>
    )
  );
}
```
In this example, the close button gains focus when the modal opens, making navigation intuitive for keyboard users.

Avoiding Focus Traps

Focus traps occur when users get “stuck” within an element, such as a modal, and can’t return to the main content. Ensure that focus can move freely between interactive elements and provide a way to close modals with the Escape key.

Best Practices for Accessible Interactive Elements

When building custom components, pay attention to how they’ll be used with a keyboard:

Provide Clear Labels for Inputs

Forms are essential in any application, and labeling form controls is critical for accessibility. Use labels effectively with inputs, either through <label> elements or aria-label attributes.
```
function NameInput() {
  return (
    <label htmlFor="name">
      Name:
      <input type="text" id="name" aria-required="true" />
    </label>
  );
}
```
Accessible Modals

For custom modal components, set the role= "dialog" and aria-modal= "true" attributes, which inform assistive technology that the content is a modal.

Testing Focus

After adding interactive elements, test that each one can be reached and activated using only the Tab, Enter, and Escape keys. This ensures full keyboard accessibility.

Managing Screen Reader Navigation in SPAs

Single Page Applications (SPAs) often update content dynamically without full page reloads, which can make it difficult for screen reader users to keep track of changes. When the main content area updates, shift focus to the new content or provide a way for screen readers to be alerted about the change.

Example: Setting Focus on Page Updates
```
import React, { useEffect, useRef } from 'react';
function ContentArea({ content }) {
  const contentRef = useRef();
  useEffect(() => {
    contentRef.current.focus();
  }, [content]);
  return (
    <main tabIndex="-1" ref={contentRef}>
      {content}
    </main>
  );
}
```
Here, the main content area receives focus after each update, helping screen reader users navigate SPAs more easily.

Testing Your React App for Accessibility

Testing is crucial to ensure your React application meets accessibility standards. Here are some testing methods and tools:
1. Manual Testing: Use keyboard-only navigation to interact with your app, checking that all elements are accessible and usable. Verify that custom elements respond to the Tab, Enter, and Escape keys.
2. Screen Readers: Test with a screen reader like NVDA (for Windows) or VoiceOver (for macOS). Experience the app as a screen reader user to see how well content updates and ARIA roles are conveyed.
3. Automated Tools: Tools like Google Lighthouse or WAVE identify many accessibility issues. They’re helpful for quickly checking common problems, although they don’t replace manual testing.
Conclusion

Building accessible React applications takes effort but is entirely achievable with the right techniques and tools. Start by setting up your development environment with eslint-plugin-jsx-a11y to catch common issues, and always prioritize semantic HTML elements for inherent accessibility. ARIA roles are powerful but should be used to enhance—not replace—standard HTML.

Ensuring keyboard accessibility, managing focus in SPAs, and regularly testing for accessibility can make a world of difference for users. By following these practices, you’re not only meeting WCAG standards but also creating a better user experience for everyone.

Need help? Reach out to 216digital using the contact form below for a complimentary ADA briefing.
Bobby

November 6, 2024

How-to Guides

ARIA, How-to, React, web developers, web development
Using NVDA to Test Web Accessibility
Making your website accessible isn’t just a checkbox to tick—it’s about creating a space where everyone feels welcome. Imagine trying to browse a site only to hit wall after wall because it wasn’t designed with all users in mind—that’s the reality for millions of people with disabilities. One of the most effective ways to understand and improve your site’s accessibility is by testing it with tools like NVDA (NonVisual Desktop Access). NVDA is a free, open-source screen reader for Windows that provides audio feedback, enabling users who are blind or visually impaired to explore and interact with digital content.

If you’re a developer or designer aiming to make your website user-friendly for everyone, testing with NVDA can be a real eye-opener. This guide will walk you through everything you need to get started—from setting up NVDA to identifying common accessibility barriers. We’ll also compare NVDA with other screen readers and share tips on integrating accessibility checks into your workflow.

Why Testing with a Screen Reader Matters

Testing with a screen reader is crucial for building websites that everyone can use and enjoy. Did you know that over 8 million people in the United States have a visual disability? Worldwide, an estimated 2.2 billion people are affected by some form of visual impairment. That’s a considerable number of users who rely on screen readers like NVDA to navigate the web. Yet, despite this need, studies show that 95.9% of the world’s top million homepages still have detectable accessibility issues, many of which directly impact screen reader users.

Common Accessibility Barriers

While standards like the Web Content Accessibility Guidelines (WCAG) exist to help ensure content is accessible, there’s still a gap between ticking the compliance boxes and actual usability. Some common accessibility barriers impacting screen reader users include:
- Missing or Incorrect Alt Text: Without alt text, images lack context, making it hard for users to understand what’s on the page.
- Improper Heading Structure: Jumping from an H1 to an H3 heading (and skipping H2) can make navigating a page disorienting.
- Inadequate Link Descriptions: Using link text like “Click here” doesn’t tell users where the link will take them.
- Lack of Keyboard Navigation: If elements aren’t reachable by the keyboard, users may not be able to navigate away from certain sections.
By testing your site with a screen reader like NVDA, you can spot and fix these barriers directly, ensuring your content is genuinely usable—not just technically accessible. This step is vital for engaging a wide audience, including customers who rely on screen readers for equal access.

Plus, by prioritizing screen reader accessibility, you’re not just meeting legal requirements; you’re showing that your brand values inclusivity, which can resonate with customers and build loyalty.

Getting Started with NVDA

Ready to dive in? First, you’ll need to install NVDA on a Windows computer. Just head over to its official website and follow the straightforward instructions. Once it’s installed, take a few minutes to explore the settings. NVDA lets you adjust things like speed, voice pitch, and how much information it reads out loud. Tweaking these settings can make your screen reader testing smoother and help you catch all the essential details without getting distracted.

Understanding the Basics of NVDA

At first glance, NVDA might seem a bit overwhelming, but don’t worry—once you get the hang of a few essential controls, you’ll be navigating like a pro. The main control is the Insert key, which you use along with other keys to execute commands. For example, pressing Insert + Spacebar toggles between browse and focus modes, showing how users move between different sections and interact with elements on your site.

Key Shortcuts to Know
- Tab: Move through interactive elements like buttons and links.
- Shift + Tab: Go back through items, helping you check the flow of navigation.
- H: Navigate through headings in sequence (Shift + H moves backward), which is crucial for accessibility.
- K for links or G for graphics: Jump to specific content, helping you quickly assess if important items are accessible.
Testing for Accessibility Barriers with NVDA

Once you’re comfortable with NVDA, it’s time to put your website to the test. The goal is to see how easy (or difficult) it is for a screen reader user to find and understand information on your site.

Check Your Navigation Structure

Screen reader users rely heavily on clear navigation. Headings should be marked in a logical order, and the Tab key should move through items sensibly. As you use NVDA, please pay close attention to how it announces headings, links, and interactive elements. For instance, links labeled “Read More” can be confusing, while “Learn More About Our Services” is much more straightforward. Descriptive link text is vital to helping screen reader users navigate confidently.

Confirm Image Descriptions

Proper alt text is a must for images. Use the G key to move through images and listen to the descriptions NVDA reads aloud. The alt text doesn’t need to be lengthy—just informative enough to give users an idea of the image’s purpose.

For additional information about alt text, read our article “Understanding Image Alt Text Descriptions.”

Test Interactive Elements Like Forms

Forms can be tricky for screen reader users if they’re not labeled well. As you move through form fields, listen to the labels NVDA reads. Each field should have a clear label, and error messages should be accessible, too. Testing with NVDA can reveal unlabeled fields or hidden error messages that might make filling out forms difficult.

Common Accessibility Barriers to Watch For

Using NVDA can help you spot common barriers that affect accessibility:
- Keyboard Traps: These occur when users get stuck in one part of the page. Use the Tab and Shift + Tab keys to move around; if you find yourself stuck, it’s likely a keyboard trap.
- Focus Indicators: Screen reader users (and keyboard users in general) need a visible marker to show where they are on the page. Test this by tabbing through your site to see if each interactive element has a clear indicator.
- Content Flow: Listen to your site in linear order, from top to bottom. Does it make sense as you go? Unclear structure or skipped headings can confuse users trying to navigate the content in a meaningful order.
Documenting What You Find

As you test, it’s helpful to document any issues you come across. Be specific: note where each issue happens, what the problem is, and why it’s an accessibility issue. For example, if a button lacks a label, describe which button it is, where it’s located, and how this impacts screen reader users. Including step-by-step details on how you tested (like key sequences or what NVDA readout) can also help your team quickly recreate and fix the issue.

Trying Out Other Screen Readers

While NVDA is a fantastic tool, remember that users rely on different screen readers like JAWS or VoiceOver on Apple devices. Testing with more than one screen reader can uncover accessibility issues that one tool might miss. NVDA is particularly good with dynamic content and ARIA (Accessible Rich Internet Applications) attributes. So, if you can, try testing with multiple screen readers to get a fuller picture of your site’s accessibility.

Making Accessibility Part of Your Process

Accessibility testing with NVDA shouldn’t be a one-time thing—it works best when it’s part of your development process from the start. By catching issues early, you’ll avoid significant fixes later and create a better experience for everyone. During design, consider accessibility-friendly patterns like high-contrast colors and adjustable font sizes. During development, use NVDA to test as you go and do a final check once your site is live.

And if possible, getting feedback from users with disabilities can be incredibly valuable. While NVDA can help you simulate a screen reader experience, real users bring real-world insights that can highlight usability issues you might not think of.

Wrapping Up

Using NVDA to test your website’s accessibility is a powerful step toward creating a more inclusive online experience, but there’s so much more to accessibility than just technical adjustments—it’s about making your site welcoming to everyone, including customers who rely on assistive technology.

To help you navigate the broader world of ADA compliance and web accessibility, consider scheduling a briefing with 216digital. Our team can walk you through key accessibility requirements, share insights into your site’s current compliance level, and guide you on building a sustainable, accessible web presence. Let’s work together to make your website an inclusive, welcoming space for all users. Schedule your ADA briefing with 216digital today, and take the next step toward true digital accessibility.
Kayla Laganiere

November 5, 2024

How-to Guides

Accessibility, Accessibility testing, ADA Compliance, NVDA, web developers, Website Accessibility

What Is POUR?

Perceivable: Making Content Accessible to the Senses

What Does Perceivable Mean in Practice?

Common Mistakes That Violate Perceivable Standards

Operable: Ensuring Users Can Navigate and Interact

What Does Operable Mean in Practice?

Common Mistakes That Violate Operable Standards

Understandable: Keeping Content Clear and Predictable

What Does Understandable Mean in Practice?

Common Mistakes That Violate Understandable Standards

Robust: Ensuring Compatibility with Current and Future Technologies

What Does Robust Mean in Practice?

Common Mistakes That Violate Robust Standards

Bringing POUR Principles Together

Example: An E-Commerce Website

Putting POUR into Practice

POURing Effort into Accessibility

What is WCAG?

Why Should You Care About WCAG Conformance?

Breaking Down the WCAG Conformance Levels

Level A: Covering the Basics

Level AA: The Sweet Spot

Level AAA: The Extra Mile

How High Should You Aim?

What Makes Level AAA So Hard?

Keeping Your Website WCAG Compliant

Regularly Audit Your Site

Train Your Team

Make Accessibility Part of Your Process

Use Accessibility Tools

Stay Up-to-Date

Achieve WCAG Conformance with 216digital

Why Animation Can Be Problematic

Does Your Design Really Need Animation?

Making Animations Accessible

A Quick Fix with prefers-reduced-motion

What Does WCAG Say About Animation?

Testing Your Animations

Accessible Animation with JavaScript

Wrapping It Up

What Is a Focus Outline?

Why Focus Outlines Matter for Accessibility

Who Benefits from Focus Outlines?

Legal and Ethical Responsibilities

How to Create Accessible Focus Outlines

How to Style Focus States Using CSS

Example: Basic Focus Outline with CSS

Add Background Effects

Avoiding Common Mistakes with Focus Outlines

Testing Focus Visibility

Make Focus Outlines a Priority

Understand and Set Your Accessibility Goals

Audit Your Website for Accessibility Gaps

Ensure Keyboard Navigation is Intuitive

Implement Proper Use of Alt Text for Images

Ensure Sufficient Color Contrast

Use Semantic HTML Structure

Test with Assistive Technologies

Incorporate Accessible Forms

Conduct Remediation Based on Prioritized Issues

Implement Continuous Monitoring with Tools Like a11y.Radar

Conduct Routine Manual and Automated Testing

Keep Up-to-Date with WCAG Guidelines

Take the First Step Towards Accessibility

Understanding ADA Compliance and Accessibility Laws

ADA Guidelines for Web Accessibility

What Are the Legal Risks for Retailers?

Common Accessibility Issues in Lawsuits

The Cost of Non-Compliance

Legal Costs

Settlements

Fines

Damage to Brand Reputation

Loss of Customers and Sales

Big Brands, Bigger Penalties

Target Corporation Settlement

Beyoncé’s Parkwood Entertainment

Dick’s Sporting Goods

A Surge in Accessibility Lawsuits and the E-Commerce Sector

Why E-Commerce Faces Elevated Legal Risks

Installing `eslint-plugin-jsx-a11y`

Avoid Using `<div>` and `<span>` for Interactive Elements

Using `aria-label` for Accessibility

Dynamic Updates with `aria-live`