IT-23 University of Maryland Digital Accessibility Standard


Table of contents

Purpose

The University of Maryland (University) Digital Accessibility Standard (Standard) establishes minimum accessibility requirements for implementing the University of Maryland Electronic Information, Communication and Technology (EICT) Accessibility Policy. It applies to University units that create, develop, procure, maintain, or use EICT.

As called for in Section VII of the EICT Accessibility Policy, this Standard translates policy requirements into practical expectations for University units. It identifies applicable accessibility standards, clarifies unit responsibilities, explains content exception categories and the exception request process, and provides guidance for addressing accessibility barriers.

These requirements support the University’s commitment to ensuring that individuals with disabilities have equal access to University information, services, programs, and activities. They also support compliance with applicable federal and state laws and regulations, including Title II of the Americans with Disabilities Act of 1990 (“ADA”), Section 504 of the Rehabilitation Act of 1973, and the U.S. Department of Health and Human Services regulations. Together, these authorities prohibit disability-based discrimination and establish accessibility obligations for public entities and recipients of federal financial assistance, including public institutions of higher education such as the University.

To help units meet these obligations, the Standard connects its requirements with the University’s digital accessibility guidance, training, tools, and technical assistance, supporting accessibility throughout the EICT lifecycle.

Top

Scope

In alignment with the University of Maryland Electronic Information, Communication and Technology (EICT) Accessibility Policy, this Standard applies to Web-based EICT that the University or any of its units provides or makes available to support teaching, research, service, or administration. It applies whether the University provides the Web-based EICT directly or makes it available through contractual, licensing, or other arrangements (for example, through third-party vendors or open sources). 

Within this scope, covered resources include external content and resources that individuals are required to access or use to participate in University courses, programs, services, or activities, regardless of where the resources are hosted or whether a formal contract or license exists.

Covered resources also include Web-based information that the University provides or makes available through shared or jointly managed activities with other organizations, including research and grant-funded collaborations, multi-institution centers and consortia, conferences, and community programs.

Examples of covered EICT are provided in the next section.

Covered EICT

Covered EICT includes, but is not limited to:

  1. Websites and Web Applications  (e.g., umd.edu sites, college and department websites, research and project websites, internal websites, web portals, dashboards, online forms, registration systems, scheduling tools, web applications developed for University programs or services, and administrative systems).
  2. Course Materials (e.g., ELMS-Canvas pages, syllabi, assignments, assessments, discussion activities, required readings, presentations, lecture materials, and other teaching and learning resources).
  3. Electronic Documents (e.g., PDFs, word-processing documents, presentations, spreadsheets, reports, policies, procedures, meeting agendas, employee training materials, newsletters, electronic flyers, research materials, and documents used by employees in their routine work), including documents distributed through email, shared drives, and learning management systems.
  4. Video and Multimedia Content (e.g., lecture recordings, livestreams, podcasts, webinars, training videos, promotional videos, event recordings, and research videos).
  5. Social Media Content (e.g., posts, images, videos, stories, livestreams, and event announcements published through official University or University-affiliated accounts).
  6. Vendor-Provided Software, Platforms, and Tools (e.g., Panopto, Google Workspace, learning technologies, communication and collaboration platforms, survey tools, and human resources, finance, research, and other administrative systems), including purchased, licensed, free, and open-source tools within the scope of this Standard.
  7. Mobile Applications (e.g., the UMD app, ELMS-Canvas app, Terp Ride, and other mobile applications provided or made available by or on behalf of the University).

Web-based information exempt from the WCAG conformance requirement, and the conditions for those exemptions, are outlined in the Exemptions section below.

For questions about whether a particular EICT is covered by this Standard, contact the ADA Coordinator at ADAcoordinator@umd.edu. 

Exemptions

Under the EICT Accessibility Policy, in the following limited situations, the specified Web-based information is not required to conform to WCAG 2.1 Level A and AA requirements outlined in this Standard below.

Clarifications to exemptions

  1. Units do not need to submit a formal exception to the Policy request when content meets all the criteria for an exemption listed above. The unit that owns or controls the content is responsible for verifying and documenting that all applicable criteria are met. If eligibility is unclear, the unit must consult the ADA Coordinator before treating the content as exempt.
  2. Units must keep documentation supporting the exemption within the unit. Units must also provide clear, accessible instructions for requesting an accessible version. These instructions must appear near the content or on the collection’s main page and include a monitored contact or accessible request form. 
  3. Archived web content must be stored in a clearly labeled archive area. If the content or its use changes, the unit must reassess whether it still meets the exemption criteria.
  4. All Web-based information under an exemption category must be made accessible and usable upon request. The responsible unit must monitor and respond promptly to these requests, as outlined in items 7 and 8 of the Unit Responsibilities section below.
  5. Content that does not meet all the criteria for an exemption must comply with the digital accessibility requirements in the Policy and this Standard, unless an exception has been approved through the Policy’s exception request process.

Top

Standard

