How-to Guides Archives- Page 9 of 10/Category

How to Build Accessible Slideshows and Carousels
Slideshows and carousels can add style and organization to a website, but they often pose accessibility challenges. If not designed with care, they can be difficult for people with disabilities—especially those who use screen readers or rely on keyboard navigation—to interact with. The good news is that by following a few key practices, you can make sure your slideshows and carousels are accessible for everyone, enhancing user experience and making your site more inclusive. Let’s break it down step by step.

Why Accessibility Matters for Slideshows and Carousels

Before we dive into the “how,” let’s talk about the “why.” Making sure your slideshows are accessible isn’t just the right thing to do; it’s essential. Accessibility is about making sure everyone can use your website, and it helps you comply with important standards like the Web Content Accessibility Guidelines (WCAG).

If you skip over accessibility, you could end up frustrating visitors, losing potential customers, or even dealing with legal trouble. Plus, accessible content doesn’t just help those with disabilities—it actually improves the experience for all users and makes your site more welcoming.

Key Considerations for Accessible Slideshows

So, how do you make your slideshows and carousels accessible? Here are a few key things to keep in mind:

Keyboard Navigation

Not everyone uses a mouse to navigate a website—some people rely entirely on their keyboard. This means your slideshow should be easy to move through using just the keyboard without users getting stuck or confused.

Best Practices:
- Tab Key Navigation (WCAG SC 2.1.1): Make sure users can use the Tab key to move forward through the slides and Shift + Tab to move backward.
- Arrow Key Control (WCAG SC 2.1.2): Allow users to switch slides with the left and right arrow keys so they can navigate without getting lost.
- Visible Focus(WCAG SC 2.4.7): Ensure that buttons and interactive elements like arrows have visible focus indicators so keyboard users can easily see what they’re interacting with.
Descriptive Labels and Alt Text

For people using screen readers, descriptive labels and alt text are super important. Without them, the screen reader can’t tell the user what a button or slide is for.

Best Practices:
- Alt Text for Images (WCAG SC 1.1.1): Every image in your slideshow should have alt text that describes what’s in the image. For example, if one slide shows a chart about “Website Accessibility,” the alt text should explain the key points of the chart.
- ARIA Labels: Use an aria-label attribute to give a text label to an object, such as a “Next” and “Previous” buttons. When a screen reader encounters an object, the aria-label text is read aloud to inform the user about what it is. So, instead of a generic label like “Button,” make it something like “Next slide: About Us” so users know exactly where they’re headed.
Pause/Play Buttons

Automatic slideshows that move on their own can be frustrating—especially for people with cognitive or motor disabilities. Always give users control over the slideshow with pause and play options.

Best Practices:
- Pause/Play Button (WCAG SC 2.2.2): Make sure there’s a clearly labeled button to pause or play the slideshow and that it’s easy to use with both the mouse and keyboard.
- Adjustable Timing (WCAG SC 2.2.1): For each slide transition, users should be able to turn off, adjust, or extend the time before the slide changes. This ensures that users have enough time to read and understand the content before the next slide appears.
Using ARIA Roles for Screen Reader Compatibility

ARIA roles help screen readers understand the structure and behavior of a slideshow. They provide extra information about how it’s organized and how users can interact with it.

Best Practices:
- Role Assignment: Use ARIA roles like role= "region" to define different parts of the slideshow so that screen readers can identify them quickly.
- Live Regions: Use aria-live= "polite" to let screen readers know when a new slide has appeared, keeping users in the loop without disrupting their experience.
- Hide Inactive Slides: Only show one slide at a time to screen readers. You can do this by adding aria-hidden= "true" to the slides that aren’t currently visible.
Poor Color Contrast

Even with the best intentions, it’s easy to fall into some design traps that can hurt accessibility. If the text on your slides blends into the background, users with low vision will have a hard time reading it.

Best Practices:
- High Contrast Text(WCAG SC 1.4.3): Make sure there’s plenty of contrast between the text and background. For example, white text on a dark background or black text on a light background works well. Aim for a contrast ratio of at least 4.5:1 for standard text and 3:1 for larger text, as recommended by WCAG. You can use color contrast checkers to make sure your text stands out against the background.
Testing for Accessibility

Once you’ve added accessibility features, testing is critical to making sure everything works as it should. There are a few easy ways to test your slideshows:

Ways to Test:
- Use a Screen Reader: Try out your slideshow with popular screen readers like NVDA (NonVisual Desktop Access) or JAWS (Job Access With Speech) to see if everything is being read in the correct order and labeled correctly.
- Keyboard Navigation: Go through your slideshow using only your keyboard to make sure you can interact with all the buttons and slides.
- Automated Tools: Use tools like WAVE or the Google Lighthouse browser feature to check for common accessibility issues like missing alt text or incorrect ARIA roles.
Final Thoughts

Making your slideshows and carousels accessible might take a little extra effort, but it’s totally worth it. Not only will it make your site more inclusive, but it’ll also create a smoother experience for all your users. From ensuring easy keyboard navigation to adding meaningful labels and controlling autoplay features, each step brings you closer to a more accessible website.

So, the next time you’re adding a slideshow to your site, remember—accessibility isn’t just a nice-to-have; it’s a must-have! With a bit of planning and regular testing, you can create slideshows that everyone can enjoy.

Are you ready to make sure your website is accessible? Then, schedule an ADA Strategy Briefing with the web accessibility experts at 216digital.
Greg McNeil

September 23, 2024

How-to Guides

Accessibility, ADA Compliance, Carousels, digital accessibility, Slideshowes, WCAG, Web Accessibility, web development
Web Accessibility: What to Ask Your Digital Agency
When choosing a digital agency to build or maintain your website, one of the most crucial factors to consider is accessibility. Digital Accessibility ensures that your website is usable by everyone, including people with disabilities. But how do you know if your agency partner understands web accessibility and can meet your needs? Asking the right questions can make all the difference.

Why It’s Important to Ensure Your Agency Understands Digital Accessibility

Web accessibility isn’t just about checking a box; it’s about making your website available to all users, regardless of their abilities. In the United States, over 70 million adults live with a disability. If your website isn’t designed with accessibility in mind, you could miss out on a large audience. Beyond that, failing to meet accessibility standards can expose your business to legal risks, including lawsuits under the Americans with Disabilities Act (ADA).

Moreover, accessible websites provide a better overall user experience, which can lead to increased engagement and customer satisfaction. If a website is easy to navigate for individuals with disabilities, it’s also likely more intuitive for everyone. That’s why it’s vital to ensure your digital agency understands and prioritizes web accessibility.

When Is the Best Time to Ask Your Agency About Accessibility?

The short answer? As early as possible.

Accessibility should be baked into the foundation of your website, not an afterthought. Whether you’re designing a new website or revamping an existing one, accessibility discussions should start in the planning phase.

If you’re already working with a digital agency, it’s never too late to ask about accessibility. It’s better to make improvements now than to wait until you’re facing a lawsuit or losing customers. By prioritizing accessibility from the start, you ensure your site meets legal requirements and offers a smooth, inclusive experience for all users.

Key Web Accessibility Questions to Ask Your Digital Agency

What Is the Current State of Web Accessibility on Our Website?

Before diving into solutions, it’s essential to assess where your website currently stands in terms of accessibility. Your digital agency should conduct an accessibility audit to identify any existing issues. Here are a few questions you can ask:
- Do you offer an initial accessibility audit?
- Can you provide examples of accessibility issues that have been flagged?
- What tools or methods do you use to test for accessibility?
A comprehensive audit should highlight potential barriers on your site, like empty headers, missing alt text for images, or lack of keyboard navigation. Starting with an audit gives you a clear picture of where improvements are needed.

What Is Your Approach to Web Accessibility?

Every digital agency has a process for implementing accessibility. You’ll want to understand how your agency handles it from start to finish. Ask them about their approach and experience:

How well do you know WCAG 2.1 guidelines?

