View the latest updates and emergency notifications on the COVID-19 News & Information website.
Accessibility Resource Center

The ADA and Reasonable Accommodation For Employees With Disabilities

CMT Web Services is committed to providing everyone in the CSU, Chico community equal access to University programs, services, and activities. We are working hard to make our websites (those in the domain) accessible to all users. This means a goal of meeting the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG 2.1 AA).


The Campus Web Accessibility Plan applies only to websites and web content contained within the URLs and

The Web Accessibility Plan does not apply to other sites, including the following:

  • Web-based applications including University Catalog, Directory, or Class Schedule
  • Personal faculty and student websites in YourWeb or MyWeb
  • Affiliate or auxiliary websites regardless of domain (ex., University Public Events, Athletics, RCE)
  • LMS content or other instructional materials
  • Meriam Library websites and other digital properties

System Background

Web Services provides the framework (template) for all subsites, referred to in this plan as the "Campus Web." This framework is built within the Cascade web content management system (WCMS) and is designed to provide a unified brand and user experience in websites conducting official university business.

The content within each site is controlled by a website owner (appropriate administrator) and updated by site maintainers designated by the site owner. Each site maintainer is required to attend Cascade training that includes accessibility tips, best practices, and resources and sign a user agreement before being granted access to the WCMS.

