Skip to Main Content

What to Know

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 Section 504 applies to all operations of institutions that receive federal funding, which includes UCLA. The Section 504 digital accessibility compliance deadline is May 11, 2026, and it imposes the same substantive requirements as ADA Title II.
  • 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. 

What Is Covered

UCLA’s digital accessibility requirements apply broadly. See the Digital Accessibility Frequently Asked Questions from UCOP for more details about what is covered under this policy. Covered content includes:
  • 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.

Submit or learn about the exception process

Get help determining whether an exception applies

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

RequirementDeadline
UC IMT-1300 (ITAPP implementation)April 24, 2026
Section 504 digital access complianceMay 11, 2026
ADA Title II digital access complianceApril 26, 2027
All new digital content must meet WCAG 2.1 AAEffective April 24, 2026

The Title II compliance deadline has been extended to April 26, 2027.  The Section 504 digital access compliance deadline remains May 11, 2026. Assume section 504 applies to UCLA, because UCLA receives funding from HHS. Section 504 and Title II impose the same substantive digital access obligations [WCAG 2.1 AA].

The Title II analysis for the exceptions remains the same. For those exceptions tethered to a date (archived web content, preexisting conventional electronic documents, and preexisting social media posts), the applicable date remains April 24, 2026. Thus, any new digital content created after April 24, 2026 must meet WCAG 2.1 AA.

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.

Get Adobe Acrobat Pro through Creative Cloud

Accessibility Remediation Tools

Looking for other tools? UCLA supports a range of accessibility scanning, review, and remediation tools for websites, applications, and documents.

Browse accessibility tools and resources

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 encounter a digital accessibility barrier on a UCLA website, application, or document, you can report it for review and remediation.
 
Report an accessibility issue

If you are seeking an accommodation and/or support related to a disability, please reach out to one of the following offices:

Not sure where to start? We can help you find the right resource.