The Web Content Accessibility Guidelines (WCAG) 2.1 are the industry standard for web accessibility. Your agency should be familiar with these guidelines and know how to apply them to your website.

Do you integrate accessibility into every stage of development?

Accessibility isn’t just a one-time fix. You should implement steps during the design, development, and content creation phases. Ask your agency if they have a process for embedding accessibility throughout the entire project.

Do you use both automated and manual testing methods?

Automated tools can catch many accessibility issues, but manual testing is essential for uncovering complex problems. Your agency should combine both methods for a thorough approach.

How Will You Ensure Accessibility Is Maintained?

Accessibility is an ongoing commitment. Websites change over time as content is updated and features are added. It’s important to ask how your agency plans to maintain accessibility once the site is live:

Do you offer ongoing accessibility monitoring?

Regular monitoring can help you stay compliant as web standards evolve and your website grows. Ask your agency if they provide services like continuous testing or accessibility check-ups.

Can you train our team to maintain accessibility?

If your website content is managed internally, your team should know how to keep it accessible. Some agencies offer training for content creators and developers to ensure new additions meet accessibility standards.

What is your process for updating the site to stay compliant with new regulations?

Digital accessibility laws are constantly evolving, and you need to ensure your website stays compliant. Your agency should have a plan for keeping your site up-to-date with the latest guidelines and legal requirements.

How Do You Prioritize Web Accessibility Issues?

Accessibility issues vary in severity. Some barriers, like missing alt text, are easier to fix, while others may require significant changes to your website’s structure. Ask your agency how they prioritize accessibility fixes:

How do you determine which issues need immediate attention?

Critical issues that block users from accessing content should be resolved first. Make sure your agency knows how to prioritize fixes to address the most pressing concerns first.

How long will it take to resolve accessibility issues?

Accessibility improvements should be made in a timely manner. Understanding the expected timeline helps you plan your next steps and set realistic expectations.

What’s Your Experience with Similar Projects?

Experience is vital when it comes to accessibility. You want to work with a digital agency that has a proven track record of making websites accessible:

Have you worked with other companies in our industry?

Different industries have unique accessibility challenges. For example, e-commerce sites may need to focus on accessible forms and shopping carts, while media companies may prioritize video captions and transcripts.

Can you show us examples of websites you’ve made accessible?

Case studies or portfolio examples can give you an idea of the agency’s capabilities. Look for examples that demonstrate a deep understanding of accessibility best practices.

Prioritize Accessibility from the Start

Web accessibility isn’t just a legal requirement – it’s a business imperative. By asking your digital agency the right questions, you can ensure your website is accessible to all users while avoiding the risk of legal issues.

Remember, accessibility should be an ongoing effort. Choose a digital agency that understands the importance of maintaining compliance and improving your website over time. By doing so, you’ll create an inclusive online experience that benefits both your users and your business.

Contact 216digital for Your Accessibility Needs

If you’re unsure where to start, 216digital can help. Our team specializes in ADA remediation and web accessibility, and we’re here to guide you every step of the way.

Schedule an ADA briefing with 216digital today to learn more about how we can help you maintain a compliant and accessible website. Let’s work together to make your site welcoming to everyone while keeping your business protected from legal risks.

Don’t wait—make accessibility a priority from the start!
Greg McNeil

September 19, 2024

How-to Guides, Legal Compliance

ADA Compliance, ADA Web Accessibility, digital accessibility, digital agency, Web Accessibility
How to Make Your Website’s Pop-Ups Accessible
Pop-ups are often used on websites to capture leads, promote special offers, or guide users through certain actions. However, while they can be powerful tools for engagement, they can also be a nightmare for users, especially those with disabilities. An inaccessible pop-up can frustrate users, prevent them from completing tasks, or even drive them away from your site.

To ensure your pop-ups enhance the user experience for everyone, including those using assistive technology, it’s essential to focus on accessibility. Let’s dive into the challenges of pop-ups and explore actionable steps and coding techniques to make them accessible.

Challenges of Website Pop-Ups for Accessibility

Hard to Close or Dismiss

One of the most common complaints about pop-ups is how difficult they can be to close. Whether it’s a tiny “X” button or a disappearing background overlay, some pop-ups seem almost impossible to dismiss without frustration. For users with mobility impairments, small targets like these can be especially problematic. Additionally, people who rely on keyboards or screen readers may not be able to easily navigate to the close button.

Improperly Labeled Pop-Ups

Screen reader users rely heavily on clear labels and descriptions to understand the content on a page. When a pop-up appears without proper labeling, it can be incredibly confusing. If there’s no clear announcement of what the pop-up is for or if the content isn’t properly described, these users may struggle to engage with the pop-up at all.

Focus Trap

A “focus trap” happens when a user is unable to move out of the pop-up window using their keyboard. This can cause frustration and make it difficult, if not impossible, to return to the main content. For users who rely on keyboard navigation, a focus trap can completely halt their browsing experience.

Disruption of Browsing Experience

A poorly timed or intrusive pop-up can disrupt the browsing experience for all users, but it’s especially challenging for people with disabilities. Imagine navigating a website with a screen reader, and a pop-up interrupts your flow. If the pop-up isn’t well integrated or easy to dismiss, it can leave users feeling lost or overwhelmed.

Now that we’ve identified the challenges, let’s explore how to address these issues and ensure your pop-ups are accessible to everyone.

Best Practices for Accessible Pop-Ups

Make Sure Pop-Ups Are Easy to Close

One of the easiest ways to make your pop-ups more user-friendly is to ensure they’re easy to close. Provide a large, clearly visible close button, and place it in a predictable spot, like the top-right corner of the pop-up. Avoid small, hard-to-click targets, especially for users with mobility issues.

Code Tip: Include a Keyboard Shortcut

Make sure the pop-up can be dismissed using the Esc key. Adding this functionality allows keyboard users to close the pop-up quickly, without needing to navigate to a specific button.
```
document.addEventListener('keydown', function(event) {
  if (event.key === "Escape") {
    closePopup();
  }
});
```
In this example, the Esc key is programmed to trigger the closePopup() function, providing an easy way to dismiss the pop-up.

Properly Label the Pop-Up for Screen Readers

When a pop-up appears, it should be immediately announced to users who rely on screen readers. This helps provide context so they can understand what’s happening on the page. You can do this by using ARIA (Accessible Rich Internet Applications) attributes.

Code Tip: Use ARIA Attributes for Accessibility
```
<div role="dialog" aria-labelledby="popupTitle" aria-describedby="popupDescription">
 <h2 id="popupTitle">Special Offer</h2>
  <p id="popupDescription">Get 20% off your next purchase when you sign up for our newsletter.</p>
</div>
```
In this code, the role="dialog” attribute lets screen readers know that a pop-up window (dialog box) has appeared. The aria-labelledby and aria-describedby attributes provide titles and descriptions that help users understand what the pop-up is about.

Prevent Focus Trapping

A common accessibility mistake with pop-ups is trapping focus within the pop-up window, which prevents keyboard users from returning to the main content. To avoid this, ensure that users can freely navigate between the pop-up and the rest of the page.

Code Tip: Manage Focus Correctly

When the pop-up opens, move the user’s focus to the first interactive element (like a form field or close button). When the pop-up closes, return focus to the element that triggered it, allowing users to continue where they left off.
```
const popup = document.getElementById("popup");
const triggerButton = document.getElementById("triggerPopup");
triggerButton.addEventListener('click', function() {
  popup.style.display = "block";
  popup.querySelector('input').focus(); // Move focus to the first element in the popup
});
function closePopup() {
  popup.style.display = "none";
  triggerButton.focus(); // Return focus to the triggering element
}
```
Avoid Disrupting the Browsing Experience