In 2018–19, Web Services completed a migration of campus websites into a mobile-responsive framework (Campus Web 3.0, using this migration as a remediation checkpoint and dramatically improving the overall accessibility of the Campus Web. Several sites in the Campus Web remain noncompliant: Advanced Laboratory for Visual Anthropology, Chico Performances, College of Business

System Status


Current inventory of existing www websites (campus authentication required) and associated digital content, including maintainers, division, accessibility score, QA and SEO scores, PDF accessibility scores, page views, and last modified date.

Historical Data

June 2017 Status: Pre-migration & Pre-Siteimprove Baseline

Inventory (Siteimprove)
  • Pages: 18,166
  • Links: 93,464
  • Documents: 15,980
  • Media files: 24,536
  • JavaScript files: 309
  • CSS: 662
  • Meta tags: 44
Automated Check Against WCAG 2.0 (Siteimprove)
  • 86 A issues to fix or check
  • 7 AA issues to fix or check
  • 23 A and AA issue types with no errors

August 2018 Status: Midway Through 3.0 Migration

  • Pages: 13,974
  • Links: 60,813
  • Documents: 10,953
  • Media files: 17,302
  • JavaScript files: 380
  • CSS: 530
  • Meta tags: 35
Automated Check Against WCAG 2.1 (Siteimprove)
  • 91.5/100 Siteimprove weighted accessibility score
  • 73 A issues to fix or check (48,313 occurrences)
  • 4 AA issues to fix or check (1,452 occurrences)
  • 39 A and AA issue types with no errors

October 2019 Status: 3.0 Migration complete


  • Pƒages: 12,120
  • Lƒinks: 48,425
  • Dƒocuments: 7,402
  • Mƒedia files: 12,854
  • JƒavaScript files: 260
  • CƒSS: 282
  • Mƒeta tags: 13

Aƒutomated Check Against WCAG 2.1 (Siteimprove)

  • 8ƒ7.6/100 Siteimprove weighted accessibility score for 3.0 sites only (87.6 for all
  • 5ƒ6 A issues to fix or check (91,544 occurrences)
  • 3ƒ AA issues to fix or check (596 occurrences)
  • 4ƒ2 A and AA issue types with no errors


This plan was created to align with the structure of the CSU Accessible Technology Initiative (ATI). The CSU ATI coded memo can be found at

CSU ATI Web Accessibility goals fall into 7 main categories:

  • Web Accessibility Evaluation Process: Identify and repair or replace inaccessible websites, web applications, and digital content.
  • New Website/Web Application and Digital Content Design and Development Process: New website/web application and digital content development complies with all Section 508 accessibility guidelines.
  • Ongoing Monitoring Process: Updating and maintenance of websites/web applications and digital content comply with Section 508 Accessibility Standards.
  • Exemptions and Alternatives Process: Documented noncompliant websites, web applications and digital content must be delivered in an equally effective alternate format and granted an exemption.
  • Training Process: Professional development training has incorporated Section 508 accessibility guidelines into website and web applications development and digital content preparation.
  • Communication Process: The campus community is aware of Section 508 guidelines to make web-based information available to everyone (students, staff, faculty & the general public) regardless of disability.
  • Administrative Process: Campus governance entities are aware of and kept informed about web accessibility.

1. Web Accessibility Evaluation Process

Responsible body: CMT Web Services

Inventory:Dynamic report pulling data from server, Siteimprove, Cascade

Automated testing: Monthly testing of entire domain using Siteimprove

Manual testing: Twice yearly, selected pages, using CSU testing framework and additional criteria including a screen reader test

Distribution of results: Automated reports to 3.0 site owners/maintainers via Siteimprove; manual testing results emailed to individual stakeholders. Users of the WCMS see a Siteimprove integration within Cascade that informs them of accessibility scan results.

Compliance assistance:   Accessible Content ticket category and Website Design and Support Knowledge Base within the campus service catalog (Siteimprove reports, the Web Services website, and the University Communicators Guide all contain links to relevant help tickets)

Digital content: Basic scan of PDFs and semi-automated caption check via Siteimprove. Fƒull monthly scan of documents using Ally for Web.

Documentation: Historical data of automated tests and manual tests archived in Siteimprove and Box, respectively

3.0 Migration Wrap-Up: Aƒll www campus sites (except two outliers) now

  • Aƒre responsive
  • Uƒse a template with a baseline acceptable level of accessibility
  • Hƒave a standard accessibility reporting link in the campus footer
  • Aƒre in the Cascade WCMS with Siteimprove integration
  • Hƒave site maintainers trained in accessibility
  • Aƒre current (non-archival)
  • Aƒre doing University business

2019–20 Maintenance Strategy: Increase accessibility baseline from 90/100 to 95/100 Siteimprove score.

  • Cƒontinue to scan, revise, and adjust 3.0 framework based on testing results.
  • Lƒimit the introduction of site maintainer errors
  • Uƒse Web Services student assistants to visually check and fix errors identified in Siteimprove
  • Cƒontinue contacting owners of non-Cascade sites and archiving, migrating, or moving them to another system (ex., student clubs to OrgSync, personal sites to YourWeb)
  • Dƒo a post-migration assessment of Campus Web

2019–20 Remediation Strategy: Focus on PDFs and web elements.

  • Aƒnalyze site elements, document best practices, and provide alternatives for accessibility issues such as tables used for layout, PDFs used to present information better suited to a web page, poorly written alt text, etc.
  • Iƒncrease Ally for Web PDF score to 70% on campus subsites by partnering with OATS on remediation.
  • Eƒxplore the use of online forms instead of PDFs for simple information gathering.

2. New Websites and Digital Content

Process for new websites:

  • Uƒse Cascade framework based on Chico State Web Design System library of accessible elements and styles
  • Nƒew websites are requested by site owner and approved by Web Content Review Committee
  • Kƒeep Chico State Web Design System current using formalized versioning system
  • Follow Web Services development standards

Tools used during design and development: online Colour Contrast Analyser, Siteimprove browser extension, Google Lighthouse, WAVEBƒutton Contrast Checker

2019–20 Goals

  • Cƒreate release checklist for pre-production testing of framework changes
  • Sƒchedule and document process for accessibility checking and remediation of front-end framework and associated elements
  • Gƒet campus consensus on workflow that limits site maintainer ability to upload inaccessible PDFs
  • Sƒtart gathering data to inform development of a 4.0 framework centered around universal design principles

3. Ongoing Monitoring

  • Cƒontinue to check selected pages manually (every 6 months) and all subsites automatically (every month)
  • Cƒontinue to check web content (PDFs) monthly
  • Rƒequire update clients ƒto remediate content before Web Services upload
  • Uƒse one quarter-time student assistant position to remediate issues introduced by content maintainers and do visual checks through Siteimprove
  • Sƒiteimprove plug-in integrated into Cascade WCMS editing interface
  • Cƒascade WCMS automated accessibility ƒchecks
    • Oƒther automated features include enforcing file naming conventions, automatically add file extensions to links to media file, and building menu links with descriptive ARIA labels.

2019–20 Goals

  • Eƒmbed OATS student in Web Services part time to assist with screen-reader testing of campus sites
  • Tƒest and compare various automated testing tools to validate our results
  • Cƒontinue to adapt monitoring process to WCAG 2.1

4. Exemptions & Alternatives

See Campus Web Exemptions

5. Training

  • Aƒccessibility basics and introduction to Siteimprove covered in Cascade 3.0 training ƒfor site maintainers, offered monthly. This training is required for Cascade access.
  • Aƒll Web Services staff and student assistants have completed “General Digital Accessibility Basics” Siteimprove Academy course
  • Wƒalk-in lab available for site maintainers to get hands-on assistance in site remediation
  • Aƒn Accessibility Assistance page ƒfor Campus Web site maintainers
  • Aƒccessibility section included in University Style Guide ƒto increase awareness among campus communicators, including best practices for digital content
  • Wƒeb Accessibility Knowledge Base ƒof content accessibility tutorials is regularly updated to help site maintainers with content issues identified in Siteimprove automated scans

2019–20 Goals

  • Aƒll Web Services technical staff complete Siteimprove Academy developer training or other training

2020–21 Goals

  • Lƒeverage new campus training system to require accessibility basics training as a Cascade training prerequisite
  • Lƒeverage new campus training system to require and automatically assign accessibility training to all campus developers

6. Communication

  • Cƒontinue to send monthly Siteimprove content accessibility reports to identified site owners and maintainers
  • &ƒ#8220;Report an accessibility issue” link in standard campus footer—directs to tƒhe Web Accessibility section of the campus ATI site, ƒwhich includes our desired level of compliance, links to resources for compliance assistance, and a link to the form for reporting web accessibility issues
  • Aƒccessible Content Service Catalog ƒin the TeamDynamix ticketing system allows campus community to request site scans, content remediation assistance, captioning support, and more
  • Aƒccessibility section included in University Style Guide ƒincreases awareness among campus communicators

2019–20 Goals

  • Mƒake website status reports publicly available via a link from CSU, Chico’s ATI site, sortable by campus department/college/division
  • Dƒetermine site owners by using departmental hierarchy
  • Cƒreate comprehensive report for site owners that includes inventory, site health, document health, and maintainers; send quarterly
  • Mƒore regularly send Web Services newsletter for site maintainers that informs them of WCMS changes and includes accessibility reminders
  • Rƒelease at least one accessibility-related campus announcement per semester

7. Administrative

  • Revise and publish Campus Web Accessibility Plan yearly

2019–20 Goals

  • Aƒssist campus with development of Web Governance Policy

Outreach to Other Campus Areas

While this plan covers the Campus Web only, Web Services is committed to fostering collaboration with other campus units creating websites and web apps. Our efforts to help other units meet ATI standards include

  • Cƒampus Web UI: a library of CSS web styles available to campus app developers and vendors
  • Mƒanual and automated scans: provided by Web Services to other campus units and auxiliaries
  • Sƒiteimprove access for other campus units and auxiliaries upon request
  • Wƒeb Services participation in ATI working groups and the Disability Access and Compliance Committee
  • Cƒontribution to annual ATI report, President’s Report, and Web Accessibility Report required by the CSU
  • Aƒccessibility consulting to other units for websites, web apps, and other digital projects
  • Sƒupport the CSU, Chico CAARP plan
  • Cƒreate digital branding consultation service offering that includes accessibility

Previous Plans