Skip Navigation. Skip to content
University Policies
Back to Policy Section VI: General Administration
Section VI: General Administration

Policy Number: VI-1.00(E)

University of Maryland Accessible Technology Policy

(Approved by the President on an interim basis Amended and approved by President Technical amendments Approved by the President on an interim basis, pending University Senate review )

I. POLICY

The University of Maryland (“University”) is committed to creating and maintaining a welcoming and inclusive educational and working environment for people of all abilities and to ensuring equal access to information and services for all its constituencies. Web-based information and services delivery are the primary means by which the campus community and its visitors communicate and conduct business.

This Policy sets minimum standards for the Accessibility of all University Web-based information used to conduct University business, to ensure compliance with applicable state and federal law and regulations.

II. DEFINITIONS

  1. “Accessibility” means that individuals with disabilities are afforded the same opportunity to independently, fully and equally acquire the same information, engage in the same interactions, and enjoy the same services as individuals without disabilities, in an equally effective and equally integrated manner, with substantially equivalent ease of use.
  2. “Legacy Web-based information” means any Web-based information created, adopted, or modified before April 24, 2026.
  3. “Web-based information” means web pages, websites, Web content, web-based applications, Mobile applications, online instructional content, services, and resources, and Conventional electronic documents, that the University provides or makes available directly or through contractual, licensing, or other arrangements (for example through third-party vendors or open sources).
    1. “Conventional electronic documents” means Web content or content in Mobile applications that is in the following electronic file formats: portable document formats (‘‘PDF’’), word processor file formats, presentation file formats, and spreadsheet file formats.
    2. “Mobile applications” means software applications that are downloaded and designed to run on mobile devices, such as smartphones and tablets.
    3. “Web content” means the information and sensory experience to be communicated to the user by means of a user agent (meaning any software that retrieves and presents Web content for users), including code or markup that defines the content’s structure, presentation, and interactions. Examples of Web content include text, images, sounds, videos, controls, animations, and conventional electronic documents.

III. REQUIREMENTS

  1. Effective April 24, 2026, all Web-based information (including both Legacy Web-based information and newly designed Web-based information) by any University administrative, academic, or programmatic unit must be in compliance with the W3C Web Content Accessibility Guidelines, version 2.1 (WCAG 2.1) Level A and Level AA success criteria and conformance requirements and any other accessibility standards required by law or the University.
    1. The following types of Web-based information are not subject to this requirement:
      1. Archived web content: Web content that: (1) was created before, reproduces paper documents created before, or reproduces the contents of other physical media created before April 24, 2026; (2) is retained exclusively for reference, research, or recordkeeping; (3) is not altered or updated after the date of archiving; and (4) is organized and stored in a dedicated area clearly identified as being archived;
      2. Preexisting conventional electronic documents: Conventional electronic documents that are available on a website or mobile app before the date of compliance, unless such documents are currently used to apply for, gain access to, or participate in the University’s services, programs, or activities;
      3. Third-party content: Content posted by a third party, unless the third party is posting due to contractual, licensing, or other arrangements with the University;
      4. Individualized, password-protected or otherwise secured conventional electronic documents: Conventional electronic documents that are: (1) about a specific individual, their property, or their account; and (2) password-protected or otherwise secured; or
      5. Preexisting social media posts: University social media that were posted before April 24, 2026.
    2. All Web-based information under an exception category must be made accessible and usable upon request.
  2. All University web pages (newly designed or legacy), including course content sites, must contain the words “Web Accessibility” in the footer or any visible location and link to a common institutional web page (https://www.umd.edu/web-accessibility) that contains the following statement: “The University of Maryland is committed to equal access to Web-based information and other information technology accessible to all users. If you are having trouble accessing the content on this (website or course content page) and need it in an alternative format or have comments or suggestions on accessibility, contact itaccessibility@umd.edu. For more information about accessibility at UMD, visit the UMD Accessibility website.”
  3. The unit that owns and controls the Web-based information is responsible for any remediation and for replacing or modifying the original content.
  4. The instructor or unit who owns and controls online instruction content in the University’s learning management system (“LMS”) or other outside platforms is responsible for any remediation and for replacing or modifying the original content.
  5. The unit that procures or manages the Web content or Mobile application is responsible for remediation and for replacing or modifying the original content.

IV. EXCEPTIONS

  1. Any University administrative, academic, or programmatic unit may request an exception to the requirements of this Policy to use “conforming alternate versions of Web Content”, as defined by WCAG 2.1, only where it is not possible to make Web-based information directly accessible due to technical or legal limitations.
  2. Any University administrative, academic, or programmatic unit may request an exception to the requirements of this Policy on the basis that noncompliance with the requirements would have such a minimal impact on access that it would not affect the ability of individuals with disabilities to do any of the following in a manner that provides substantially equivalent timeliness, privacy, independence, and ease of use: (a) access the same information as individuals without disabilities; (b) engage in the same interactions as individuals without disabilities; (c) conduct the same transactions as individuals without disabilities; and (d) otherwise participate in or benefit from the same services, programs, and activities as individuals without disabilities.
  3. Any University administrative, academic, or programmatic unit may request an exception to the requirements of this Policy on the basis that compliance with the requirements: (a) would result in a fundamental alteration in the nature of a University service, program or activity, or (b) would result in an undue financial or administrative burden. A decision that compliance would result in a fundamental alteration or undue burden must be made by the President or their designee after considering all resources available for use in the funding and operation of the service, program, or activity, and must be accompanied by a written statement of the reasons for reaching that conclusion. If compliance would result in a fundamental alteration or undue burden, compliance is required to the extent that it does not result in a fundamental alteration or undue burden, and the University shall take any other action that would not result in a fundamental alteration or undue burden but would nevertheless ensure that individuals with disabilities receive the benefits or services provided by the University to the maximum extent possible.

V. EXCEPTION REQUEST PROCESS

Units seeking an exception must submit an exception form, which may be found at https://it.umd.edu/accessibility, explaining in detail why the Policy exception is being sought and how, if the requested exception is granted, the unit will provide equally effective alternative access and ensure, to the maximum extent possible, that individuals with disabilities will receive the same benefits or services as their nondisabled peers.

VI. PURCHASING

University purchases of web-based deliverables must comply with applicable procurement policies, processes and standards, including any IT accessibility requirements and contract provisions. More information is available at https://purchase.umd.edu/. 

VII. REVIEW

The University’s Americans with Disabilities Act (ADA) Coordinator will initiate a review and propose necessary revisions of this Policy and its associated standards as needed.

VIII. CONTACTS