assistive technology Archives /Tag

How to Use JAWS for Screen Reader Testing
For millions of people with visual impairments, screen readers like Job Access With Speech (JAWS) are essential for navigating the digital world. According to a 2024 WebAIM survey, JAWS continues to lead the way as one of the most widely used screen readers, with 41% of respondents relying on it—outpacing other tools like NonVisual Desktop Access (NVDA) and Apple VoiceOver.

If you’re focused on building an accessible digital experience, incorporating screen reader testing into your workflow is a must. Not only does it help you create a more inclusive website, but it also supports compliance with accessibility laws like the Americans with Disabilities Act (ADA), WCAG standards, and more.

In this guide, we’ll break down how to use JAWS for accessibility testing, explore essential commands, and share tips for improving your website’s usability. But first, a quick look at what makes it such a powerful tool.

What is JAWS?

JAWS, developed by Freedom Scientific, is a screen reader that converts on-screen text into speech or braille for users who are blind or visually impaired. It allows users to navigate websites, applications, and documents without needing to see the screen.

JAWS is one of the most popular screen readers globally, making it an essential tool for web accessibility testing. By simulating how users rely on assistive technologies, JAWS helps you identify barriers that may prevent someone from fully engaging with your website.

Why is JAWS Essential for Accessibility Testing?

Accessibility testing is about ensuring everyone, regardless of ability, can interact with your website. JAWS plays a vital role in this process because:
- Real-World Simulation: JAWS mimics how many visually impaired users experience the web, allowing you to uncover issues that automated tools might miss.
- WCAG Compliance: Testing with JAWS helps ensure your website complies with the Web Content Accessibility Guidelines (WCAG), a global standard for digital accessibility.
- Improved User Experience: By identifying and fixing accessibility barriers, you create a more inclusive, user-friendly experience for all visitors.
How to Set Up JAWS
1. Download and Install JAWS: Visit the Freedom Scientific website to download JAWS. While it’s a paid tool, a 40-minute free demo mode is available for testing purposes.
2. System Requirements: Ensure your computer meets the system requirements. JAWS works on Windows but does not support macOS directly.
3. Set Up Your Environment: Use headphones to listen while testing so the screen reader’s output doesn’t interfere with other tasks.
4. Familiarize Yourself with the Settings: Spend time exploring the settings menu to adjust speech rate, verbosity, and other preferences.
Key JAWS Commands You Need to Know

Learning a few essential JAWS commands will make testing faster and more effective. Here are some basics to get you started:
- Navigating Headings: Press H to jump to the next heading and Shift + H to go to the previous heading.
- Lists: Press L to move to the next list and I to navigate to individual list items.
- Links: Use Tab to navigate through links or Insert + F7 to bring up a list of all links on the page.
- Forms: Press F to jump to the next form field and Shift + F to go to the previous one.
- Read the Page: Use Insert + Down Arrow to read the page continuously or Arrow Keys for manual reading.
Step-by-Step Guide to Testing Web Accessibility with JAWS

Start with the Homepage

Open your website’s homepage and let JAWS read through it. Check if the content flows logically and whether important elements, like headings and links, are announced correctly.

Test Navigation

Use the Tab key to navigate through links and interactive elements. Ensure focus indicators are visible and links are descriptive (e.g., “Learn More” should specify the action or page it leads to).

Evaluate Headings

Press Insert + F6 to bring up a list of headings. Verify that they are hierarchical and descriptive, making it easier for users to navigate.

Check Forms

Navigate through form fields using the F key. Test for proper labeling, keyboard navigation, and error message announcements.

Test Images and Alt Text

JAWS will read the alt text of images. Ensure images have descriptive alt text and that decorative images are marked appropriately (e.g., as null or empty).

Assess ARIA Roles and Landmarks

Use JAWS to test ARIA roles, landmarks, and live regions. Verify that these elements provide meaningful context to screen reader users.

Document Issues

As you test, document any barriers you encounter, such as missing alt text, unclear link descriptions, or inaccessible forms. Include the steps to replicate the issue and suggest solutions.

Tips for Effective JAWS Testing
- Pair with a Keyboard-Only Test: Ensure your website is fully navigable using only a keyboard, as this is crucial for screen reader users.
- Listen Critically: Pay attention to how JAWS announces content. Confusing or incomplete announcements signal a need for improvement.
- Focus on User Experience: Think about how easy it would be for a JAWS user to accomplish key tasks on your website, such as making a purchase or finding contact information.
- Test Multiple Pages: Don’t stop at the homepage. Test a variety of pages, including forms, product pages, and blogs.
Limitations of JAWS