Pop-ups should never interrupt the user’s browsing experience unexpectedly. It’s important to trigger pop-ups at the right time and make them easy to interact with.
- Don’t use pop-ups on page load – This can be jarring for users, especially those using screen readers. Instead, trigger pop-ups based on user action, like clicking a button or scrolling to a specific section of the page.
- Use overlays carefully – Ensure that any background overlay that appears when a pop-up opens doesn’t obscure important content or make it difficult for users to navigate.
- Provide Accessible Text for Pop-Up Links and Buttons
You should clearly label and make the buttons and links in your pop-up easy to understand.Avoid generic text like “Click Here” or “Submit.” Instead, use descriptive text that explains the action.

Example:
- Good: “Sign Up for Our Newsletter”
- Bad: “Submit”
This helps all users, including those using screen readers, understand exactly what will happen when they click on a button.

Keep the Design Simple and Clear

Simplicity is key when it comes to accessible pop-ups. Avoid cluttering the pop-up with too much information or distracting animations. Use high-contrast colors and large, readable fonts to make the content easy to digest.

Test with Real Users and Assistive Technologies

The best way to ensure your pop-ups are truly accessible is to test them with real users, especially those who rely on assistive technologies. Tools like screen readers, voice commands, and keyboard-only navigation can help you understand how users will interact with your pop-up.

Tools for Testing Pop-Up Accessibility:
- Screen readers: Test your pop-up with screen readers like NVDA (NonVisual Desktop Access) or JAWS (Job Access With Speech).
- Keyboard navigation: Make sure all interactive elements in the pop-up can be accessed using only a keyboard.
- Accessibility checkers: Use automated tools like WAVE or Axe to scan your site for accessibility issues.
Make a Pop with 216digital

Making sure your website’s pop-ups are accessible isn’t just about ticking boxes—it’s about making sure everyone has a great experience on your site. Simple steps like ensuring your pop-ups are easy to close, clearly labeled, and don’t trap users can make a big difference in how people interact with your content.

Whether you’re a website owner, developer, or content creator, making your pop-ups accessible means more people can engage with what you have to offer. It also shows that you care about creating a web experience that everyone can enjoy.

To take your pop-ups from good to great, consider scheduling an ADA briefing with 216digital. We’ll help you make thoughtful adjustments and test your pop-ups with assistive technologies to ensure they enhance, rather than hinder, the user experience. Let’s work together to make sure your pop-ups are welcoming and accessible to all your visitors!
Greg McNeil

September 13, 2024

How-to Guides

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

What is Web Accessibility?

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

Why Accessible Coding is Important

Accessible coding is crucial for a variety of reasons:
- Wider Audience Reach: By making your site accessible, you expand your audience and enhance user experience for everyone.
- SEO Benefits: Accessibility often overlaps with good SEO practices, boosting your website’s visibility.
- Legal Requirements: Laws like the ADA in the U.S. require websites to be accessible, protecting you from potential legal issues.
Now let’s dive into seven core principles of accessible coding and see how you can implement them in your website’s code.

1.Provide Alt Text for Non-Text Components

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

Why Alt Text is Important:
- Screen Reader Accessibility: People with visual impairments use screen readers that read aloud the alt text. If an image lacks alt text, the user will miss out on important information.
- SEO Benefits: Alt text improves SEO by giving search engines more information about the content of your images. Search engines can’t “see” images, but they can index alt text, helping your site rank better in image search results.
Best Practices for Writing Alt Text:
- Be Descriptive and Specific: Describe the content and purpose of the image. For example, instead of just saying “image of a tree,” say, “A large oak tree in a park during autumn.”
- Keep it Concise: Alt text should typically be no longer than 125 characters. This keeps the description brief while still conveying necessary information.
- Use Empty Alt Attributes for Decorative Images: For images that serve a purely decorative purpose (i.e., they don’t convey information or serve a functional purpose), use an empty alt attribute (alt=””). This prevents screen readers from wasting time on irrelevant content.
Example:
```
<img src="award-ceremony.jpg" alt="CEO receiving the 'Best Company Award' at the 2024 Business Awards" />
```
In this example, the alt text describes the image in a way that conveys its significance. This provides context for users who cannot see the image and helps them understand its role on the page.

For purely decorative images that don’t add meaning, you would use an empty alt attribute:
```
<img src="border-decoration.png" alt="" />
```
For more information about Alt text for images, check out our article Understanding Image Alt Text Descriptions.

2. No Keyboard Traps

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

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

How to Prevent Keyboard Traps:
- Ensure All Interactive Elements Are Focusable: Elements like buttons, form fields, and links must be easily accessible via the keyboard’s “Tab” key.
- Provide a Clear Way to Escape Modals: If using pop-ups or modal windows, ensure that users can exit using keyboard controls, typically the “Escape” key.
Example:
```
<a href="submit.html" id="submit-btn" tabindex="0">Submit</a>
```
This code ensures that the “Submit” button can be accessed via keyboard. The tabindex="0" attribute allows it to be included in the natural tab order of the page.

3. Allow Users to Resize Text

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

How to Implement Text Resizing:
- Use Relative Font Sizes: Avoid using fixed units like px for font size. Instead, use relative units such as em or percentages (%). This ensures that text can scale properly.
- Test Text Scaling: After implementing relative font sizes, test your site by increasing text size to 200% in different browsers to ensure the content remains legible and the layout doesn’t break.
Example:
```
body {
font-size: 100%; /* Base font size that scales */
}
h1 {
    font-size: 2em; /* 200% of the body text size */
}
```
In this example, the body text is set at a flexible 100%, and the headings use a relative size (2em) that will scale based on the user’s settings.

4. Avoid Seizure Triggers

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

How to Prevent Seizure Triggers:
- Avoid Fast Animations: If you need animations, make sure they don’t flash rapidly or use extreme changes in brightness.
- Limit Flashing to Below 3 Hz: Ensure that any flashing or blinking elements do not exceed three flashes per second.
Example:
```
/* Safe animation with no rapid flashing */
@keyframes safe-flash {
    0%, 100% { opacity: 1; }
    50% { opacity: 0.5; }
}
.flash-warning {
    animation: safe-flash 2s infinite;
}
```
This animation fades in and out at a safe pace, avoiding any rapid flashing that could trigger seizures.

5. Follow a Logical Reading and Code Order

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

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

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

Here, the content is organized in a logical structure, making it easier for screen readers to understand and navigate.
```
  <header>
    <h1>Welcome to Our Store</h1>
    <nav>
        <ul>
            <li><a href="#home">Home</a></li>
            <li><a href="#shop">Shop</a></li>
            <li><a href="#contact">Contact Us</a></li>
        </ul>
    </nav>
</header>
<main>
    <section id="shop">
        <h2>Shop Our Latest Collection</h2>
        <p>Browse our new products for this season.</p>
    </section>
</main>
<footer>
    <p>&copy; 2024 Our Store</p>
</footer>
```
6. Use Headings Appropriately

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

Best Practices for Headings:

WCAG SC 1.3.1 Info and Relationships requires that content structure and relationships be programmatically determined or available in text. Proper use of headings and a clear content structure ensure that users can navigate and understand the content more easily.
- Use Headings to Structure Content: Use <h1> for the main title of the page, <h2> for section titles, and so on. Don’t skip heading levels (i.e., don’t jump from <h1> to <h3>).
- Avoid Using Headings Solely for Styling: Headings should not be used just to make text look bigger or bolder. Use them to represent the content hierarchy.
Example:
```
<h1>Guide to Accessible Coding</h1>
<h2>Why Accessibility Matters</h2>
<h3>Legal Requirements</h3>
<h3>Improved User Experience</h3>
```
In this example, the headings follow a logical order, making the content easy to navigate for users with screen readers.

7. Use HTML Tags That Make Websites Accessible

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

Key Accessible HTML Elements:
- <label>: Associates a form field with a text description, making it easier for screen readers to understand.
- <button>: Creates a clickable button that is accessible via keyboard and screen readers.
- ARIA Attributes: These attributes, such as aria-label and aria-required, provide additional context for assistive technologies.
Example:
```
<form>
    <label for="email">Email Address:</label>
    <input type="email" id="email" name="email" aria-required="true">
</form>
```
In this example, the <label> tag clearly associates the input field with its description, while the aria-required="true" attribute informs screen readers that the field is mandatory.

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

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

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

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

