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

2017-18 Campus Web Accessibility Plan

NOTE: The 2018–19 accessibility plan is now available. This plan is for reference only. 

CMT Web Services is committed to providing everyone in the CSU, Chico community equal access to participate in 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.0 AA).

System Background

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

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 and sign a user agreement before being granted access to the WCMS.

Web Services is currently (June 2017–December 2018) migrating campus web sites into a new, more accessible and mobile-responsive framework (Campus Web 3.0). We are using this migration as an accessibility remediation checkpoint.

Campus Web Accessibility Plan

Step 1: Notice of Accommodation

  • Create a "Report an Accessibility Issue" link for the campus footer. This leads to a webpage owned by the Accessibility Resource Center, which includes a link to a reporting form that will auto-generate a TeamDynamix ticket. This allows users to choose between multiple reporting mechanisms. (Done: 2017)
    • Note: The footer in the old web templates does not automatically update, so any changes roll out slowly as site maintainers publish their pages live.
  • Revision: Change footer link so it goes to the Web Accessibility section of the campus ATI site,(opens in new window) which includes our desired level of compliance, links to resources for compliance assistance, and a link to the form for reporting web accessibility issues. (Done: December 2017)

Step 2: Inventory Campus Web and Determine Accessibility Baseline

  • Roll out Siteimprove scanning software across the campus web to inventory all live sites and associated media files. (Done: May 2017)
    • May 12, 2017 Baseline Inventory (Siteimprove)
      • Pages: 27,873
      • Links: 120,746
      • Documents: 17,291
      • Media files: 34,902
      • JavaScript files: 351
      • CSS: 753
      • Email addresses: 3,849
      • Phone numbers: 2,563
      • Social security numbers: 1
      • Meta tags: 47
    • June 19, 2017 Baseline Campus Web Conformance to 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
    • March 15, 2018 Inventory (Siteimprove)
      • Pages: 12,962
      • Links: 67,903
      • Documents: 12,918
      • Media files: 16,947
      • JavaScript files: 276
      • CSS: 524
      • Email addresses: 3,113
      • Phone numbers: 2,190
      • Social security numbers: 0
      • Meta tags: 38
    • March 15, 2018 Campus Web Conformance to WCAG 2.0 (Siteimprove)
      • 91.5% Siteimprove weighted accessibility score
      • 75 A issues to fix or check
      • 4 AA issues to fix or check
      • 23 A and AA issue types with no errors
  • Create master list of all sites (published and unpublished) located on the campus web server, including fields for site type, WCMS vs. non-WCMS, site owner and maintainer, migration status, and associated department and division. (Done: Fall 2017)
    • Include analytics and Siteimprove accessibility score information in master list. (Planned: Spring 2018)

Step 3: Train Staff

  • Require all 5 Web Services staff and 2 student assistants to take Siteimprove Academy(opens in new window) courses in web accessibility.
    • General Digital Accessibility Basics (Done: September 2017)
    • Content accessibility and developer tips (pending course releases by Siteimprove)

Step 4: Clean Up Campus Web 3.0 Site Framework

  • Use data from Siteimprove automated scans and manual scans (following the CSU-suggested criteria) to make changes to the 3.0 framework HTML and CSS. (Done: October 2017)
  • Automate accessibility best practices
    • Automatically add file extensions to links to media file (Done: September 2017)
    • Implement Siteimprove plug-in in Cascade interface (Done: March 2017)
  • Create an organized library of CSS web styles (CSWeb 3.2) that can be rolled out across Campus Web 3.0 and well as shared with vendors and campus developers managing University sites outside of the domain. This includes CSS integrations that improve screen reader compatibility. (Done: March 2018)

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

  • Focus Web Services resources on migration into the more accessible framework.
  • Require all site maintainers to remediate PDFs and caption videos (through the Office of Accessible Technology and Services) prior to site 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.
  • Create group in Siteimprove that consists of all 3.0 sites (adding sites as we migrate)—focus content remediation efforts here
    • Progress as of Nov. 11, 2017 (30% of sites migrated)
      • 3.0 Sites
        • 98% Siteimprove weighted accessibility score
        • 29 issue types to do
      • 2.0 Sites
        • 86% Siteimprove weighted accessibility score
        • 71 issue types to do
    • Progress as of March 15, 2018 (40% of sites migrated)
      • 3.0 Sites
        • 98.2 Siteimprove weighted accessibility score
        • 29 issues types to do
      • 2.0 Sites
        • 89.6% Siteimprove weighted accessibility score
        • 69 issue types to do
  • Create an "exemptions" policy for the Campus Web that identifies archival sites that are not critical to providing services and will be remediated or archived after the main site migrations (Done: October 2017)

Step 6: Create Procedures/Best Practices for Site Maintenance and New Content

  • Create internal policy that Web Services will not post inaccessible content on the web on behalf of clients—requiring them to seek video captioning and PDF remediation help through the Office of Accessible Technology first. Post this requirement on the web in the Content Update Service information page. (Done: June 2017)
  • Create a Campus Web Site-Maintainers Agreement(opens in new window) that clarifies site maintainer responsibility for accessible content, post on Web Services site and present at Cascade training (Done: August 2017)
  • Require embedded videos posted by Web Services on behalf of clients to be from Kaltura/MediaSpace (Done: October 2017)
  • Continue to check sites manually (every 6 months) and automatically (every month)
    • Focus internal resources on remediation of 3.0 group, keeping the Siteimprove weighted accessibility of those sites above 90% (continual effort)
    • Make reports publically available on CSU, Chico’s ATI site (Planned: Spring 2018)
    • Send monthly Siteimprove accessibility reports to site owners and maintainers (Done: June 2017)
    • Create a walk-in lab for site maintainers to get hands-on assistance in site remediation of issues identified in their reports (Done: November 2017)

Step 7: Enhance Education, Awareness, and Training Across Campus

  • Add accessibility basics and introduction to Siteimprove to Cascade 3.0 training (Done: August 2017)
  • Include accessibility section in University Style Guide(opens in new window) to increase awareness among campus communicators (Done: January 2018)
  • Build Web Accessibility Knowledge Base of content accessibility tutorials for site maintainers (Done: October 2017)
    • Additional content planned to help site maintainers remediate content issues identified in Siteimprove automated scans (continual effort)
  • Build Accessible Content Service Catalog for campus community to request site scans, content remediation assistance, captioning support, and more (Done: October 2017)
  • Send updates on web accessibility through the campus announcements system every semester (continual effort)

2018–19 Plans

Increase collaboration with other campus units creating websites and web apps outside of the campus web

  • Share CSWeb 3.2 web style library with campus developers and vendors
  • Organize manual testing training sessions
  • Email personalized reports on web health to chairs, deans, VPs

Integrate Siteimprove with Ally (piloted for LMS content scanning in fall 2017) and scanning of web apps to create overall picture of CSU, Chico web accessibility (including documents and media files within web environment)

Require separate course in accessibility for site maintainers

Remediate exemptions