While JAWS is an invaluable tool for accessibility testing, it has limitations:
- Cost: It is expensive, which may be a barrier for smaller teams or independent developers.
- Learning Curve: The abundance of commands and settings can be overwhelming for beginners.
- Not a Catch-All Solution: JAWS testing alone cannot guarantee accessibility compliance. It’s essential to pair it with other tools and techniques.
Why JAWS Should Be Paired with Other Tools

JAWS provides critical insights, but no single tool can capture all accessibility issues. Consider pairing it with:
- Automated Testing Tools: Tools like WAVE and Lighthouse can quickly identify common issues, such as missing alt text or low contrast.
- Other Screen Readers: Testing with multiple screen readers, such as NVDA or VoiceOver, ensures compatibility across platforms.
- Manual Testing: Involve users with disabilities in your testing process to gain authentic feedback.
Building a More Inclusive Web

Testing your website with JAWS is a powerful step toward creating an inclusive digital environment. By understanding how screen reader users interact with your content, you can uncover barriers and make meaningful improvements. Remember, accessibility is not just about compliance—it’s about creating a web that works for everyone.

While JAWS is a fantastic tool, it should be part of a broader accessibility strategy that includes other tools, user testing, and a commitment to following WCAG guidelines. With the actionable insights from this guide, you’re well on your way to improving your website’s accessibility and making a positive impact on all your users.

Let’s work together to make the web a more inclusive place!

Need help with accessibility testing? If you’re ready to take your accessibility efforts to the next level, 216digital can help. Our team specializes in comprehensive accessibility solutions that go beyond surface fixes. Schedule an ADA briefing with us today by using the contact form below. Let’s work together to make your website accessible to everyone.
Greg McNeil

January 16, 2025

How-to Guides, Testing & Remediation

Accessibility testing, assistive technology, How-to, JAWS, screen readers, user testing
Making Hidden Content Accessible to Assistive Technologies
As a web developer, you want your website to be usable by everyone, including people who rely on assistive technologies. These technologies—such as screen readers, braille displays, and speech recognition software—can help individuals with disabilities navigate the web more easily. Sometimes, you may need to hide certain parts of your webpage visually without hiding them from these tools. However, doing this incorrectly can cause big accessibility issues.

In this article, we’ll explore how to effectively hide and manage hidden content for people using assistive technologies. We’ll discuss why display: none is problematic, how to use the clip pattern, and how attributes like aria-hidden and hidden can help. By the end, you’ll have a better understanding of how to ensure your website remains inclusive and user-friendly.

The Problem with display: none

When you use display: none in your CSS, you remove an element from the visual flow of the page. This means sighted users will not see it. But, it also means the element is completely invisible to assistive technologies such as screen readers. If you’ve hidden important text or controls this way, users who rely on assistive technologies might miss out on content or functionality that they need.

For example, imagine you have a button that visually looks like an icon, but you hide the text label using display: none. Now, people who can see the icon know what the button does, but people using assistive technologies hear nothing. This creates a poor user experience and makes your site less accessible.

The Clip Pattern: A Better Approach

To visually hide content while keeping it available to assistive technologies, the clip pattern is a popular solution. The idea is to position the element off-screen so sighted users don’t see it, but screen readers can still find it. Here’s an example:
```
.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  border: 0;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
}
```
By applying the .visually-hidden class to your element, you ensure it’s hidden visually but remains accessible to assistive technologies. This makes the content discoverable by screen readers, letting users who can’t see the screen still benefit from it.

Why the Clip Pattern Works

This pattern relies on moving the element so it’s not visible in the viewport and restricting its size to 1px by 1px. With clip: rect(0, 0, 0, 0); (or clip-path in modern CSS), the browser cuts off any visual display. Yet, the element remains in the Document Object Model (DOM), meaning assistive technologies can still access it. That’s the key difference between this and display: none.

Managing Visibility with aria-hidden and the hidden Attribute

Beyond CSS, there are HTML and ARIA (Accessible Rich Internet Applications) attributes that also control how content is shown to both users and assistive technologies. Two important attributes here are aria-hidden and the HTML5 hidden attribute.

aria-hidden="true"

When you add aria-hidden="true" to an element, you’re telling assistive technologies not to read or announce that element to users. This is handy for decorative images or redundant content. For instance, if you have a background image that doesn’t provide important information, you could mark it with aria-hidden="true" so screen readers ignore it.

But be cautious: if you need an element to be read by assistive technologies, do not use aria-hidden=”true”. This attribute will block that element from being announced entirely.
```
<div aria-hidden="true">
  <img src="decorative-image.jpg" alt=""/>
</div>
```
HTML5 hidden Attribute