September 10, 2024

How-to Guides

digital accessibility, How-to, WCAG, WCAG Compliance, Web Accessibility, web development
How to Implement ARIA Landmarks and Roles for Better Accessibility
For users of assistive technologies, accessing and interacting with websites can be difficult if the proper structure and cues aren’t in place. This is where ARIA (Accessible Rich Internet Applications) landmarks and roles come in handy. Implementing ARIA landmarks and roles can significantly improve your website’s accessibility, helping users navigate more easily and interact with web elements effectively. If you’re new to ARIA, don’t worry! This guide will walk you through ARIA landmarks and roles, why they matter, and how to implement them step-by-step.

What Is ARIA and Why Is It Important?

ARIA is a set of HTML attributes intended to make webpages easier to navigate for people who rely on assistive technology, such as screen reading software. These attributes help bridge gaps in standard HTML that might not convey sufficient meaning to people with disabilities.

By using ARIA, developers can label, describe, and define the functionality of elements in ways that ensure everyone has a better user experience. Regarding web accessibility, ARIA attributes are recommended in some cases by the Web Content Accessibility Guidelines (WCAG), which provide standards to help websites comply with accessibility requirements.

ARIA landmarks and roles are two essential aspects of making sure your website content is accessible for all users to understand and interact with.

ARIA Landmarks: What Are They?

ARIA landmarks are unique markers you can add to different sections of your webpage to make navigation easier for users with disabilities. These landmarks help people who use screen readers understand the structure of a webpage and quickly jump to different sections. Think of them as signposts, making it clear where key sections—like the header, main content, navigation, and footer—are located.

The major ARIA landmarks include:
- <header>: Identifies the top section of the webpage.
- <main>: Indicates the main content of the page.
- <nav>: Points to the area that contains navigational links.
- <footer>: The bottom section of the webpage.
Why Are ARIA Landmarks Important?

ARIA landmarks are invaluable for users with visual or motor impairments who use the keyboard or screen reader to navigate the web. They allow users to skip repetitive elements (like navigation bars) and jump directly to the content they’re looking for. Without these landmarks, a user would have to listen to every single line of the page to figure out where the main content starts or how to get to the footer. Using ARIA landmarks ensures that your website is easy to navigate for everyone.

How to Implement ARIA Landmarks Step-by-Step

Now that you understand the importance of ARIA landmarks let’s look at how to implement them in your website’s code. The good news? Adding ARIA landmarks is simple and can be done using standard HTML elements.

Adding the Header Landmark

The <header> element is used to define the global top section of your page, which typically contains things like the website logo, title, or main navigation links. Here’s an example of the correct usage of the HTML5 <header> region:

<header>
```
<h1>My Cool Website</h1>
<h1>My Cool Website</h1>
  <nav>
    <ul>
      <li><a href="/">Home</a></li>
      <li><a href="/about">About</a></li>
      <li><a href="/products">Products</a></li>
    </ul>
  </nav>
</header>
```
The Main Landmark

The <main> element is crucial because it defines the primary content of the page. The <main> element, along with a skip link, can allow users of assistive technology to skip past repetitive content such as the navigation:
```
<main role="main">
  <h2>Main Content</h2>
  <p>This is the most important part of the page.</p>
</main>
```
By using role=”main”, you’re ensuring that screen readers can quickly identify and jump to the core content of your page. Only one main landmark should be used per page.

Using the Navigation Landmark

The navigation area of your website should be easy to identify and skip if necessary. You can use the <nav> element or the ARIA role, but you do not need to use both:
```
<nav>
  <ul>
    <li><a href="#section1">Section 1</a></li>
    <li><a href="#section2">Section 2</a></li>
  </ul>
</nav>
<div role="navigation">
  <ul>
    <li><a href="/products">Products</a></li>
    <li><a href="/about">About Us</a></li>
  </ul>
</div>
```
With the navigation region, you’re clearly marking the section of the page that contains links for navigating to other parts of the site.

Adding the Footer Landmark

Finally, the <footer> element typically contains secondary content, such as copyright information or additional links. Adding a landmark here helps screen reader users know when they’ve reached the end of the page:
```
<footer role="contentinfo">
  <p>&copy; 2024 Your Company</p>
</footer>
```
In this case, role= "contentinfo" tells screen readers that this section provides supplementary information about the website.

ARIA Roles: What Are They?

ARIA roles go beyond marking sections of the page—they describe the functionality of specific elements. By using ARIA roles, you’re defining how an element should behave or be interacted with, especially when using assistive technologies.

Some commonly used ARIA roles include:
- “button”: Makes non-biased elements like <div> behave like a button.
- “dialog”: Defines a pop-up dialog window.
- “alert”: Marks an element as an important alert that needs immediate attention.
Why Are ARIA Roles Important?

ARIA roles give more meaning to non-standard HTML elements. For example, if you create a custom button using a <div> instead of the traditional <button> element, a screen reader might not recognize it as a button. By assigning it an ARIA role, you ensure it’s interpreted correctly, making the interaction more intuitive and accessible.

How to Implement ARIA Roles Step-by-Step

Let’s check out some examples of proper ARIA implementation.

Creating a Custom Button

If you have a custom button element (like a <div> styled as a button), you can add the role="button" to make sure it’s recognized as an interactive button by screen readers:
```
<div role="button" tabindex="0" onclick="submitForm()">Submit</div>
```
The ARIA role “button” tells assistive technology to announce this element as a button, and the “tabindex” attribute makes the element focusable via the keyboard. However, it’s always best to use the correct semantic HTML5 <button> tag whenever possible.

Adding a Dialog Role

For models or pop-up windows, you can use the role= "dialog" to make them accessible:
```
<div role="dialog" aria-labelledby="dialogTitle" aria-describedby="dialogDescription">
  <h2 id="dialogTitle">Confirmation</h2>
  <p id="dialogDescription">Are you sure you want to delete this file?</p>
  <button onclick="closeDialog()">Cancel</button>
</div>
```
The aria-labelledby and aria-describedby attributes help give context to the dialog box for users relying on assistive technologies.

Creating an Alert

If you need to display important, time-sensitive information—like an error message or form feedback—you can use the role= "alert":
```
<div role="alert">
  <p>Error: The "password" field is required.</p>
</div>
```
This role makes sure that screen readers announce the alert immediately, ensuring the user doesn’t miss critical information.

Going Beyond ARIA: Continue Your Accessibility Journey

The HTML markup of your website is far more critical than just defining the visual style of the site. It is used by screen reading software, assistive technologies, and keyboard navigation to ensure users have easy access to content. SEO crawlers also use it to determine the accuracy and relevance of your content.

By adding landmarks like header, main, navigation, and footer, and using roles like button, dialog, and alert, you’ll not only meet the accessibility standards outlined by WCAG, but you’ll also create a more user-friendly website for everyone.However, this is just one piece of the web accessibility puzzle.

Team Up with 216digital

At 216digital, we understand that keeping up with ADA compliance and accessibility best practices can be challenging. That’s why we’re here to help. We specialize in helping businesses achieve and maintain ADA compliance with expert guidance and actionable strategies. Schedule an ADA briefing with our experts today to learn more about how we can guide you through the complexities of accessibility, ensuring your website meets legal standards and delivers a great experience for all users.

Let’s make the web more accessible, together—book your ADA briefing today!
Bobby

September 6, 2024

How-to Guides

Accessibility, ADA Compliance, ARIA, How-to, WCAG, Web Accessibility, web development
How to Make Your Blog Accessible to All Readers

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

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

How Accessible Content Helps SEO

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

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

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

Use Headings to Convey Meaning and Structure

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

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

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

Keep Content Clear and Concise

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

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

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

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

