Exceptions

Exceptions

All online content must meet the accessibility requirements of WCAG 2.1 at the AA level, unless one of the following exceptions applies.

Archived Web Content

Web content that meets all four of the following requirements is not required to meet WCAG accessibility standards: 

  1. The content was created before April 24, 2026, or reproduces paper documents or the contents of other physical media (audiotapes, film negatives, and CD-ROMs for example) that were created that date; and
  2. The content is kept only for reference, research, or recordkeeping and is not needed to access or participate in any university program, employment, service or activity; and
  3. The content is kept in a special area for archived content; and
  4. The content has not been changed since it was archived.

Example: Spreadsheet data on a departmental website from a research project that was completed prior to April 2026, is not assigned for use by students, is kept in an “archive” subdomain of a department website, and is not updated after April 2026 would likely be exempted from WCAG requirements. 

However, if the same data were assigned to students in a course after April 2026, or revised or amended after the same date, it would no longer be exempted and would have to be made accessible or removed from the site.

Example: A PDF of information on how to join a sponsored student organization or perform required tasks as a research assistant was posted in 2022 and has not been changed. The exception would not apply and the PDF would have to meet WCAG requirements because it is needed to participate in a university activity or university employment. 

Preexisting Conventional Electronic Documents

Documents that meet both of the following requirements are not required to meet WCAG accessibility standards:

  1. The documents are word processing, presentation, PDF, or spreadsheet files; and
  2. They were available on the state or local government’s website or mobile app before April 24, 2026.

Example: A PDF version of a decades-old manuscript posted to the archive section of a library’s website would be exempt from WCAG requirements if posted before April 24, 2026. The same document would not be exempt if posted after April 2026. 

Third-Party Posted Content

Where content is posted to a university website or other online application by a third party—that is, a member of the public or other person not controlled by the university—it is not required to meet WCAG accessibility standards. 

This exception applies only where the third party is not posting due to contractual, licensing, or other arrangements with the university.

Example: An image posted as a comment to a university social media post by a member of the public not acting on behalf of the university would be exempt from WCAG requirements. Thus, there would be no requirement that the image have an alt text description. However, if a university department contracted or otherwise arranged to have an outside entity post content on its behalf, that content would be covered by WCAG requirements.

Individualized Password Protected Documents

Online documents that meet all three of the following requirements are exempt:

  1. The documents are word processing, presentation, PDF, or spreadsheet files; and
  2. They pertain to a specific person or account; and
  3. The documents are password-protected or otherwise secured.

Note that this exception DOES NOT apply to course content in Canvas or any other learning management system, which must meet accessibility standards.

Example: A PDF of a traffic ticket or transcript for a particular student would likely fall within this exception. An HTML webpage containing the same information, however, would not. Likewise, a PDF uploaded to a Canvas course page would not fall within the exception, even if the course were accessible by only a few individuals.

Preexisting Social Media Posts

Social media posts made before April 24th, 2026 are not required to meet accessibility requirements. All social media posts on or after that date must meet all WCAG compliance standards.