Web Accessibility Testing

Factors to consider when preparing to test your site

Each website or application has different needs, defined by purpose and audience, as well as the skills of the designers and developers. While there is no blueprint for website assessment, here are some factors to consider when preparing to test your website.

Quick Fixes

Does your site use a template? Style sheets? Application frameworks? A content management system? Test shared code and structure across a small number of representative pages to see whether there are recurring problems that can be addressed in a common library or shared file. Look for keyboard operability, nested headings, broken skip links, poor color contrast, and other issues that can be addressed quickly in a template or library.

Participation

Which of your web resources is necessary for users to participate in your site? If an inaccessible home page, login or registration screens, catalogs, LMS documents, data outputs, calendars, social media, or other content types will impact a user's full participation, test these resources first.

Resources directed specifically to people with disabilities

It goes without saying that resources for disability-related services need to be accessible. Be sure to test site resources aimed at users with disabilities.

Traffic

All else being equal, prioritize resources that receive a lot of traffic over those that are rarely visited. The UI Web Accessibility Policy specifies testing and remediation of the top 20% of non-compliant pages on your site each year.