Describe Your Images

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

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

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

Make Link Text Meaningful

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

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

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

Check the Comment Form—Is It Labeled Properly?

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

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

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

Use Flexible Font Sizes

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

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

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

Put Your Blogroll on the Right-Hand Side

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

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

Conclusion

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

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

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

Greg McNeil

September 5, 2024

How-to Guides

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

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

What is a Website Navigation Menu & Structure?

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

The structure of a navigation menu can vary from simple to complex, depending on the size and type of website. Most websites use one or more of these types of menus:
- Horizontal Menus: Commonly found at the top of a webpage.
- Vertical Menus: Often located on the left or right side of a webpage.
- Dropdown Menus: This appears when you hover over or click a menu item.
- Hamburger Menus: Those three stacked lines you see on mobile websites or apps.
The structure needs to be clear and intuitive so users can find what they’re looking for quickly and easily. For example, if you’re on an online store’s website, you’d expect to find “Products” in the main menu, not buried under “About Us.”

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

Common Accessibility Challenges with Navigation Menus

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

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

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

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

Features of an Accessible Navigation Menu

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

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

Keyboard accessibility is one of the most critical aspects of web accessibility. Some users may not be able to use a mouse due to motor disabilities, repetitive strain injuries, or personal preference. For these users, navigating a website entirely via the keyboard is essential. Here’s how you can make your navigation menu keyboard-friendly:
- Tab Order: Ensure that users can navigate through all menu items using the Tab key. The order should be logical and follow the visual flow of the website.
- Enter and Arrow Keys: When a menu item has a dropdown, users should be able to expand or collapse it using the Enter or Arrow keys. Once expanded, users should be able to navigate through the submenu items using the Arrow keys.
- Focus Management: Users should always know where they are on the page. Make sure that when a user opens a dropdown, the focus shifts to the first item in that dropdown.
Here’s an example of how you can make a simple navigation menu keyboard accessible:
```
<nav>
  <ul>
    <li><a href="#home" tabindex="0">Home</a></li>
    <li><a href="#about" tabindex="0">About</a></li>
    <li><a href="#services" tabindex="0">Services</a></li>
    <li><a href="#contact" tabindex="0">Contact</a></li>
  </ul>
</nav>
```
2. Visible Focus Indicator (WCAG 2.4.7 – Focus Visible):

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

Styling Focus Indicators

Customize the default focus style to make it more visible. You can use CSS to create a more prominent outline or make a background change. For example:
```
a:focus {
  outline: 3px solid #ff9800; /* Orange border for focused links */
  background-color: #f0f0f0; /* Light gray background for contrast */
}
```
Accessible Color Choices

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

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

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

ARIA Roles

Use roles like role= “navigation” to indicate the navigation region and role= “menu” or role= “menuitem” to define menus and items within them. For example:
```
<nav role="navigation" aria-label="Main Navigation">
  <ul role="menubar">
    <li role="none"><a href="#home" role="menuitem">Home</a></li>
    <li role="none"><a href="#about" role="menuitem">About</a></li>
    
  </ul>
</nav>
```
ARIA Attributes for State

Use aria-expanded to indicate if a dropdown is expanded or collapsed. This helps users who rely on screen readers understand whether they can interact further with the menu item.
```
<button aria-expanded="false" aria-controls="submenu">Services</button>
<ul id="submenu" role="menu">
  <li role="none"><a href="#design" role="menuitem">Design</a></li>
  <li role="none"><a href="#development" role="menuitem">Development</a></li>
</ul>
```
When the button is clicked to expand the menu, JavaScript should change aria-expanded= “true”.

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

Ensuring sufficient color contrast is vital for users with visual impairments, including color blindness. The contrast ratio between the text and its background should be at least 4.5:1 for normal text and 3:1 for large text.
- Choosing Accessible Colors: Use online tools like the WebAIM Contrast Checker to ensure your menu items meet the WCAG color contrast standards.
- Avoid Low-Contrast Hover States: While hover effects can be helpful, make sure they don’t reduce the text’s visibility. For example, avoid light text on light backgrounds.
5. Responsive and Mobile-Friendly Design (WCAG 1.4.10 – Reflow):

Navigation menus must be accessible across different devices and screen sizes. This is especially important given the widespread use of mobile devices.
- Responsive Design Techniques: Ensure that the menu collapses into a mobile-friendly version, like a hamburger menu, without losing accessibility features.
- Mobile Screen Readers: Make sure mobile screen readers can read and navigate the menu. Test with VoiceOver on iOS and TalkBack on Android to ensure compatibility.
6. Skip Navigation Links (WCAG 2.4.1 – Bypass Blocks):

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

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

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

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

Menu items should be labeled clearly to describe what users can expect when they click on them. This reduces confusion and ensures all users, including those with cognitive disabilities, can easily navigate the site.
- Avoid Vague Labels: Instead of “Explore,” use something like “Our Services” to make it clearer what users will find.
Tips for Creating an Effective Accessibility Navigation Menu

Creating an accessible navigation menu isn’t just about meeting the guidelines—it’s about creating a better experience for everyone. Here are some tips to help:
1. Keep it Simple: A clear and straightforward menu structure is easier for all users to navigate.
2. Use Clear Labels: Avoid jargon and use common terms. For example, instead of “Explore Our Solutions,” just use “Services.”
3. Include Skip Links: A “Skip to content” link allows keyboard users to skip repetitive navigation links.
4. Test with Real Users: Get feedback from people with different disabilities to understand how accessible your menu really is.
5. Provide Descriptive Anchor Text: Use anchor text that tells users where they’re going. For example, use “About Us” instead of “Click Here.”
Testing for an Accessible Menu

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

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

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

August 30, 2024

How-to Guides

digital accessibility, How-to, navigation menu, Web Accessibility, web development
Top 9 Web Accessibility Issues and Fixes
Imagine trying to explore a website but not being able to get the information you need because the site wasn’t made with you in mind. For many people with disabilities, this is a frustrating reality.

Web accessibility isn’t just a technical requirement—it’s about making sure everyone can use your website. Whether you’re a developer, IT director, or content manager, making your website accessible is essential. By fixing common accessibility problems, you not only meet legal standards but also make your site better for everyone.

Let’s dive into the top 10 web accessibility issues and how to fix them.

1. Missing Alt Text for Images

Alt text, or alternative text, is a brief description added to images on a website. It helps people who can’t see the images understand what they are about, as the alt text is read aloud by screen readers or displayed if the image doesn’t load. When alt text is missing, people with visual impairments miss out on important information, making the website less accessible. This can lead to frustration for users and might even cause legal issues, as websites are expected to be accessible to everyone.

According to WCAG 2.1 SC 1.1.1 (Non-text Content), all non-text content, like images, needs a text alternative that serves the same purpose or provides the same information.

How to Fix:
- Add Descriptive Alt Text: For each image, write meaningful alt text that clearly describes what it’s showing or its purpose. For example, instead of just saying “Image of a dog,” say “Golden Retriever playing in a park.”
- Use Empty Alt Attributes for Decorative Images: If an image is just decorative, use an empty alt attribute (alt=””). This way, screen readers skip over these images, making navigation easier for users.
- Review and Update Regularly: Regularly check your alt text to make sure it’s still relevant, especially if you update the images or content on your site.
For more information about Alt text for images, check out our article Understanding Image Alt Text Descriptions.

2. Web Accessible Forms

Forms that are not web accessible can be a big problem for people with disabilities. When forms are not designed with web accessibility in mind, they may be hard to understand or use with assistive technologies like screen readers. For example, if a form doesn’t have clear labels or instructions, someone using a screen reader might not know what information to put in the fields. This can make it difficult or even impossible for them to complete the form.

WCAG 2.1 SC 1.3.1 (Info and Relationships)requires that the information and relationships between form elements be clear and properly coded so that assistive technologies can read and interpret them correctly.

