Upcoming Event
UCLA’s digital accessibility requirements come from three converging sources:
- UC IMT-1300 — IT Accessibility Policy The University of California’s systemwide policy requires all UC locations to implement an IT Accessibility Policy Program (ITAPP) and bring covered IT into compliance with WCAG 2.1 AA. UCLA’s compliance date under this policy is April 24, 2026.
- ADA Title II Federal regulations under the Americans with Disabilities Act require state and local government entities, including public universities, to make their digital content accessible. The federal compliance deadline has been extended to April 26, 2027, but UCLA’s UC policy obligations remain in effect on April 24, 2026. Content created after April 24, 2026 must meet WCAG 2.1 AA regardless of the federal deadline extension.
- Section 504 of the Rehabilitation Act HHS has issued an Interim Final Rule extending the Section 504 web and mobile accessibility compliance deadline by one year, to May 11, 2027 for institutions with 15 or more employees.
- WCAG 2.1 AA The Web Content Accessibility Guidelines are the technical standard UCLA must meet. They cover web pages, documents, applications, multimedia, and interactive tools.
Federal Accessibility Deadlines Have Been Extended
Two federal deadlines for digital accessibility compliance have been extended. Here's what's changed (and what hasn't) for UCLA.
What changed
The U.S. Department of Justice (DOJ) previously extended the ADA Title II compliance deadline to April 26, 2027. On May 7, 2026, the U.S. Department of Health and Human Services (HHS) Office for Civil Rights issued an Interim Final Rule extending the Section 504 compliance deadline to May 11, 2027 for recipients with 15 or more employees.
What hasn't changed
The substantive standard (WCAG 2.1 AA) has not changed. UCLA's obligation to ensure that people with disabilities can access our digital content remains in effect.
Content exceptions tied to a specific date (including archived web content, preexisting conventional electronic documents, and preexisting social media posts), continue to use April 24, 2026 as the cutoff date. Any new digital content created after April 24, 2026, must meet WCAG 2.1 AA.
IMT-1300, the UC systemwide IT Accessibility Policy, has not been revised. UCLA's ITAPP programs and the work of our Action Response Teams continue as planned.
What Is Covered
- Websites and web applications, including content behind a login
- Documents (PDFs, Word files, presentations, spreadsheets) created or posted after April 24, 2026
- Course materials in Bruin Learn and other learning platforms
- Multimedia (video, audio, interactive content)
- Procurement — software, platforms, and tools UCLA purchases or licenses
- Third-party tools and embeds used to deliver UCLA services
What is Not Covered Under the UC Policy’s Accessibility Standard:
- Archived content (content preserved for historical reference, with no ongoing use)
- Electronic documents posted before April 24, 2026, that are not currently used to access UCLA services, programs, or activities
- Social media posts published before April 24, 2026
- Individualized, password-protected documents about a specific person
Note: Even exempt content may still be subject to individual accommodation requests.
When making a specific piece of content accessible is not technically feasible or creates an undue burden, UCLA has a formal exception process. Exceptions require institutional approval and must include an Equally Effective Alternate Access Plan (EEAAP) that describes how affected users can still access the content or service.
Exceptions are not permanent waivers: they are documented, time-limited, and subject to review.
Digital accessibility is a shared responsibility across campus. Everyone who creates, publishes, purchases, or manages digital content has a role.
The UCLA Digital Accessibility Steering Committee, co-chaired by Lucy Avetisyan (AVC & CIO) and Dr. Ralina Joseph (Vice Provost for Inclusive Excellence), provides strategic direction and institutional oversight.
Six Action Teams (ARTs) are leading domain-specific work across web content, applications, academic and course content, health, research, and procurement.
Learn more about the Steering Committee and governance structure
| Requirement | Deadline |
|---|---|
| UC IMT-1300 (ITAPP implementation) | April 24, 2026 |
| Section 504 digital access compliance | May 11, 2027 |
| ADA Title II digital access compliance | April 26, 2027 |
| All new digital content must meet WCAG 2.1 AA | Effective April 24, 2026 |
The U.S. Department of Justice (DOJ) previously extended the ADA Title II compliance deadline to April 26, 2027. On May 7, 2026, the U.S. Department of Health and Human Services (HHS) Office for Civil Rights issued an Interim Final Rule extending the Section 504 compliance deadline to May 11, 2027 for recipients with 15 or more employees.
What hasn't changed
The substantive standard (WCAG 2.1 AA) has not changed. UCLA's obligation to ensure that people with disabilities can access our digital content remains in effect.
Content exceptions tied to a specific date (including archived web content, preexisting conventional electronic documents, and preexisting social media posts), continue to use April 24, 2026 as the cutoff date. Any new digital content created after April 24, 2026, must meet WCAG 2.1 AA.
IMT-1300, the UC systemwide IT Accessibility Policy, has not been revised. UCLA's ITAPP programs and the work of our Action Response Teams continue as planned.
What to Do
If you own or manage a UCLA website, you are responsible for ensuring it meets WCAG 2.1 AA.
Start by scanning your site to understand where issues exist. SiteImprove is available to all UCLA units and provides automated accessibility scanning with prioritized issue tracking.
Common issues to address first: missing alt text, improper heading structure, insufficient color contrast, unlabeled form fields, and inaccessible PDFs linked from your pages.
Documents posted or created after April 24, 2026 must meet WCAG 2.1 AA. This includes PDFs, Word files, PowerPoint presentations, and spreadsheets.
The best approach is to create accessibly from the source — use proper heading styles, add alt text to images, and ensure reading order before you export to PDF. Retrofitting inaccessible documents is significantly more time-consuming.
For existing high-use documents posted before April 24, 2026 that are actively used to access UCLA services or programs, remediation should be prioritized.
If you own or manage a campus application — including enterprise systems, student or faculty portals, and administrative tools — you are responsible for ensuring it meets WCAG 2.1 AA.
This includes both in-house developed applications and vendor-supplied platforms. For vendor tools, accessibility requirements should be part of procurement review and contract language.
Technology purchases at UCLA must meet accessibility requirements. Before acquiring software, platforms, or tools — including free or low-cost products and click-through agreements — procurement leads should verify vendor accessibility claims and request Voluntary Product Accessibility Templates (VPATs) or Accessibility Conformance Reports (ACRs).
Faculty, instructors, and TAs are responsible for ensuring that course materials — including documents, slides, videos, and third-party tools used in Bruin Learn — are accessible to all students.
The Teaching & Learning Center and the Disabilities & Computing Program offer resources and consultations to help you get started. Ally, integrated into Bruin Learn, provides per-file accessibility scores and guidance for common document types.
When accessibility compliance is not achievable for a specific item, UCLA’s exception process allows units to document the barrier, the reason for the exception, and the alternate access plan that ensures affected users are not excluded.
Exceptions must be approved by the designated institutional authority, are time-limited, and require an Equally Effective Alternate Access Plan (EEAAP).
Remediating PDFs with Adobe Acrobat Pro
Adobe Acrobat Pro is available free to UCLA faculty and staff through Adobe Creative Cloud. It includes an Accessibility Checker that identifies issues and an integrated remediation workflow for fixing tag structure, reading order, alt text, form fields, and other common barriers. If you have a backlog of PDFs that need attention, Acrobat Pro is your primary tool.
Accessibility Remediation Tools
Looking for other tools? UCLA supports a range of accessibility scanning, review, and remediation tools for websites, applications, and documents.
Get Help
UCLA offers training through several campus partners. Whether you’re new to accessibility or looking to go deeper, there are options for every role.
Disabilities & Computing Program (DCP) Ongoing workshops on web accessibility, document accessibility, PDF remediation, and SiteImprove. Open to all UCLA staff and faculty.
Teaching & Learning Center Resources and consultations for instructors focused on making course content accessible.
Bruin Learn Center of Excellence Support for instructors using Bruin Learn tools, including Ally.
If you are seeking an accommodation and/or support related to a disability, please reach out to one of the following offices:
- For students, please contact contact the Center for Accessible Education (“CAE”) at (310) 825-1501.
- For university staff, employees may submit the IRM Request for Reasonable Accommodation Form via email to rtwmail@irm.ucla.edu(link sends email).
- Alternatively, employees may initiate the process by calling (310) 794‑6948 to speak with an IRM representative and request assistance.
- For UCLA Health staff, please contact UCLA Health Disability Management.
Not sure where to start? We can help you find the right resource.