Real examples of accessibility improvements across campus.
Learning from each other
These case studies showcase how departments and individuals across the University of Arizona have improved accessibility. Each story includes the challenge faced, solutions implemented, measurable results, and lessons learned.
Have a success story to share? Email accessibility@arizona.edu — we'd love to feature your work!
University Libraries Website Redesign
The Challenge
The UA Libraries website served over 50,000 unique visitors monthly but had accumulated accessibility debt over 15 years of incremental updates. An automated scan revealed 2,400+ accessibility errors, and user feedback indicated screen reader users struggled to find resources.
Before & After
Results
Timeline
Comprehensive audit with axe, manual keyboard testing, and screen reader evaluation with NVDA and VoiceOver.
Prioritized fixes by severity and user impact. Fixed critical keyboard traps and form issues first.
Redesigned navigation structure and implemented skip links. User testing with DRC students.
Final testing, documentation, and team training on maintaining accessibility.
"The accessibility improvements didn't just help users with disabilities—our analytics showed everyone benefited from the clearer navigation and faster page loads."
💡 Key Lessons
- Automated testing catches ~30% of issues; manual testing is essential
- User testing with actual assistive technology users revealed issues tools missed
- Accessibility improvements often improve SEO and mobile experience
- Building accessibility into the CMS template prevented future regressions
HR Forms Accessibility Initiative
The Challenge
HR managed over 200 PDF forms that employees needed for benefits, leave, and employment processes. Most were created years ago as flat PDFs without form fields or proper tagging, making them unusable for employees with disabilities.
Before & After
Process
Audited all forms; identified 50 high-priority forms used by 80% of employees.
Recreated forms in Word with proper structure, then exported to tagged fillable PDFs.
Tested all forms with Adobe Acrobat's accessibility checker and manual screen reader testing.
Trained HR staff on maintaining accessible forms and established QA process.
💡 Key Lessons
- Recreating in Word is often faster than remediating bad PDFs
- Keep source files (Word/InDesign) for future updates
- Interactive PDFs benefit everyone, not just AT users
- Clear form instructions reduce errors for all users
Chemistry Department Course Materials Overhaul
The Challenge
The Chemistry department discovered that many course PDFs were scanned images without OCR, lecture slides had no alt text for complex molecular diagrams, and videos lacked captions. A student accommodation request highlighted the scope of the problem.
Before & After
Approach
The department partnered with IT and the DRC to develop a sustainable workflow:
- Prioritization: Started with highest-enrollment courses (CHEM 151, 152)
- Templates: Created accessible PowerPoint templates with placeholder for diagram descriptions
- Training: Faculty workshop on alt text for scientific content
- Process: Built captioning into Panopto recording workflow
"Writing descriptions for molecular structures actually made me think more carefully about what I wanted students to understand. It improved my teaching."
💡 Key Lessons
- Start with high-impact courses; don't try to fix everything at once
- Student workers can be trained to help with PDF remediation
- Building accessibility into creation is faster than remediation
- Faculty champions make adoption much easier
Student Information System Accessibility Requirements
The Challenge
During procurement of a new student information system module, the initial vendor VPAT claimed "Supports" for most criteria but testing revealed significant issues with keyboard navigation and screen reader compatibility in critical enrollment workflows.
Our Approach
- Due diligence: Requested live demo instead of relying on VPAT alone
- Testing: Conducted independent testing with JAWS and keyboard-only
- Documentation: Created detailed accessibility requirements as RFP criteria
- Contract: Added accessibility conformance clause with remediation timeline
Results
Working with the vendor, we achieved:
"The accessibility testing we did during procurement saved us from a much bigger problem after launch. Students would have been locked out of enrollment."
💡 Key Lessons
- Never rely solely on vendor VPATs—conduct your own testing
- Include accessibility requirements in RFPs from the start
- Contract language gives you leverage for fixes
- Early engagement with vendors is usually well-received
Share your story
Has your department made accessibility improvements you're proud of? We want to hear about it! Success stories help inspire and guide others across campus.
Submit a story
Share your accessibility wins, challenges overcome, and lessons learned.
Get featured
We can help you document your work and share it with the campus community.