DIY Accessibility Checklists

The University of California has a systemwide policy that requires websites, web-based applications, mobile applications, and other software to be accessible to persons with disabilities, including those who use assistive technology. Currently, the policy identifies the Web Content Accessibility Guidelines (WCAG) 2.0 AA as the standard to meet for websites and web-based applications.

Designers, developers, and suppliers can use the following resources to help make sure their products comply with the systemwide policy.

Do-It-Yourself (DIY) Accessibility for Developers

We've created a master spreadsheet containing the DIY Accessibility Checklist. This spreadsheet is available at the bottom of this page. The individual sections of the checklist are explained in additional details in the below set of links. 

For UC Berkeley departments/units:

If you will be requesting a Web access clinic for your website, we recommend that you complete as many of the checklists as possible in advance. We tend to see the same problems over and over again in our clinics. If you can fix the common issues identified in the checklists before we review your site, we'll be able to focus on the issues that require judgment and in-person testing.

For anyone else:

Anyone is free to copy, adapt, and use as a guide in their development or testing process. 

 check box, computer monitor, and keyboard

Strongly Recommended

For Berkeley or other UC sites, you should prioritize these sections of the checklist in order to make sure your project complies with the systemwide policy:

 HTML code on laptop screen, and three people talking

Recommended

And the following sections are generally recommended: