Testing is a key part of ensuring accessibility. Although we test websites and applications at any point pre or post launch, we strongly encourage early testing, beginning with prototyping and at the start of platform configuration. The earlier inclusive design is incorporated, and the earlier issues are identified and fixed, the easier it will be to ensure accessibility.

Types of tests

We offer multiple types of tests:

• Formal tests. These are comprehensive manual tests, conducted with screen readers and alternative input devices, and include usability, per the WCAG standards. Results are written in plain language, issues are prioritized, and we include guidance on solutions. We also follow up our tests with support to help you implement fixes.
• Quick tests. These are shorter, more focused tests, and include a write-up and recommendations. We follow up with support to help you implement fixes.
• Website pre-launch checks, done either independently or as part of the Office of Communications website review process.
• Automated monitoring. The University's public-facing academic and administrative sites are monitored for accessibility. We use the DubBot monitoring tool. Results help improve individual sites, the University's supported website platform called SiteBuilder, and training and outreach.
• Testing with people with disabilities. We are running a pilot with Fable Engage to usability test websites and applications with people with disabilities. Request a Fable test.
• DIY testing training and certification. We teach staff how to run their own base level accessibility tests on websites and applications, and offer a Certificate in Accessibility Testing.

While we encourage website and application owners to test for accessibility, we ask that campus partners contact us for screen reader and alternative input device testing. Effective and comprehensive screen reader testing requires specialized skills and the use of multiple devices.