When to use Ally, UDOIT, or the Canvas Course Accessibility Checker
accessibility
Knowing what to fix is only half the work — you also need the right tools to fix it. This section collects the scanning tools, remediation software, templates, and checklists available to the UCLA community. Most are free for faculty and staff. Where campus-specific resources exist, we link to them directly; where the best resource is external, we'll tell you that too.
PDFs and other digital documents should be easy to read, easy to navigate, and usable with assistive technology. That includes documents shared on websites, in email, in courses, and through campus systems. Remediating PDFs is not only a compliance step; it is part of creating a more usable and inclusive experience for everyone.
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. The Steering Committee is working with Compliance and Campus Counsel to assess the implications for the campus program, including whether this affects our obligations under other relevant laws and whether UC's IT Accessibility Policy (IMT-1300) will be revised. We will share updates as more information becomes available.
Not sure who can help with digital accessibility? Start here.
If you've run into a digital accessibility problem on a UCLA site, application, or document, please contact the UCLA ADA/504 Compliance Office for further assistance by emailing ada@saonet.ucla.edu or calling (310) 206-8049.
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.
Documents can have the most accessibility challenges, and one of the most fixable. PDFs, Word files, PowerPoint presentations, and spreadsheets are everywhere at UCLA: on departmental websites, in Bruin Learn, attached to emails, linked from forms. And as of April 24, 2026, any document you create or post must meet WCAG 2.1 AA. The good news: you have tools available right now, most of them free.
If you own or manage a UCLA website: a departmental site, a lab page, a program page, an event site, or any other UCLA web presence, it must meet the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard. This applies to all UCLA websites, including pages behind a login.
If you are purchasing, renewing, or contracting for software, a platform, or any technology tool on behalf of UCLA, including free products, low-cost subscriptions, and click-through agreements, then accessibility requirements apply to that purchase.