Web Access Clinics

Request a Web Access clinic if:

• You have a campuswide system, application, or interactive web-based product (this does not include most websites);
• The Disability Access and Compliance department has requested that your website needs a review by the Web Access team. 

Web Access clinics are free-of-charge, held twice a month, and prioritized on a first-come, first-served basis following the above guidelines. You must plan ahead as clinic dates are limited and may fill up in advance.

If your campus team needs a Web Access clinic before the next available clinic date, contact webaccess@berkeley.edu for a list of third-party suppliers who can assess your product/site for a fee. Your team is responsible for working with one of these suppliers.

In order to have a Web Access clinic, you must submit proof of keyboard and/or mobile testing before the clinic date; see the Request a Web Access clinic form (below) for details. 

Request a Clinic form

If your site meets the above criteria for a clinic, please fill out Request a Web Access clinic form. The Web Access team will review your request and follow up accordingly. 

If your site is not a campuswide system, application, or web-based product, or a special-exception website, then you should not request a Web Access clinic; instead, please read the rest of this page for information about accessibility requirements and resources. 

Accessibility requirements and resources

All electronic assets, whether developed in-house or purchased, need to comply with the systemwide accessibility policy (WCAG 2.0AA) policy, and the campus functional owner is responsible for ensuring compliance. The campus functional owner is responsible for addressing overall accessibility issues throughout the lifecycle of the campus system and application (desktop, web-based, or mobile), and ensuring compliance with the systemwide policy (WCAG 2.0AA).

All campus site owners should use Siteimprove and the DIY Accessibility Checklist, and follow the Website Owner Responsibilities as outlined on the Disability Access and Compliance website.

The following resources are available to help meet accessibility requirements:

• Open Berkeley: fully-managed website solution for campus websites. Since accessibility is built into the platform, Open Berkeley websites do not need to be reviewed in a Web Access clinic. Open Berkeley Site Builders/Editors/Contributors should follow best practices for content creators when using the platform's tools to work on their websites.
• Siteimprove: The UC has a systemwide contract with Siteimprove, an automated accessibility tool. This tool will often catch common accessibility issues, such as heading structure and alt text. All Berkeley.edu websites (including Open Berkeley websites) are strongly encouraged to enroll in Siteimprove.
• DIY Accessibility Checklist: This robust checklist is designed to be used throughout the website development process, and was created based on the Web Access team’s experiences with reviewing websites for accessibility.
• Keyboard Testing: One of the best ways a developer can ensure that they’ve created an accessible foundation for their product is to test it using only the keyboard. Keyboard accessibility is part of the WCAG 2.0 standard. The Keyboard Testing checklist can help developers ensure keyboard accessibility.