1. Siteimprove Implementation Lessons Learned & Benefits Attained
Chris Patterson, UCLA
Lucy Greco, UC Berkeley

2. The Request for Proposals
Initiated by the Electronic Accessibility Committee in 2017
Actually 2 RFPs
Automated testing tool
Training services
Systemwide license paid by Risk Services for the first 3 years
The RFP committee had representation from a majority of the campuses and UCOP.
We went through an extensive process of evaluation including demonstrations and sandboxing before selecting Siteimprove.

3. But keep the bigger goal in mind.
The Ultimate Goal
IS NOT
a perfect score in Siteimprove
perfect compliance with WCAG 2.0 or 508 or other standard IS
better accessibility
WCAG 2.0 Compliance and Siteimprove are good tools to reach toward that goal.
But keep the bigger goal in mind.

4. What is Siteimprove good for?
A good first step toward accessibility
A good birds eye view of accessibility of a site and across the system
An easy way to catalog general errors that can be found via automated testing
A good step in quality assurance
Alerts developers to accessibility issues they had not considered previously
Basic PDF testing
Prioritizing issues – install the Priority JavaScript code in your sites

5. Lessons Learned & Benefits Attained – An illustration
At Berkeley, they found non-distinctive links via Siteimprove’s testing

6. Lessons Learned & Benefits Attained – Another illustration
Should everything be in a landmark?

7. Lessons Learned & Benefits Attained – Another illustration
At UCLA, we found HTML and CSS that will not validate

8. After getting Siteimprove results
Decide about the issues identified
Content is no longer valid or useful – Take it down
Create a schedule for when and how to fix issues
Use the Decisions feature (but sparingly)
Do manual testing – no automated tool can test for all accessibility issues

9. Find a way to start improving – set short-term goals
Fix one issue each week
Reduce your accessibility gap by 50% over 3 months
Other ideas?

10. Decisions - Demonstration

11. Form a Community around Accessibility
Slack – uctech.slack.com
#accessibility
#siteimprove
Seek out your Campus Siteimprove Administrator
Seek out your EAC representative

12. Questions? Thoughts? Suggestions?
should everything be in a landmark?

13. Thank You! Chris Patterson – chris@ucla.edu
Lucy Greco –