All UC Berkeley websites must adhere to WCAG technical standards. Below are additional requirements.
Choose a platform that is capable of creating accessible content.
- Open Berkeley is a fully-managed website solution that's designed to be accessible and makes it easy for content editors to create accessible content.
- For any other platforms (e.g., WordPress, Drupal, Expression Engine, Django, Rails, Gatsby, React, custom-built, etc.), your department must have enough expertise to ensure your site is accessible. You are responsible for understanding and managing the underlying source code.
- If you're using site-building services or third-party developers, consult with the provider on how they will address accessibility issues. Accessibility should be included in any contract agreement with third-party developers and agencies. Prior to procuring or renewing contracts, the UCB unit or department should have completed the Accessible Technology Procurement intake form.
The following third-party no-code hosting services are PROHIBITED at UC Berkeley:
- Softr
- Squarespace
- Webflow
- Weebly
- Wix
Accessibility overlays are PROHIBITED at UC Berkeley.
Overlays promise site owners a quick and easy fix for inaccessible websites, but they do not work as promised. Some examples include UserWay and accessiBe. Learn why overlays are so challenging by reading Overlaying Overconfidence - My Lived Experience with Overlays and how Accessibility Overlay Widgets Attract Lawsuits.
Monitor and fix accessibility issues.
- All public berkeley.edu subdomains must be in Siteimprove, a service that provides automated accessibility testing for our websites.
- Use both manual testing and automated testing (Siteimprove) to identify and fix accessibility failures on your website.
In your website footer, include an Accessibility link.
Using the link text, "Accessibility," provide a link to the Report a Web Accessibility Issue page. Refer to the footer of this web page for Accessibility, Nondiscrimination and Privacy links.