Website Access Requirements

Information, Resources and Guidance

In 2003, the U.S. Department of Justice issued the first guidance on website compliance with Section 508 of the Rehabilitation Act of 1973, and with the Americans with Disabilities Act. In 2013 UCOP adopted its ‘Information Technology Access Policy,’ andmandated all University of California campuses to create implementation procedures. This page and links will provide guidance and links to resources to support our ongoing effort to improve implementation, including our robust Web Access program which can provide consultation and support for website builders and managers, and a similarly robust UC Learning Center series of trainings on building and managing accessible websites

Websites created on third-party, no-code platforms (e.g., Squarespace, Webflow, Weebly, Wix=”SQWXs”) typically have accessibility issues, and perform poorly when audited using Siteimprove’s automated accessibility scanner.

Based on current scanner capabilities and industry benchmarks, your site should target a Siteimprove score that meets UC Berkeley’s minimum scores for WCAG 2.0 AA and other requirements. These benchmarks may change at any time. Automated scanners do not detect all accessibility issues.

Third-party accessibility overlays (some examples include UserWay and accessiBe) are not sufficient to satisfy the policy, and should not be used on UC Berkeley websites.

Beyond no-code website platforms, any website developed without accessibility best practices will also have accessibility barriers, and score poorly on Siteimprove.