Short answer: almost certainly yes.
If you create, manage, teach with, or publish digital content at UCLA: websites, documents, course materials, applications, social media, or technology tools, then your content must be digitally accessible.
This page will help you understand exactly what's covered, what's not, and what to do if you're unsure.
What is covered
The following types of content and technology must meet WCAG 2.1 AA:
- Websites and web pages All UCLA websites and web applications, including pages and tools behind a login or firewall. This includes departmental sites, lab pages, event pages, portals, and web-based tools.
- Documents PDFs, Word files, PowerPoint presentations, and spreadsheets created or posted on or after April 24, 2026. This includes documents distributed by email, posted to websites, or shared through Bruin Learn or other platforms.
- Course materials All digital materials used in instruction: slides, readings, videos, assignments, and third-party tools integrated into Bruin Learn or other learning platforms. This applies to faculty, instructors, TAs, and instructional designers.
- Applications and software Campus applications, enterprise systems, student and faculty portals, administrative tools, and any software UCLA provides or requires community members to use.
- Multimedia Videos, audio recordings, podcasts, and interactive content UCLA produces or hosts: including recorded lectures, training videos, and promotional content.
- Technology purchases Any software, platform, or tool UCLA procures or licenses, including free products and click-through agreements.
- Social media Posts published on or after April 24, 2026 on UCLA-managed social media accounts.
- Third-party content Content posted by a third party under a contractual, licensing, or other arrangement with UCLA.
What is not covered
The following categories are explicitly exempt from the accessibility standard under UC IMT-1300:
- Archived content Content preserved solely for historical reference that is no longer actively used to access UCLA services, programs, or activities.
- Pre-April 24, 2026 documents Electronic documents (PDFs, Word files, presentations, spreadsheets) posted before April 24, 2026: but only if they are not currently being used to apply for, access, or participate in UCLA services, programs, or activities. If someone needs that document to do something today, it should be treated as in scope regardless of when it was posted. If the content is archived and someone requests an accommodation to read it, it is no longer considered archived and should be updated.
- Pre-April 24, 2026 social media posts Social media posts published before April 24, 2026 on UCLA-managed accounts.
- Individualized personal documents Password-protected or otherwise secured documents about a specific individual, their property, or their account.
- Truly third-party content Content posted by a third party that is not the result of a contract, license, or other arrangement with UCLA.
Still not sure? Ask yourself these questions.
- Does someone need this content to access a UCLA service, program, or activity? If yes, it's in scope, regardless of format, age, or where it lives.
- Did UCLA create it, commission it, or require its use? If yes, it's in scope.
- Was it posted or created on or after April 24, 2026? If yes, it's in scope.
- Is it a document posted before April 24, 2026 that nobody actively uses anymore? That may be exempt, but if there's any doubt, treat it as in scope or consider whether it should simply be removed.
A note on exemptions vs. exceptions
An exemption means the content is outside the scope of the policy entirely.
An exception is different: the content is in scope and does need to comply, but there's a documented reason why full compliance isn't currently achievable. Exceptions require institutional approval and an Equally Effective Alternate Access Plan (EEAAP) to ensure affected users aren't excluded in the meantime.
If you're hoping something is exempt but you're not confident, it's worth checking before assuming; the cost of getting it wrong falls on the people who can't access your content.