How to Fix:
- Label Form Elements Clearly: Use the <label> tag to connect labels with each form field. This helps screen readers explain each field’s purpose. For example, use <label for=”email”>Email Address</label> with <input type=”email” id=”email”>.
- Provide Accessible Error Messages: Make sure error messages are clear and easy to understand. Use ARIA attributes like aria-live to alert users to errors and make sure screen readers can easily read the messages.
- Include Clear Instructions: Give clear instructions for filling out the form, especially for fields with specific requirements like date format or password criteria.
3. Poor Color Contrast

Low color contrast between text and background can make content hard to read, especially for users with visual impairments or color blindness. For example, light gray text on a white background is hard for many users to see.

WCAG SC 1.4.3 (Contrast – Minimum) requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text to meet web accessibility standards.

How to Fix Color Contrast:
- Check Contrast Ratios: Use online tools like WebAIM’s Contrast Checker to make sure the color contrast between text and background meets accessibility guidelines. Aim for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
4. Missing Keyboard Navigation

Web keyboard navigation is a way for people to use a website just by pressing keys on their keyboard, instead of using a mouse. This is important for people who can’t use a mouse, like those with certain disabilities.

When a website doesn’t support keyboard navigation, it means that users who rely on keyboards might not be able to access all parts of the site. This is a problem because it makes the website more challenging to use for people with disabilities.

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

How to Fix:
- Enable Keyboard Navigation: Ensure that all interactive elements, such as links, buttons, and menus, can be accessed using only a keyboard. This includes allowing users to tab through items and activate them using the Enter or Space keys.
- Implement Proper Tab Order: Use the tabindex attribute to manage the order in which elements receive focus when tabbing. Avoid skipping focusable elements or creating confusing navigation paths.
- Use Focus Management: When interactive elements like modal dialogs or dropdown menus open, move the focus to the first interactive element within the component, and return it to the triggering element when the component closes.
5. Video and Audio Captions

Videos and audio content that lack captions or transcripts are inaccessible to users who are deaf or hard of hearing. Without captions or transcripts, these users miss out on the audio information provided in multimedia content.

WCAG SC 1.2.2 Captions (Pre-recorded) mandates that videos and audio content include captions to assist users who are deaf or hard of hearing. Without captions, these users may miss crucial information, making it more challenging for them to grasp or engage with the content fully.

How to Fix:
- Provide Captions: Make sure your videos include captions that match what people say. Start with tools like YouTube’s automatic captions, but edit them manually to ensure accuracy.
- Create Transcripts: Give users transcripts for your audio content. A transcript is a written version of what’s said in a video or audio file, including important sounds. Users can read these transcripts or use them with text-to-speech tools.
- Make Captions and Transcripts Available: Allow users to turn captions on or off and offer transcripts for download. This gives people the choice to use captions or read the text in a way that works best for them.
6. Missing Skip Links

Web accessible skip links are special links on a website that let people quickly jump past repetitive content, like navigation menus, to get to the main part of the page. This is especially helpful for people using screen readers or keyboard navigation.

If a website is missing these skip links, it can make it much harder for users to navigate, which goes against WCAG SC 2.4.1 Bypass Blocks.” This helps users quickly get to the content they need, reducing the effort required to access important content.

How to Fix Skip Links:
- Add Skip Navigation Links: Place “skip to content” links at the top of your web pages. These links should be one of the first elements in the tab order, allowing users to bypass repetitive navigation and go directly to the main content.
- Make Skip Links Visible: Ensure that skip navigation links are visible when focused. Use CSS to make them visually prominent when selected by a keyboard, so users know where they are skipping to.
7. Unclear Headings and Structure

Poorly structured headings can make it difficult for users with screen readers to understand the organization of the content. For example, if headings are not used correctly or if they are missing, users may struggle to comprehend the hierarchy and flow of the information.

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

How to Fix:
- Use Proper Heading Tags: Implement <h1>, <h2>, <h3>, etc., in a logical order to reflect the content’s structure. The <h1> tag should represent the main title, with subsequent headings breaking down the content into logical sections.
- Ensure Headings Are Descriptive: Headings should clearly describe the content that follows, helping users understand what each section covers. For example, instead of a generic heading like “Details,” use “Product Specifications.”
- Maintain a Consistent Structure: Consistently apply heading tags across your website to create a predictable and accessible content structure, making it easier for users to navigate.
8. Inconsistent Link Text

Links with vague or repetitive text like “click here” or “read more” can be confusing for screen reader users as they lack context about the link’s destination or purpose. For example, if several links are labeled “read more,” users may not know which topic they are referring to.

WCAG SC 2.4.4 Link Purpose (In Context) requires that the purpose of each link be clear from the link text alone or from the surrounding context. This helps users understand where a link will take them and ensures that all users can navigate effectively.

How to Fix:
- Use Descriptive Link Text: Ensure that the link text clearly indicates what the link will do or where it will take the user. For instance, instead of saying “click here,” use “Download our accessibility guide.”
- Avoid Repetition: Ensure that each link’s text is unique, especially if links are close to each other. This helps users distinguish between different links and understand their destinations.
- Provide Context in Surrounding Text: If necessary, add context around the link text to clarify its purpose. However, the link text itself should still be sufficiently descriptive on its own.
9. No Focus Indicators

Web accessible focus indicators are visual cues that show which part of a website a user is currently interacting with, like when using a keyboard or a screen reader.

According to WCAG SC 2.4.7 Focus Visible, “Focus Visible,” these indicators are crucial for making websites easy to navigate. Without them, users might struggle to see where they are on the page, which can make the site hard to use, especially for people with disabilities. Proper focus indicators help everyone use a website more effectively and inclusively.

How to Fix Focus Indicators:
- Ensure Visible Focus: Use CSS to create clear, visible focus indicators for all interactive elements. For example, you can use outline: 2px solid #000; to ad a solid black outline when an element is focused.
- Customize Focus Styles: Enhance default focus styles to make them more visible, especially if the default outline blends into the background. Consider using a contrasting color or a thicker border.
How to Test for Web Accessibility Issues

Testing for web accessibility can be done using a combination of manual checks and automated tools. Let’s take a look at a quick guide:
1. Manual Testing: Use a keyboard to navigate your site and check all interactive elements. Utilize screen readers to ensure that content is read out correctly and that forms, buttons, and links are accessible.
2. Automated Tools: Use tools like WAVE, Axe, or Lighthouse to perform automated accessibility audits. These tools can quickly identify many common issues, but manual testing is still essential for thorough accessibility checks.
3. User Testing: If possible, involve users with disabilities in your testing process. They can provide valuable feedback on real-world accessibility issues that automated tools might miss.
Building a Path to Web Accessibility

Making sure your website is accessible goes beyond just checking off boxes—it’s about creating a welcoming space where everyone can connect with your content. By tackling common accessibility issues, you not only improve how people experience your site but also protect your organization from potential legal problems and open up new audience opportunities.

If you want to learn more about improving your website’s accessibility initiative, schedule a complimentary ADA strategy briefing with the experts at 216digital. We make web accessibility simple and achievable, helping you develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms.

Don’t let your website fall behind on accessibility. Let’s work together to make sure everyone can fully experience your site.
Greg McNeil

August 22, 2024

How-to Guides

Accessibility, ADA Compliance, digital accessibility, Web Accessibility, web development, Website Accessibility
Creating Accessible Web Forms
In today’s digital world, ensuring your content forms are accessible is more important than ever. Whether you’re a website owner, a developer, or a content creator, ensuring that everyone can use your forms is key to providing a great user experience. This article will dive into why accessible content forms matter, how to ensure your forms meet accessibility standards and tips for creating inclusive digital spaces. Let’s explore how you can make your forms better for everyone!

Why Should Content Forms Be Accessible?

