View the latest updates and emergency notifications on the COVID-19 News & Information website.
Web Services

2018–19 Campus Web Accessibility Plan

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 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)
  •   Blackboard content
  •   Library websites and systems

System Background

Web Services provides the framework (template) for all subsites, referred to as the "Campus Web." This framework is built within Cascade web content management system (WCMS) and is designed to provide a unified brand and user experience for official University department sites.

The content within each site is controlled by a department/office website owner and updated by site maintainers designated by the site owner. Each site maintainer is required to attend Cascade training that includes accessibility and sign a user agreement before being granted access to the WCMS.

Web Services is currently (June 2017–spring 2018) migrating campus websites into a new mobile-responsive framework ( Campus Web 3.0). We are using this migration as an accessibility remediation checkpoint.

System Status


Current inventory of existing www websites and associated digital content, including framework, response, redirect status, maintainers, accessibility score, 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% 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


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

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

Remediation Strategy: Use Campus Web 3.0 Site Migration as an Accessibility Remediation Checkpoint

  • Focus Web Services resources on migration into the more accessible framework. (Done: throughout migration)
  • Require all site maintainers to remediate PDFs and caption videos (through the Office of Accessible Technology and Services) prior to site migration. (Done: throughout migration)
  • Analyze site elements 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. (Done: throughout migration)
  • Create group in Siteimprove that consists of all 3.0 sites (adding sites as we migrate)—focus content remediation efforts here (Done: 2018)

2018–19 Goals

  • Continue migrating 2.0 sites into 3.0 framework, eliminating outdated sites/content and remediating all digital content in process (Done: summer 2019)
  • Begin contacting owners of non-Cascade sites and archiving, migrating, or moving them to another system (ex., student clubs to OrgSync, personal sites to YourWeb) (More than 100 www sites done by summer 2019.)
  • Trial Ally for Web to better scan digital content
  • Trial ReadSpeaker to provide on-page text-to-speech and foreign language translation (Done: spring 2018. Did not meet our needs.)
  • Expand manual testing to more sites (identified by CSU as priorities for 2018 reporting) and collaborate with the Office of Accessible Technology and Services (OATS) to add screen-reader testing (Done: spring 2019)

2019–20 Goals

2. New Websites and Digital Content

Process for new websites:

  • Use Cascade framework based on Campus Web UI library of accessible elements and styles
  • Keep Campus Web UI current using formalized versioning system
  • Follow Web Services development standards

Tools used during design and development: online Colour Contrast Analyser, Deque, Siteimprove browser extension, Google Lighthouse, WAVE.

2018–19 Goals

  • Create release checklist for pre-production testing of UI changes (in progress, pushed to 2019-20)
  • Automate accessibility checks for front-end development whenever changes are pushed to GitHub (in progress, pushed to 2019–20)
  • Begin visioning a 4.0 framework centered around universal design principles (Started: fall 2018, starting with home page in 2019–20)

3. Ongoing Monitoring

  • Continue to check selected pages manually (every 6 months) and all subsites automatically (every month)
  • Focus internal resources on remediation of 3.0 group, keeping the Siteimprove weighted accessibility score of those sites above 90/100
  • Send monthly Siteimprove content accessibility reports to identified site owners and maintainers
  • Ask site maintainers to remediate PDFs and caption videos (through OATS) prior to adding to site (see Site Maintainers Agreement)
  • Require update clients to remediate content before Web Services upload
  • Use one quarter-time student assistant position to remediate issues introduced by content maintainers and do visual checks through Siteimprove
  • Include Siteimprove plug-in with Cascade WCMS editing interface
  • Cascade WCMS automated accessibility checks
    • Other automated features include enforcing file naming conventions, automatically add file extensions to links to media file, and building menu links with descriptive ARIA labels.

2018–19 Goals

  • Explore other ways to automate accessibility in Cascade (Done: fall 2018. See "Automating Accessibility."
  • Adapt monitoring process to WCAG 2.1 (In progress: Siteimprove changes, additional manual checkpoints)
  • Make website status reports publicly available via a link from CSU, Chico’s ATI site, sortable by campus department/college/division (In progress: working out sorting by department, identifying owners)

4. Exemptions & Alternatives

Documented non-compliant websites, web applications, and digital content must be delivered in an equally effective alternate format and granted an exemption. — CSU Memorandum AA-2013-03(opens in new window).

5. Training

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

2018–19 Goals

  • All Web Services technical staff complete Siteimprove Academy developer training (In progress, along with WCAG 2.1 training)
  • Leverage new campus training system to require accessibility basics training as a Cascade training prerequisite (Pushed to 2019–20)

2019–20 Goals

  • Leverage new campus training system to require and automatically assign accessibility training to all campus developers

6. Communication

  • “Report an accessibility issue” link in standard campus footer—directs to the 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
  • Accessible Content Service Catalog in the TeamDynamix ticketing system allows campus community to request site scans, content remediation assistance, captioning support, and more
  • Accessibility section included in University Style Guide increases awareness among campus communicators

2018–19 Goals

  • Create a Web Services newsletter for site maintainers that informs them of WCMS changes and includes accessibility reminders (Done: see "News")
  • Release at least one accessibility-related campus announcement per semester (Done: through "News")
  • Hold a site maintainers workshop that teaches attendees how to meet audience needs by gathering data and using best practices in accessibility, user experience, and web content (Done: summer 2019 Content Maintainers Workshop)

7. Administrative

  • Revise and publish Campus Web Accessibility Plan every summer

2018–19 Goals

  • Encourage campus adoption of web branding and accessibility policy that allows Web Services to enforce best practices (Web governance plan in progress)

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

  • Campus Web UI: a library of CSS web styles available to campus app developers and vendors
  • Manual and automated scans: provided by Web Services to other campus units and auxiliaries
  • Siteimprove access for other campus units and auxiliaries upon request
  • Web Services participation in ATI working groups and the Disability Access and Compliance Committee
  • ATI reporting
  • Inventory of non-Cascade campus websites
  • Accessibility consulting to other units (such as 2018-19 consultations with Athletics during a site redesign and with IRES units on Salesforce digital communications tools)

2018–19 Goals

  • Organize manual testing training sessions (In progress: delayed due to campus focus on CAARP plan)
  • Email personalized reports on web health to chairs, deans, VPs (In progress: delayed due to campus focus on CAARP plan)
  • Create IRES technical accessibility group (In progress: delayed due to campus focus on CAARP plan)

2019–20 Goals

  • Participate in campus launch of universal access logo and brand
  • Help campus implement central hosting solution for non-Cascade websites

Previous Plans