The hidden attribute is another way to remove content from everyone—both sighted users and assistive technologies. When you use it, browsers typically hide the element. Screen readers will also skip it. This is good if the element is meant to be inaccessible to all users, like a form section that’s not yet relevant or a menu item that’s not available.
```
<div hidden>
  <p>This content is hidden from all users.</p>
</div>
```
Use hidden or aria-hidden when you truly want to exclude an element from assistive technologies. If you want it hidden visually but still available to screen readers, you should stick with the clip pattern or .visually-hidden approach.

Best Practices for Accessible, Visually-Hidden Content

1. Use Semantic HTML

Using proper semantic HTML elements (like <nav> for navigation, <main> for main content, or <section> for thematic grouping) is important for clear structure. It helps assistive technologies interpret your content correctly. Semantic HTML also reduces the need for extra attributes and complex styling, since the markup itself conveys meaning.

2. Avoid Hiding Focusable Elements

If an element can receive focus (like links, form inputs, or buttons), think carefully before hiding it. A hidden yet focusable element can be confusing for keyboard-only users, since it might get focus without being visible. If you must hide a focusable element, consider removing it from the tab order by using tabindex="-1" or ensuring it’s properly revealed at the right time.

For example, if you have a pop-up form that appears only after a button click, you can initially hide it with the clip pattern. Once the user clicks, you can remove the clip pattern or switch the CSS to show the content. This way, the form becomes available to both sighted users and people using assistive technologies at the same time.

3. Provide Context for Hidden Content

Sometimes you want to reveal hidden content dynamically (like a drop-down menu). In these cases, use ARIA attributes such as aria-expanded and aria-controls to inform assistive technologies that a certain part of the page is now visible or hidden. This can help screen reader users understand changes on the page.
```
<button aria-expanded="false" aria-controls="menu" id="menuButton">
  Toggle Menu
</button>

<nav id="menu" class="visually-hidden">
  
</nav>
```
When you click the button, you can toggle its aria-expanded value from false to true, and remove the .visually-hidden class from the menu. This ensures that both visual and non-visual users know the content has been revealed.

4. Test with Multiple Assistive Technologies

It’s important to test your website with different assistive technologies because each one may behave slightly differently. Popular screen readers include NVDA, JAWS, and VoiceOver. Don’t forget to check on both desktop and mobile devices. Regular testing can help you catch accessibility issues before your users do.

Handling Localization

If you’re translating your site into multiple languages, remember that hidden text might also need translation. For example, your .visually-hidden text for instructions or links should be available to screen readers in every supported language. Make sure your language attributes (like lang="en") are correct, and consider cultural differences that could impact how you label hidden elements.

For instance, if you have an English site and a Spanish site, your hidden instructions should be translated into Spanish on the Spanish version. This ensures that users relying on assistive technologies can access the content in the correct language.

Putting It All Together: A Quick Example

Let’s look at a simple example of an accessible button that has visually hidden text:
```
<button class="icon-button">
  <span class="visually-hidden">Submit Form</span>
  <img src="icon-submit.png" alt="" aria-hidden="true" />
</button>
```
- The .visually-hidden class hides the text “Submit Form” from sighted users, but screen readers can still read it.
- The <img> tag includes an empty alt attribute and aria-hidden="true", so assistive technologies ignore the image itself.
- Sighted users see only the icon, while screen reader users hear “Submit Form.”
This example keeps your content accessible to people using assistive technologies and also meets visual design needs.

Additional Resources
- Web Content Accessibility Guidelines (WCAG): A detailed guide on making web content accessible.
- WAI-ARIA Authoring Practices: Official tips on using ARIA roles, states, and properties.
- MDN Web Docs on ARIA: In-depth explanations of ARIA attributes and best practices.
Exploring these resources will help you master hiding content effectively, ensuring people who use assistive technologies can still access everything they need.

Conclusion

Hiding content from sighted users while keeping it accessible to assistive technologies is an essential skill for modern web developers. By avoiding display: none for important information, using the clip pattern for visually hidden content, and carefully leveraging aria-hidden or hidden, you can ensure everyone has a good experience on your site.

Remember to keep the following points in mind:
1. Use the clip pattern (.visually-hidden) to hide content from sighted users but keep it readable by assistive technologies.
2. Use aria-hidden and hidden only when you truly want to hide content from all users, including those using assistive technologies.
3. Pay attention to focusable elements, making sure you don’t accidentally trap keyboard users in hidden sections.
4. Test frequently with various tools and real users to ensure your hidden content behaves as you expect.
5. Localize your hidden text so that people using assistive technologies in other languages can also benefit.
By following these guidelines, you’ll be well on your way to building inclusive websites that work for everyone. Your careful attention to accessibility shows that you value all your users, regardless of their abilities or the assistive technologies they use. Embracing these practices will help ensure a positive, welcoming, and user-friendly experience across the board.
Greg McNeil