Effective April 26, 2027, covered legacy and newly designed Web-based information must meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level A and Level AA success criteria and conformance requirements. This obligation is subject to the applicable compliance dates, exemptions, and other provisions established by the EICT Accessibility Policy. This compliance date does not postpone accessibility obligations already required by law or University policy.

Internal employee-facing EICT

Web-based information that is internal to one or more University units and available only to employees (meaning it is neither student-facing nor public-facing) must comply with applicable accessibility standards. Examples include internal websites, applications, platforms, and mobile apps. Employee-only access does not, by itself, qualify content for an exemption.

When internal employee-facing EICT involves a software product undergoing the University’s procurement review process, units must follow applicable procurement and accessibility review requirements. Refer to the DIT Software Risk Management (SRM) program for the applicable review process. For assistance with that process, contact software-risk-mgmt@umd.edu.

When an employee needs an accommodation to access or use internal employee-facing EICT, units must work with UHR or Faculty Affairs, as appropriate, to arrange and implement reasonable accommodations in accordance with the University Policy on Access for Individuals with Disabilities (VI-1.00(D)). 

For guidance on handling specific accessibility requests or concerns involving internal employee-facing EICT, contact the ADA Coordinator at ADAcoordinator@umd.edu. 

Unit responsibilities

  1. Digital accessibility is a shared and ongoing responsibility. Each unit is accountable for the EICT it creates, owns, controls, procures, manages, or makes available. The unit that owns and controls the content is responsible for remediating, replacing, or modifying the original content. For online instructional content, this responsibility rests with the instructor or unit that owns and controls the content, including content in the LMS and outside platforms. Units that procure or manage web content or mobile applications are responsible for addressing accessibility barriers in those resources.
  2. Unit leadership must work with Digital Accessibility Liaisons, the DIT Digital Accessibility Office, ADA Coordinator, and other relevant stakeholders, to coordinate accessibility efforts, align unit priorities with University guidance, and address support needs and barriers.
  3. For legacy content, units must prioritize high-impact digital assets, such as public-facing websites, instructional materials, and essential resources, focusing first on barriers that prevent access or participation. Units should make incremental improvements by updating or replacing inaccessible legacy content and removing content that is no longer needed.
  4. New content must meet applicable accessibility requirements from the outset. Over time, units should integrate digital accessibility into standard workflows, including content creation, web publishing, procurement, and instructional design.
  5. In coordination with the DIT Digital Accessibility Office, ADA Coordinator, and other relevant stakeholders, units must regularly evaluate their covered EICT for accessibility barriers and track progress in addressing identified issues. Evaluations must include manual checks and, where appropriate for the content or technology, automated checks (e.g., Siteimprove for websites and Ally for ELMS-Canvas courses). Automated results alone do not establish conformance.
  6. When the University provides or makes available Web-based information through collaborations or jointly managed activities (e.g., grant-funded collaborations, multi-institution centers and consortia, conferences, and community programs), units must discuss, agree on, and document digital accessibility roles and responsibilities with their partners, including who will evaluate accessibility, fix barriers, and respond to access requests.
  7. Units must provide a clear, accessible way for anyone to request content in an accessible format or report an accessibility barrier. All unit websites must include a clearly visible Web Accessibility link to www.umd.edu/web-accessibility in the footer or another consistent and prominent location. ELMS-Canvas includes this accessibility link in its menu so users can request support or report a barrier.
    1. Depending on their services, units may provide a designated accessibility contact; accessible request and reporting forms on websites and mobile applications; assistance by email, phone, chat, or in person; and accessibility information on course syllabi, program, event, facility, and service pages.
    2. When an individual with a disability, or someone acting on their behalf, requests accessible content, the responsible unit must provide an accessible, usable version of content the University provides or makes available. This requirement also applies to content that qualifies for an exemption.
    3. Units must work with the individual, give primary consideration to their requested format, and provide timely access based on their needs, consistent with the University Policy on Access for Individuals with Disabilities (VI-1.00(D)). Any alternative format must provide equally effective access.
    4. Units must not deny a request solely because the individual is not affiliated with UMD or will use the content outside a UMD course or activity.
  8. Units must route accessibility requests to the appropriate staff within their unit, promptly acknowledge receipt, and resolve requests in a timely manner. Resolution may include remediating the content or providing an equally effective alternative consistent with this Standard.
    1. Units should aim to resolve requests within 10 business days of receipt. Earlier action must be taken when needed to ensure timely access to a course, program, service, or activity. This target must not delay earlier action needed to ensure timely access to a course, program, service, or activity.
    2. If additional time is needed, the unit must arrange timely, equally effective interim access in consultation with the individual and communicate the expected completion date to the requester. Interim access does not replace required remediation or the Policy’s exception request process.
    3. For help identifying the appropriate unit contact or addressing technical accessibility barriers, contact the DIT Digital Accessibility Office at itaccessibility@umd.edu.
    4. Units should consult the ADA Coordinator when responsibility for a request or the appropriate response is unclear, such as when a request concerns general use rather than an identified disability-related access need, or content controlled by an outside publisher or organization.
    5. If a unit believes fulfilling a request would cause an undue financial or administrative burden or a fundamental alteration, it must follow the process outlined in Requesting an Exception to the Policy below. Units must not make that determination independently. For questions about the exception request process, contact the ADA Coordinator at ADAcoordinator@umd.edu.

