Getting Started with Accessibility Testing

This section is designed to help people who are new to accessibility, want a foundational understanding of how to get started with testing, or are looking for practical ways to integrate accessibility testing tools and techniques into workflows. This section should not be considered as a comprehensive guide for accessible content creation, substitute for ongoing training, or replace professional audits or legal advice. Recommended resources will not be a comprehensive list of every tool or standard for accessibility.

What is accessibility testing?

Accessibility testing refers to testing elements of digital content to determine if they meet accessibility guidelines and standards. Accessibility testing can help you identify areas where your content needs work, sometimes assist in remediating accessibility issues, and give you a place to start ensuring that digital resources are usable by people with a wide range of disabilities and abilities.

There are many types of accessibility testing; this guide focuses on two main types:

  • Automated testing involves using tools to scan digital content for potential accessibility issues. These tools typically compare your content to a defined threshold or standard and alert you if your content does not meet that threshold or standard. Automated tools are a great place to start, but many times, they are not sufficient as the only form of testing.
  • Manual testing involves people using techniques to evaluate if content meets an accessibility standard. Where automated testing alerts you if something doesn’t meet a standard, in manual testing you are determining if your content meets a standard. This guide intends to give you context and techniques so you are able to do manual testing when needed.

Why should I test for accessibility?

There are many reasons why you should test for accessibility. The primary reason is to ensure that all patrons and staff have equitable access to all library resources as per institution, state, and/or federal guidelines and regulations. Showing a track record of accessibility testing can also protect individuals and institutions from legal challenges if accessibility concerns arise. Another potential reason for accessibility testing is to promote community engagement. Conducting regular accessibility testing signals to your community that you and your library value inclusion.

Regardless of personal or institutional reasons for testing accessibility, ensuring content is accessible benefits everyone. For example, captioning videos is essential for people with hearing disabilities, but it also benefits non-native English speakers and people in noisy environments.

The tools and resources in this section are organized with the intention of allowing for both browsing and topic navigation. As such, there is intentional repetition throughout, and you may notice some of the information between the core concepts and other content types overlap or repeat.

Tools organized by content type

Frequently used tools for automated testing

  • Browser Extensions and Bookmarklets for Automated Web Page Testing
    Automated accessibility testing cannot replace manual testing by an actual human being, but it can be a good first step in supporting ongoing efforts to meet accessibility goals. Extensions and bookmarklets typically compare content of a web page to a set of standards and alert you when there are possible issues.
  • Developer Tools Built-in to Browsers
    These tools are intended for web developers with some familiarity with HTML or DevTools but may be useful in some applications for those checking web content who are willing to learn a bit.
  • Color Contrast or Contrast Ratio
    Color checkers, also known as color contrast checkers, are automated accessibility tools used to test if text, icons, or other interface elements have sufficient color contrasts to be readable by people with low vision or color-vision deficiencies.

Frequently used tools for manual testing

  • Reading Order or Logical Reader Order
    Reading order describes the movement through digital content, which should follow an order that matches the visual and logical order of the content. Logical reading order is essential for screen reader users and navigation of the content. (Includes the #NoMouse Challenge.)
  • Screen Readers / Text-to-Speech
    Screen Readers and Text-to-Speech software can be useful when testing content for accessibility by giving you insight into the experience of a user trying to access your content with that software. They are most helpful for testing the navigation and structure of content.

What questions or feedback do you have? 

Let us know using our DUX Accessibility Toolkit feedback form.