December 31, 2024

How-to Guides

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

What are Screen Readers and Who Uses Them?

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

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

How Do Screen Reader Users Browse the Internet?

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

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

Why is Screen Reader Testing Important?

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

Ensuring Digital Accessibility

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

Complying with Legal Requirements

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

Improving User Experience

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

Reaching a Wider Audience

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

What Are the Different Approaches to Accessibility Testing?

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

Automated Testing

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

Some popular automated accessibility testing tools include:
- WAVE: A web accessibility evaluation tool that highlights accessibility issues directly on your webpage.
- Lighthouse: A tool built into Chrome that can audit your website for performance, SEO, and accessibility issues.
While automated testing is a great starting point, it should never be the only method you use. Automated testing covers only 30-40% of accessibility guidelines and can miss more subtle or complex problems that require human judgment.

Manual Testing

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

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

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

To conduct user testing:
- Recruit Testers: Find users who rely on screen readers and other assistive technologies to test your website. You can reach out to local organizations, online communities, or professional networks to find willing participants.
- Observe and Take Notes: Watch how the testers interact with your website and take note of any issues they encounter. Pay attention to their feedback and use it to make improvements.
- Iterate and Improve: After making changes based on user feedback, test again to ensure that the issues have been resolved.
User testing can be more expensive and time-consuming than other methods, but it provides the most valuable insights.

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

How to Perform Screen Reader Testing

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

Choose Your Screen Readers

There are several different screen readers available, each with its own unique features and quirks. The most commonly used screen readers in the United States are:
- NVDA (NonVisual Desktop Access): A free and open-source screen reader for Windows.
- JAWS (Job Access With Speech): A popular screen reader for Windows, often used in workplaces.
- VoiceOver: The built-in screen reader for MacOS and iOS devices.
- TalkBack: The built-in screen reader for Android devices.
To ensure that your website is accessible to the widest audience possible, it’s important to test with more than one screen reader.

Familiarize Yourself with Screen Reader Commands

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

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

Navigate Your Website

Start by opening your website with the screen reader turned on. Listen to how the screen reader announces the content, and use keyboard commands to navigate through the site. Pay attention to the following:
- Headings: Are they announced correctly? Do they provide a clear structure for the page?
- Links and Buttons: Are they labeled correctly? Do they make sense out of context?
- Forms: Are the form fields and labels announced clearly? Is it easy to fill out the form using only the keyboard?
Identify and Fix Issues

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

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

Test on Different Devices

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

Conclusion

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

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

July 31, 2024

WCAG Compliance

assistive technology, digital accessibility, screen readers, Web Accessibility, web development, Website Accessibility

How to Use JAWS for Screen Reader Testing

What is JAWS?

Why is JAWS Essential for Accessibility Testing?

How to Set Up JAWS

Key JAWS Commands You Need to Know

Step-by-Step Guide to Testing Web Accessibility with JAWS

Start with the Homepage

Test Navigation

Evaluate Headings

Check Forms

Test Images and Alt Text

Assess ARIA Roles and Landmarks

Document Issues

Tips for Effective JAWS Testing

Limitations of JAWS

Why JAWS Should Be Paired with Other Tools

Building a More Inclusive Web

Making Hidden Content Accessible to Assistive Technologies

The Problem with display: none

The Clip Pattern: A Better Approach

Why the Clip Pattern Works

Managing Visibility with aria-hidden and the hidden Attribute

aria-hidden="true"

HTML5 hidden Attribute

Best Practices for Accessible, Visually-Hidden Content

1. Use Semantic HTML

2. Avoid Hiding Focusable Elements

3. Provide Context for Hidden Content

4. Test with Multiple Assistive Technologies

Handling Localization

Putting It All Together: A Quick Example

Additional Resources

Conclusion

Screen Readers 101: Making Your Site Accessible

What are Screen Readers and Who Uses Them?

How Do Screen Reader Users Browse the Internet?

Here’s a simplified version of how it works:

Why is Screen Reader Testing Important?

Ensuring Digital Accessibility

Complying with Legal Requirements

Improving User Experience

Reaching a Wider Audience

What Are the Different Approaches to Accessibility Testing?

Automated Testing

Manual Testing

User Testing

How to Perform Screen Reader Testing

Choose Your Screen Readers

Familiarize Yourself with Screen Reader Commands

Navigate Your Website

Identify and Fix Issues

Test on Different Devices

Conclusion

The Problem with `display: none`

Managing Visibility with `aria-hidden` and the `hidden` Attribute

`aria-hidden="true"`