Website owner responsibilities

All UC Berkeley websites must meet WCAG 2.0 AA technical standards.  To learn more about WCAG 2.0 AA compliance please visit the Web accessibility training page on this website. In order to comply WCAG 2.0 level AA standards, campus site owners must:

Choose a platform that is capable of creating accessible content.

  • Open Berkeley is a fully-managed website solution that relies on accessible design and development practices, and offers tools for website builders that support creating accessible content.
  • For any other platforms (e.g., WordPress, Drupal, Expression Engine, Django, Rails, Gatsby, React, custom-built, etc.), your department must have expertise to determine your chosen platform's accessibility.  Please refer to the Manual accessibility testing template.
  • If using managed site-building services or third-party developers, consult with the provider on how they will work with you in a timely manner to address accessibility issues specific to your site. Accessibility should always be included in any contract agreement with third-party developers and agencies. The vendor should have completed the Accessibility Questionnaire as part of the contract.

Use that platform’s tools correctly to create accessible content.

  • Review the Checklist page and Concepts section of this website.  
  • Enroll the site in Siteimprove.
  • Use both manual testing (checklist) and automated testing (Siteimprove)  for a full assessment and understanding of your website's accessibility.
  • Remediate your WCAG 2.0 AA failures on your website.

Manage the underlying source code to fix discovered issues.

  • If your website is built on Open Berkeley, this is included in the service.
  • If your website is using another platform/framework or is custom-built, you are responsible for understanding and managing the underlying source code.

Websites on the berkeley.edu domain MAY NOT use third-party accessibility overlays. Some examples include UserWay and accessiBe. Learn why overlays are so challenging by reading Overlaying Overconfidence - My Lived Experience with Overlays.

Websites on the berkeley.edu domain MAY NOT use the following third-party no-code hosting services:

  • Softr
  • Squarespace
  • Webflow
  • Weebly
  • Wix

Accurately caption all video content.

On your website footer, include a link to the Report a Website Access Issue page.

  • Refer to the footer of this web page for Accessibility, Nondiscrimination and Privacy links.