Charter overview
This charter establishes the governance framework for digital accessibility at the University of Arizona. It defines organizational structure, roles, responsibilities, and accountability mechanisms to ensure compliance with legal requirements and institutional commitment to access.
Charter scope
This governance structure applies to:
- All university websites and web applications
- Mobile applications
- Learning management systems and educational technology
- Documents and digital content
- Procured third-party technology
- Audio and video content
Governance structure
Digital Accessibility Steering Committee
Purpose: Provide strategic direction, resource allocation, and executive oversight.
Composition:
- Chief Information Officer (Chair)
- Vice Provost for Academic Affairs
- ADA/504 Coordinator
- Director of Disability Resource Center
- University Communications representative
- Faculty Senate representative
- Staff Advisory Council representative
- Student representative (appointed by ASUA)
Meetings: Quarterly
Digital Accessibility Operations Team
Purpose: Implement policies, provide training, and manage day-to-day accessibility operations.
Composition:
- Digital Accessibility Coordinator (Lead)
- Web Accessibility Specialist
- Instructional Technology Accessibility Specialist
- Procurement Accessibility Liaison
- Communications Accessibility Liaison
Meetings: Bi-weekly
Unit Accessibility Liaisons
Purpose: Serve as accessibility points of contact within colleges, departments, and administrative units.
Responsibilities:
- Coordinate accessibility efforts within unit
- Report issues to Operations Team
- Communicate policy updates to unit staff
- Attend quarterly liaison meetings
Roles and responsibilities
Digital Accessibility Coordinator
- Develop and maintain accessibility policies and standards
- Coordinate accessibility training programs
- Manage accessibility auditing and testing
- Track and report on accessibility metrics
- Respond to accessibility complaints and requests
- Advise on procurement accessibility evaluations
Content owners (all staff)
- Create accessible content following guidelines
- Remediate existing inaccessible content
- Report accessibility issues when identified
- Complete required accessibility training
- Respond to accommodation requests
Web developers and IT staff
- Build accessible websites and applications
- Test for accessibility during development
- Follow WCAG 2.1 AA standards
- Fix accessibility bugs as high priority
- Maintain accessibility in third-party integrations
Procurement officers
- Include accessibility requirements in RFPs
- Evaluate vendor VPATs
- Document accessibility exceptions
- Consult with Accessibility Coordinator on technology purchases
Supervisors and managers
- Ensure staff complete accessibility training
- Allocate time for accessibility work
- Include accessibility in job descriptions
- Hold staff accountable for accessible output
Standards and compliance
Technical standards
| Content type | Standard | Level |
|---|---|---|
| Websites | WCAG 2.1 | AA |
| Web applications | WCAG 2.1 | AA |
| Mobile apps | WCAG 2.1 | AA |
| Documents (PDF, Word) | PDF/UA, WCAG 2.1 AA principles | — |
| Video | WCAG 2.1 (captions, audio description) | AA |
| Procured software | VPAT/ACR documenting WCAG 2.1 AA | AA |
Legal compliance framework
- ADA Title II: Requires accessible public services (deadline April 2026)
- Section 504: Requires accessibility for institutions receiving federal funds
- Section 508: Standards for federal electronic and IT
- Arizona State Law: HB 2319 requires accessible government websites
Accountability mechanisms
Training requirements
- All employees: Accessibility awareness training within 90 days of hire
- Content creators: Document accessibility training within 6 months
- Web developers: Technical accessibility training annually
- Supervisors: Accessibility management training within 1 year
Auditing and reporting
- Automated scans: Monthly scanning of university websites
- Manual audits: Annual audit of high-traffic pages and applications
- User testing: Quarterly testing with users of assistive technology
- Metrics reporting: Quarterly accessibility dashboard to Steering Committee
Issue resolution
- Report: Issues reported to accessibility@arizona.edu or web form
- Triage: Operations Team categorizes by severity (24-48 hours)
- Assignment: Issue assigned to responsible unit
- Resolution: Unit remediates within SLA timeframe
- Verification: Operations Team verifies fix
- Escalation: Unresolved issues escalate to Steering Committee
Performance integration
Accessibility responsibilities will be:
- Included in position descriptions for relevant roles
- Part of performance evaluation criteria
- Considered in unit-level assessment
Exception process
When full accessibility cannot be achieved, units may request an exception:
Exception criteria
- Fundamental alteration of program/service
- Undue burden (documented financial analysis required)
- Technical impossibility with current technology
Exception requirements
- Documented business justification
- Description of barriers and affected users
- Proposed equally effective alternative access
- Timeline for remediation if possible
- Approval by unit head and Digital Accessibility Coordinator
Exception review
Exceptions are reviewed annually and must be re-approved to remain in effect.
Charter amendments
This charter may be amended by:
- Proposal from Steering Committee member
- Review by Operations Team
- Approval by majority of Steering Committee
- Annual review and update cycle
Version: 1.0
Effective date: January 1, 2026
Next review: January 2027