Overview
Across UPCEA’s membership and higher education more broadly, every individual plays an important role in fostering inclusive environments. As we increasingly rely on digital technologies to enhance learning and streamline operations, it becomes imperative to ensure that our websites, software, and course content are accessible to all, regardless of ability. Ensuring content is accessible can have a significant impact. Using 2019-20 data, the National Center for Education Statistics found that more than 20% of undergraduate students report having at least one disability to their institutions along with more than 10% of graduate students.
This resource details digital accessibility requirements primarily from a legal perspective. However, it is ultimately intended to serve as a more foundational resource to help those working in a wide range of roles to both support risk mitigation efforts and implement appropriate measures to create a more inclusive online learning landscape.
Accessibility Expectations and Enforcement
Federal agency definitions for what would be considered “accessible” for ADA purposes have existed in the context of higher education enforcement actions for more than a decade. However, these definitions have been somewhat subject to interpretation, with accessibility being achieved, in principle, when “a person with a disability is afforded the opportunity to acquire the same information, engage in the same interactions, and enjoy the same services as a person without a disability in an equally effective and equally integrated manner, with substantially equivalent ease of use.” (OCR Compliance Review, University of Cincinnati, 2014, p. 2). Conformance with specific technical standards would have been considered neither strictly necessary (absent a court order) nor sufficient.
However, the degree to which WCAG conformance, in particular, could be demonstrated had nevertheless been influential as part of lawsuits and investigations alleging discrimination under the ADA. At times, institutions of higher education have asserted that accessibility lawsuits and enforcement efforts combined with the lack of a clear standard for accessibility and ongoing rulemaking efforts created due process violations, but any such disputes had settled out of court without a final decision being reached on the merits of these claims. (See, e.g., NAD v. Harvard and NAD v. MIT).
For Title III entities, confusion over specific compliance obligations with regard to digital accessibility may continue. However, with specific accessibility standards, WCAG 2.1, AA, now codified in ADA implementing regulations under Title II, public institutions will have a harder time arguing that expectations for accessibility are unclear. Even during this interim period as institutions work towards compliance by the end of April 2026 or 2027, and even for private institutions of higher education that are not explicitly subject to WCAG conformance, these same guidelines can be useful to employ as part of compliance efforts and to better serve learners.
Compliance Tips
1. Convene Experts and Stakeholders. A critical first step for creating policies, resources, and procedures devoted to improving digital accessibility will be convening appropriate subject matter experts and stakeholders from across the institution. The Title II accessibility rule along with broader compliance and ethical obligations impact a wide range of systems and activities and a wide range of campus units, as a result. For institutions that lack an accessibility coordinator or devoted accessibility team, which may have already formed a network of experts and key stakeholders, forming an accessibility task force with compliance specialists and representatives from technology services, procurement, legal, online learning, library, student services (including disability services and resource units), marketing, and academic units could be formed to address many of the same critical issues and prioritize areas of greatest need. Ensuring representation from students and other end-users with disabilities will also be critical to the success of these efforts.
2. Establish Clear Policies and Procedures. While many institutions may have existing digital accessibility policies, these policies may need to be updated to ensure WCAG 2.1 (or higher), Level AA is set as the minimum technical standard for accessibility. The scope of the policy may also need to be updated (e.g., online course content should be mentioned explicitly in policies that refer only to “websites”). Resources devoted to supporting successful implementation in consideration of a wide range of digital environments and tools (e.g., online courses, websites, training for staff, social media, and technology procurement) should be listed or linked in any updated policies to ensure these are easily discoverable.
3. Ensure Accessibility Barriers Can Be Identified, Reported, and Remediated. While compliance reviews can be initiated without a complaint, providing a mechanism for individuals to report accessibility barriers can be a particularly effective strategy for minimizing the chances of accessibility complaints being filed in addition to ensuring students and learners are not falling behind in their studies due to such barriers. The University of California, Berkeley, for example, has created a web accessibility page detailing accessibility policies and barrier reporting procedures, which is linked in website footers. This page may have been created to satisfy conditions of a consent decree entered into with the DOJ in 2022, but many institutions have adopted a similar approach absent any explicit legal obligation to do so. Institutions may wish to also consider including accessibility statements on their homepages to further signal the importance of accessibility. George Washington University has taken this approach, for example, stating on its homepage that it is “committed to making all web properties and web content accessible and usable for everyone, including people with disabilities, by employing principles of universal design and striving to conform to the Web Content Accessibility Guidelines” before providing a link to an accessibility feedback form.
4. Teach and Design with Accessibility in Mind. Instructors and instructional designers will not necessarily have a foundation in the various web design and programming concepts used throughout WCAG resources, and may therefore find them difficult to navigate. Ideally, these standards would be translated for different audiences, with clear and practical examples provided for the instructional contexts, such as for the use of LMSs, content creation software, and learning tools. For example, the University of Michigan’s Center for Academic Innovation uses this online learning accessibility checklist, which promotes best practices that are mapped to specific WCAG standards. Approaching accessibility efforts through an appeal to pedagogical frameworks and best practices can be helpful as well, such as by encouraging the use of Universal Design for Learning principles. Ensuring faculty and staff have general familiarity with accessibility best practices and designing online courses to be generally accessible from the start can save significant time, cost, and effort that would instead need to be devoted to remediation work after content has already been created. When filming lecture videos, for example, asking instructors to narrate certain actions critical to the learning objectives could potentially eliminate the need to add audio descriptions post-production, which vendors can charge upwards of $10 per minute of video to provide.
5. Evaluate Third Party Content, Tools, and Services for Accessibility. At many institutions, third party tools and services will not always be procured through a central office as certain cost thresholds or other conditions may not be met, particularly with regard to free or low-cost tools used in courses open to the public and without FERPA implications. Even with regard to more central processes when such conditions are met, any accessibility testing or requests for information regarding the software accessibility (e.g., Voluntary Product Accessibility Template or “VPAT” requests), can be limited to tool reviews and may not extend to requests to procure services, such as instructional design services where course content would still be produced. Updates to procedures at both the institution- and unit-levels may be appropriate, such as by including accessibility criteria in requests for proposals and contracts with a wider range of third-party vendors. For situations in which no formal review process is applicable, faculty and staff may then need training and support to evaluate the accessibility of tools and third-party content.
Resources
- DOJ Title III Accessibility Rule: Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities
- Web Content Accessibility Guidelines (WCAG) 2.1
- Accessibility in Online Learning at the University of Michigan’s Center for Academic Innovation.pdf
- VPAT - Information Technology Industry Council
- 1EdTech TrustEd Apps Accessibility Rubric Specification v. 1.0
- UPCEA Members: CORe Discussion Thread About this Resource
History of Changes/Authorship
This guide was originally authored by Richard LaFosse of the University of Michigan with input by the UPCEA Policy Committee and Staff. It was first published and last updated on August 22, 2024.
Have a question about or suggestion for this resource? Contact us at [email protected].