Top

Guidelines and resources for making digital content accessible

These resources focus on foundational digital accessibility best practices that can have the greatest impact across common types of digital content. Applying these practices consistently will help University units reduce barriers and make digital content more accessible and usable for everyone. They provide a practical starting point but do not represent every WCAG criterion or digital accessibility requirement. The requirements summarized below are subject to the scope, compliance dates, content exemptions, and approved exceptions described in this Standard.

Foundational principles across content types

These are the four WCAG accessibility principles:

  1. Perceivable – Content must be presented in ways that users can perceive. Examples include alternative text for images, captions, other alternatives for multimedia, appropriate content structure, and sufficient color contrast.
  2. Operable – Users must be able to navigate and interact with content. Examples include keyboard access, visible keyboard focus, and clear navigation.
  3. Understandable – Content must be readable, clear, consistent, and predictable.
  4. Robust – Content must be compatible with different browsers, devices, and assistive technologies, including screen readers.

Essential digital accessibility practices across content types

Units should start by building foundational knowledge and ensuring instructors and staff responsible for creating, publishing, or managing digital content are proficient in applying the Six Essential Steps and participate in relevant digital accessibility training for their role. 

The Six Essential Steps framework translates key WCAG requirements into practical actions that can prevent common accessibility barriers across many types of digital content. It emphasizes practices that have a high impact on accessibility and are often straightforward to implement with familiar content creation tools, providing a manageable starting point for incorporating accessibility into everyday work. Keyboard accessibility and logical reading order are included as additional essential practices aligned with WCAG.

Using AI to support digital accessibility remediation

Common applications

Before acquiring or adopting software, units must follow the applicable University review process. Refer to the DIT Software Risk Management (SRM) Program to determine which review process applies, what security, privacy, and accessibility reviews are required, and whether the software qualifies for expedited procurement. Eligibility for expedited procurement does not exempt software from accessibility requirements. Contact software-risk-mgmt@umd.edu for guidance.

As part of the DIT SRM accessibility review process, units must obtain up-to-date accessibility documentation from vendors, such as an Accessibility Conformance Report (ACR) completed using the Voluntary Product Accessibility Template (VPAT). When barriers are identified, units must obtain a vendor remediation roadmap with planned fixes and clear timelines. Vendor documentation and planned fixes do not, by themselves, establish that a product meets accessibility requirements. A remediation roadmap, backed by contractual commitments, strengthens vendor accountability for completing planned fixes on time and maintaining the product’s accessibility.

For purchases of web-based deliverables, units must work with Procurement and Business Services at procurement@umd.edu to include the UMD IT Accessibility Addendum and required contract provisions. This includes software and services used to create, maintain, or update University websites, applications, and online instructional resources. Procurement and Business Services can assist with vendor communications and contractual accessibility commitments.

Units may request assistance from Procurement and Business Services at procurement@umd.edu with vendor communications and contract requirements. For questions about digital accessibility or assistance with accessibility documentation, barriers, or remediation plans, contact the DIT Digital Accessibility Office at itaccessibility@umd.edu. 

Top

Requesting an Exception to the policy

Exceptions are allowed only in limited circumstances. A unit must submit a request and receive approval before relying on an exception. This process is separate from the content exemption categories described earlier in this Standard.

A unit may request an exception for one or more of the following reasons:

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. 

The unit must submit the Exception Request Form. The request must:

Submitting an exception request does not guarantee approval. While a request is under review, the unit remains responsible for providing timely access. If an exception is approved, the unit remains responsible for providing access by meeting digital accessibility requirements to the greatest extent possible and providing an equally effective alternative so that people with disabilities can receive the same benefits and services to the maximum extent possible. The unit must follow any conditions established in the approval.

For questions about exception requests and the review process, contact the ADA Coordinator at ADAcoordinator@umd.edu. For technical assistance identifying barriers, evaluating accessible solutions, or preparing supporting documentation, contact the DIT Digital Accessibility Office at itaccessibility@umd.edu. 

Top

Accountability and commitment to progress

Ensuring digital accessibility is an ongoing process. Units must implement this Standard, identify and address accessibility barriers, and respond promptly to accessibility requests. Practical, sustained improvements support compliance but do not extend deadlines or replace required approvals.

When a barrier cannot be corrected promptly, the responsible unit must provide an equally effective alternative that enables timely access to the affected information, service, program, or activity and establish a reasonable plan and timeline for remediation. Interim access and remediation plans do not replace the Policy’s exception request process when an exception is needed. Units that do not respond to accessibility requests, provide access, or meaningfully engage in addressing identified barriers may be referred to unit leadership, the ADA Coordinator, the VPIT & CIO, or their designee for additional support, review, and determination of next steps.

Top

Escalation and support

Top

Revision history

Version 1.0, Approved by CIO and IT Council, November 9, 2026.

Top