Accessible content forms are crucial for several reasons:
1. Inclusivity: Everyone should have equal access to information and the ability to participate in discussions. By making your forms accessible, you’re ensuring that users with disabilities can join in the conversation just as easily as anyone else.
2. Legal Compliance: In the United States, there are legal requirements for digital accessibility under laws like the Americans with Disabilities Act (ADA). Making your forms accessible helps you stay compliant and avoid potential legal issues.
3. Broader Audience: Accessible forms reach a wider audience. More people can engage with your content when your forms are easy to navigate and use, leading to increased traffic and a better community experience.
The Importance of Accessible Forms

Accessible forms are not just about following the law—they’re about creating a better, more inclusive online environment. Here’s why it matters:
1. Improves User Experience: Accessible forms provide a smoother experience for all users. Features like clear navigation, readable text, and proper color contrast benefit everyone, not just those with disabilities.
2. Enhances SEO: Search engines favor well-structured websites that are easy to navigate. By making your forms accessible, you improve your SEO, leading to higher search rankings and more visibility.
3. Fosters Community: An inclusive forum encourages participation from a diverse group. When users feel they can easily engage with your content, they are more likely to become active members of your website.
How to Create Accessible Digital Forms

Creating an accessible digital forum involves several key steps. Here’s a breakdown to help you get started:

1. Understand the WCAG Guidelines

The Web Content Accessibility Guidelines (WCAG) are standards designed to make web content more accessible. They provide a framework for creating content that is usable by everyone, including people with disabilities. The guidelines are organized into four principles:
- Perceivable: Information must be presented in a way that all users can perceive, such as providing text alternatives for images.
- Operable: Users must be able to navigate and interact with your site using tools like keyboard navigation and screen readers.
- Understandable: Content must be easy to read and understand, with clear instructions and a consistent layout.
- Robust: Your content should work well across various devices and browsers, ensuring compatibility with assistive technologies.
2. Ensure Text Readability

Text readability is vital for all users, especially those with visual impairments or dyslexia. Here’s how you can improve it:
- Use Clear Fonts: Choose fonts that are easy to read. Avoid overly decorative fonts and ensure your text size is large enough to read comfortably.
- Provide Text Alternatives (WCAG 1.1.1): Include alt text for images, charts, and other non-text content. This helps users who rely on screen readers understand what’s in the visuals.
3. Implement Keyboard Navigation

Many users with disabilities rely on keyboards rather than mice. Make sure your forms are fully navigable using keyboard shortcuts:
- Focus Order (WCAG 2.4.3) : Ensure that users can tab through all interactive elements in a logical order.
- Keyboard Shortcuts (WCAG 2.1.1): Implement keyboard shortcuts for common actions to improve efficiency.
4. Use Descriptive Links and Buttons

Links and buttons should be easily identifiable and descriptive:
- Meaningful Link Text (WCAG 2.4.4): Avoid vague link text like “click here.” Instead, use descriptive text that tells users where the link will take them, such as “Read more about our forum guidelines.”
- Button Labels (WCAG 3.3.2) : Ensure buttons have clear labels that describe their action, like “Submit” or “Cancel.”
5. Ensure Color Contrast and Visual Elements

Good color contrast and visual elements are essential for readability:
- Contrast Ratios (WCAG 1.4.3): Use high contrast between text and background colors. Use tools like the WCAG Contrast Checker to verify that your button colors meet accessibility standards.
- Visual Cues (WCAG 1.3.3): Use visual indicators, such as icons or patterns, in addition to color to convey information. This helps users who are colorblind or have low vision.
6. Test with Real Users

Testing is crucial to ensure your forum is truly accessible:
- User Testing: Involve real users with disabilities in your testing process. Their feedback can help you identify and address accessibility issues you might not have considered.
- Automated Tools: Automated accessibility testing tools such as WAVE or Lighthouse to catch common issues. But remember that these tools can’t catch everything.
7. Stay Updated with Accessibility Trends

Digital accessibility is an evolving field. Stay informed about the latest updates and best practices:
- Ongoing Training: Regularly train your development team on accessibility best practices.
- Community Resources: Participate in accessibility forms and follow industry news to keep up with new developments.
Wrapping Up

Creating accessible web content forms is more than just meeting compliance standards—it’s about fostering a welcoming and inclusive digital space for everyone. By adhering to WCAG guidelines, enhancing text readability, ensuring keyboard navigation, and conducting regular accessibility tests, you can build a forum that all users can navigate and enjoy.

To take your commitment to accessibility to the next level, schedule a complimentary ADA strategy briefing with 216digital. Our team of experts will help develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms.Start integrating these practices today to build a more inclusive and user-friendly forum for everyone. Reach out today to start making a difference!
Greg McNeil

August 14, 2024

How-to Guides

accessible forms, ADA Compliance, digital accessibility, forms, Web Accessibility, web development, Website Accessibility
ADA Compliance for Videos
If you’re a website owner, developer, or content creator, you might already be familiar with the importance of making your site accessible. You might have heard about adding alt text to images or ensuring that your site is navigable using just a keyboard. But what about videos?

Videos are a powerful way to communicate with your audience, but if they aren’t accessible, you could be missing out on a large portion of your audience and might even run into legal issues. In this article, we’re diving into ADA compliance for videos, why it’s important, and how to make sure your videos are accessible to everyone.

What is ADA Video Compliance?

ADA stands for the Americans with Disabilities Act, which was passed in 1990 to prevent discrimination against individuals with disabilities. While it originally focused on physical spaces like buildings, the ADA has evolved to include digital spaces, including websites and the content they host. When we talk about ADA compliance for videos, we’re referring to making sure that your videos can be accessed and understood by everyone, including people with disabilities.

ADA compliance for videos is closely related to the Web Content Accessibility Guidelines (WCAG), which provide a set of standards for making web content more accessible. The most recent version, WCAG 2.1, lays out specific guidelines for making videos accessible.

Why is ADA Video Compliance Important?

You might be wondering why ADA video compliance is so crucial. There are a few key reasons:
1. Inclusivity: Making your videos accessible ensures that everyone, regardless of ability, can engage with your content. This isn’t just the right thing to do, it also makes good business sense. When your content is accessible, you open up your site to a broader audience.
2. Legal Requirements: The ADA requires that digital content be accessible, and failure to comply can result in lawsuits. While the law may not specifically mention videos, courts have interpreted the ADA to include all web content, including multimedia such as videos.
3. Better User Experience: Accessible videos provide a better experience for all users. Features like captions can help people understand your content in noisy environments or when they’re not able to use sound.
4. Search Engine Optimization (SEO): Adding captions, transcripts, and other accessibility features can also help with SEO. Search engines can’t watch videos, but they can read captions and transcripts, which can help your content rank better in search results.
WCAG 2.1 Video Requirements

Understanding and following WCAG guidelines can help make sure your videos meet ADA requirements. The latest version, WCAG 2.1, sets clear rules for making videos accessible, which are important for legal reasons.

WCAG 2.1 details most video-related requirements in Section 1.2. This section focuses on providing alternatives for time-based media like audio and videos. Here are the key guidelines for video content for Level A and AA:
1. 1.2.1: For prerecorded videos with no audio, there must be an audio track that gives the same information.
2. 1.2.2: Captions should be included for all prerecorded audio in videos.
3. 1.2.3: Prerecorded videos should have audio descriptions.
4. 1.2.4: Live videos should include captions for all spoken content.
5. 1.2.5: All prerecorded videos must have audio descriptions.
Tips for Creating Accessible Videos

Provide Captions for Multimedia Content

Captions are text versions of the spoken part of a video or audio. They display the dialogue, sound effects, and other audio cues. For example, if a character in a video says, “I’m going to the store,” the caption will show this text on the screen. Captions are usually placed at the bottom of the video, so they don’t cover up important parts of the visuals.

SC 1.2.2 Captions (Prerecorded) states that all prerecorded video and audio content must have captions. This helps people who can’t hear or who prefer to read understand what’s going on in the media.

Think About Your Audience When Writing Captions

Just adding captions to your videos isn’t enough. You need to ensure they’re accurate, easy to read, and truly helpful for viewers.

