Testing as Part of the Process

Accessibility testing is not a one-time activity. It is part of an ongoing process that includes evaluation, remediation, and validation. Effective testing approaches typically combine:

  • Automated tools to identify common issues
  • Manual testing to evaluate real user experience
  • Assistive technology testing to confirm usability

Quick Start Testing Workflow

Use this workflow as a starting point when evaluating digital content, tools, or supplier products:

  1. Run an automated scan

    Use tools such as WAVE, Axe, or Lighthouse to identify common issues quickly across pages and content.

  2. Review structure and content manually

    Check headings, links, forms, keyboard navigation, and focus order. Automated tools cannot catch everything.

  3. Test with assistive technology

    Use a screen reader (NVDA, JAWS, or VoiceOver) to evaluate usability and real-world experience.

  4. Document findings

    Capture issues, impacted users, severity, and recommended fixes.

  5. Validate after remediation

    Re-test to confirm issues are resolved and no new barriers were introduced.

Web and Digital Content Testing

These tools support ongoing testing of websites and digital content. Used to identify common issues including:

Missing alternative textColor contrast issuesStructural and semantic errors
  • WAVE Web Accessibility Evaluation Tool ↗Free browser-based tool for quick review of public-facing pages or demo environments. Provides visual feedback directly on the page.
  • Axe DevTools (Deque Systems) ↗Deeper testing of web applications during development and evaluation. Available as a browser extension and CI/CD integration.
  • Arc Toolkit (TPGi) ↗Browser extension designed to be integrated into automated and manual accessibility test workflows.
  • SiteImprove ↗Automated scanning platform that continuously monitors your site and identifies accessibility issues at scale.
  • Google Lighthouse ↗Open-source automated tool built into Chrome DevTools for improving the quality of web pages, including accessibility auditing.
  • ANDI Accessibility Testing Tool (SSA) ↗Free bookmarklet tool from the Social Security Administration for identifying common 508 compliance issues including missing alt text, contrast problems, and semantic errors.

Document and PDF Testing

Assistive Technology Testing

These tools validate real user experience and are essential alongside automated scanning.

  • NVDA (NonVisual Desktop Access) ↗Free, open-source screen reader for Windows. Widely used for accessibility testing, commonly paired with Firefox and Chrome.
  • JAWS (Job Access With Speech) ↗Commercial screen reader widely used in enterprise and government environments. Standard tool for accessibility evaluation.
  • VoiceOver (Apple) ↗Built-in screen reader for macOS, iOS, and iPadOS. Standard tool for evaluating mobile and Apple platform accessibility.
Key areas to evaluate with assistive technology:
  • Navigation and structure
  • Reading order
  • Interactive elements
  • Feedback and announcements

e-Learning and Application Testing

Interactive environments require additional validation using a combination of automated tools, manual keyboard testing, and screen reader testing.

Evaluate for:
  • Focus order and interaction flow
  • Accessible navigation and controls
  • Labels, instructions, and feedback
  • Compatibility with assistive technologies

ICT Testing Baseline Portfolio (U.S. Access Board)

ICT Testing Baseline PortfolioThe ICT Testing Baseline Portfolio defines a standardized set of accessibility tests used to evaluate digital content for Section 508 conformance. It outlines what must be tested — across web, documents, and other ICT — to ensure consistent, reliable results across agencies. This resource aligns with WCAG requirements while remaining tool-agnostic and adaptable to different testing approaches.