Here’s what your captions should do:
- Include All Dialogue and Key Sounds: Capture every word spoken in the video, and don’t forget important sounds and music—for instance, sound effects from sports events.
- Match the Audio and Video: Make sure captions sync up with what’s happening in the video. They shouldn’t lag behind someone speaking or an animation on screen.
- Be Readable: Use a font size that’s big enough for everyone to see comfortably.
- Cover All Your Videos: Add captions to every video you share, even on social media.
Watch Out for Automated Captions

When it comes to captions, it’s best to steer clear of automated tools. While AI has gotten a lot better, these automatic captions still make mistakes that can be annoying and distracting for viewers.

If you do use automated captions, make sure to check them thoroughly for errors. The ideal approach is to create your own captions and transcripts while you’re working on your video scripts.

Include Audio Descriptions

Audio descriptions are better than transcripts for people who are blind or visually impaired. Think of them like a podcast that explains what’s happening in a video. They provide information without requiring the viewer to see the screen.

Adding audio descriptions to your videos might feel a bit unusual at first, but it quickly becomes second nature. Audio descriptions are specifically created to help users with vision loss by describing the visual elements of a video. They include a voice track that fits into the pauses between dialogue and other audio; whenever you can, include audio descriptions in your videos.

Provide a Transcript

WCAG guidelines don’t require transcripts for pre-recorded videos with audio. However, if you publish videos without audio, you need to provide a detailed transcript to meet WCAG SC 1.2.1 (Audio-only and Video-only).

While captions alone can make videos accessible, providing transcripts is a good practice. Transcripts let people read at their own pace, which helps those using assistive technology, non-native speakers, and individuals with learning disabilities.

Make Sure Your Video Player Has Accessible Controls

Many people use keyboards to navigate the web without a mouse. Keyboard accessibility is an important part of making websites usable for everyone, but video players can sometimes create problems for keyboard users. These issues usually come from poor coding or JavaScript problems.

To check if your video player works well with a keyboard, open your website in a browser and use the Tab and Shift-Tab keys to move through the controls. As you test, ask yourself these questions:
- Can I use all the controls on the video player?
- Does the keyboard seem to get “stuck” on any control or part?
- Which part is currently selected by the keyboard?
Avoiding Flashing Content

Videos that flash or flicker can be problematic for people with photosensitive epilepsy. WCAG guidelines recommend avoiding content that flashes more than three times per second to prevent triggering seizures.

How to Install Videos on Your Website to Be Accessible

Now that you understand the importance of ADA video compliance and the relevant WCAG guidelines, let’s talk about how to install videos on your website to ensure they are accessible.

Choose an Accessible Video Player

The first step is to choose a video player that is designed with accessibility in mind. Many popular video players, like YouTube’s embedded player, already have features like keyboard accessibility and customizable captions. If you’re using a custom video player, make sure it meets WCAG guidelines by testing it with keyboard navigation and screen readers.

Add Captions to Your Videos

When you upload a video to your site, you’ll want to make sure it has captions. If you’re using a platform like YouTube, you can upload your own captions or use the platform’s automatic captioning feature, though it’s a good idea to review and edit these captions for accuracy. If you’re hosting videos yourself, there are many tools available for creating and syncing captions.

Provide Transcripts

After you’ve added captions, the next step is to create a transcript of the video. You can offer the transcript as a downloadable file or display it directly on the page below the video. Providing a transcript not only helps with accessibility but can also improve your site’s SEO.

Include Audio Descriptions

For videos with important visual content that isn’t described in the audio, consider creating a version of the video with audio descriptions. This can be as simple as adding a voiceover that describes key visual elements or creating a separate audio track that users can turn on if they need it.

Test Your Videos for Accessibility

Once you’ve added all the necessary accessibility features, it’s important to test your videos to ensure they are actually accessible. This means watching the video with captions and a screen reader, navigating the player with just a keyboard, and making sure the video content is clear and understandable, even without sound or visuals.

Use an Accessibility Checker

There are many tools available that can automatically check your site’s accessibility, including your videos. These tools can identify issues you have missed and suggest ways to fix them. Regularly running these checks can help you maintain ADA compliance as you add new content to your site.

Make Accessibility a Priority

Web accessibility isn’t just a legal requirement—it’s a way to make your content more inclusive and reach a wider audience. By focusing on ADA video compliance, you’re taking important steps to ensure that everyone, regardless of ability, can enjoy and engage with your content. Whether you’re a website owner, developer, or content creator, making your videos accessible should be a top priority.

Remember, accessibility is an ongoing process. As you continue to create and share video content, keep WCAG guidelines in mind, and make it a habit to review and update your accessibility features regularly. Not only will this help you avoid legal issues, but it will also help you create a more inclusive and welcoming online experience for all your users.

If you need help with video accessibility or legal compliance, we’re here to help. Schedule a briefing with 216digital today so that you can confidently take this next step into digital accessibility.
Greg McNeil

August 9, 2024

How-to Guides

Accessibility, ADA Compliance, ADA Website Compliance, videos and audio content, Web Accessibility, web development, Website Accessibility

Why Accessibility Matters for Slideshows and Carousels

Key Considerations for Accessible Slideshows

Keyboard Navigation

Best Practices:

Descriptive Labels and Alt Text

Best Practices:

Pause/Play Buttons

Best Practices:

Using ARIA Roles for Screen Reader Compatibility

Best Practices:

Poor Color Contrast

Best Practices:

Testing for Accessibility

Ways to Test:

Final Thoughts

Why It’s Important to Ensure Your Agency Understands Digital Accessibility

When Is the Best Time to Ask Your Agency About Accessibility?

Key Web Accessibility Questions to Ask Your Digital Agency

What Is the Current State of Web Accessibility on Our Website?

What Is Your Approach to Web Accessibility?

How well do you know WCAG 2.1 guidelines?

Do you integrate accessibility into every stage of development?

Do you use both automated and manual testing methods?

How Will You Ensure Accessibility Is Maintained?

Do you offer ongoing accessibility monitoring?

Can you train our team to maintain accessibility?

What is your process for updating the site to stay compliant with new regulations?

How Do You Prioritize Web Accessibility Issues?

How do you determine which issues need immediate attention?

How long will it take to resolve accessibility issues?

What’s Your Experience with Similar Projects?

Have you worked with other companies in our industry?

Can you show us examples of websites you’ve made accessible?

Prioritize Accessibility from the Start

Contact 216digital for Your Accessibility Needs

Challenges of Website Pop-Ups for Accessibility

Hard to Close or Dismiss

Improperly Labeled Pop-Ups

Focus Trap

Disruption of Browsing Experience

Best Practices for Accessible Pop-Ups

Make Sure Pop-Ups Are Easy to Close

Code Tip: Include a Keyboard Shortcut

Properly Label the Pop-Up for Screen Readers

Code Tip: Use ARIA Attributes for Accessibility

Prevent Focus Trapping

Code Tip: Manage Focus Correctly

Avoid Disrupting the Browsing Experience

Example:

Keep the Design Simple and Clear

Test with Real Users and Assistive Technologies

Tools for Testing Pop-Up Accessibility:

Make a Pop with 216digital

What is Web Accessibility?

Why Accessible Coding is Important

1.Provide Alt Text for Non-Text Components

Why Alt Text is Important:

Best Practices for Writing Alt Text:

Example:

2. No Keyboard Traps

How to Prevent Keyboard Traps:

Example:

3. Allow Users to Resize Text

How to Implement Text Resizing:

Example:

4. Avoid Seizure Triggers

How to Prevent Seizure Triggers:

Example:

5. Follow a Logical Reading and Code Order

How to Implement a Logical Code Order:

Example:

6. Use Headings Appropriately

Best Practices for Headings:

Example:

7. Use HTML Tags That Make Websites Accessible

Key Accessible HTML Elements:

Example:

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

What Is ARIA and Why Is It Important?

ARIA Landmarks: What Are They?