Title II of the Americans with Disabilities Act (ADA) requires state and local governments—including public education systems—to make their services accessible. While ADA requirements have always covered digital channels like websites, apps, and learning platforms, details on compliance for these technologies weren’t always clear.
On April 24, 2024, that changed.
The Department of Justice published a new rule providing specific requirements for web accessibility under Title II of the ADA.
The updated regulation will help public educators provide digital services to every student—including people with disabilities, who may have been previously left behind by inaccessible design.
For example, prior to the 2024 rule, Title II was silent on the issue of keyboard control for websites. People with motor disabilities might navigate websites via keyboard instead of using a mouse. If your site isn’t designed to support keyboard navigation, these users won’t be able to access the information you post. That’s just one of many omissions that the Title II web rule now addresses.
Here’s what teachers and administrators in public education need to know about the 2024 web accessibility rule for the ADA Title II.
The Title II Web Rule’s Impact on Public Education
The latest Title II changes are particularly impactful for public education systems at every level (K-12, community college, state universities, etc.)
In the 2022-23 school year, 7% of K-12 students in the U.S. took at least one virtual course; 3% only learned online. The same year, over half of college students engaged in distance learning.
That’s a lot of online course content—and public educators now must ensure it all complies with the Title II web rule.
Of course, educators also use digital tools for in-person learning. These systems must also comply with Title II. The takeaway is this: If your lessons involve computers or digital devices, you need to be familiar with the Title II web rule.
Looking for accessibility tools that can help your school comply with Title II? Contact us to learn about text to speech from ReadSpeaker.
ADA Title II Web Accessibility Rule: Requirements and Implications
The ADA calls its specific requirements technical standards. These are the actions or design choices that those bound by the ADA must take to achieve a compliant level of accessibility.
The 2024 web accessibility rule provides these technical standards for web content and mobile apps. Essentially, the rule says, your digital services will be compliant with ADA Title II if they conform to the Level AA success criteria listed in the Web Content Accessibility Guidelines (WCAG) version 2.1.
We’ll explain what that means shortly. First, let’s look at some of the basics surrounding this rule.
Who must follow the Title II web rule?
Title II of the ADA is designed to improve public sector accessibility. It applies to state and local governments, as well as all their agencies, departments, and travel authorities.
As we’ve mentioned, that includes public education institutions at every level. But it also covers other government services, including:
- Social service agencies
- State and local justice systems
- Election authorities
- Public healthcare facilities
- Parks and recreation departments
- Public transit organizations
- Library systems
The websites, mobile apps, and related digital services associated with any of these organizations must comply with the new ADA rule.
Who is the Title II web rule meant to serve?
The web rule is intended to improve digital accessibility for individuals with disabilities, so it primarily serves people with:
- Vision impairments or blindness
- Hearing impairments or deafness
- Motor limitations
- Speech disorders
- Photosensitivity
- Cognitive and developmental disabilities
While WCAG is designed to make as much content accessible, for the widest possible audience, it can’t address every need for every user. On the other hand, accessible design tends to create better user experiences for everyone, including people without disabilities. So the beneficiary pool for Title II’s web rule is quite deep.
What are the ADA compliance deadlines for the web rule?
The rule change takes effect in April 2026 for public entities with larger populations and 2027 for those with populations under 50,000.
The good news for government communications is that the Title II web rule should make your job easier, not harder. Rather than imposing onerous restrictions, Title II now provides clear guidance for web accessibility—and that sort of clarity is good for teachers and students alike.
It’s also good for the companies that provide educational technology: Vendors must provide Title II-compliant products if they wish to serve public school systems. Regulatory clarity helps these companies make informed design decisions.
But how exactly will the Title II web rule affect digital course design, ed-tech platforms, and online teaching tools? To answer that question, let’s take a closer look at WCAG 2.1.
What does WCAG 2.1 require?
The Web Content Accessibility Guidelines, or WCAG, are the gold standard for inclusive digital design. They’re published and maintained by the World Wide Web Consortium (W3C), an international nonprofit that creates standards and guidelines for web content.
These web accessibility guidelines are currently on version 2.2, but the Title II web rule requires conformance with WCAG 2.1, the previous iteration. Luckily, WCAG 2.2 is backwards compatible with version 2.1.
That means conformance with WCAG 2.2 also denotes conformance with WCAG 2.1, so both versions can help you make your content reliably accessible. At any rate, the fact that Title II now requires conformance with WCAG 2.1’s AA success criteria leads to a few important questions:
1. In broad terms, what does WCAG 2.1 ask of technology developers?
With nearly 80 discrete success criteria in WCAG 2.1, we can’t discuss everything in detail here. (Check out WCAG itself for the best information.) But luckily, the WCAG success criteria are neatly organized into the Four Principles of Web Accessibility. Looking at these gives us a strong idea of what Title II’s web rule requires.
The Four Principles of Accessibility in WCAG
The Principles of Web Accessibility, upon which WCAG success criteria depend, are:
- Perceivable. “Information and user interface components must be presentable to users in ways they can perceive,” says WCAG. That typically means your content should be available in multiple media: Not just text, but audible speech, for instance, and no video without captions.
- Operable. “User interface components and navigation must be operable,” says WCAG. That means users should be able to navigate your site, or use your app, in a way that works for them. That could be keyboard navigation instead of a mouse, for example.
- Understandable. “Information and the operation of [the] user interface must be understandable,” says WCAG. You can achieve this goal by including instructions, labelling buttons clearly (and in ways that show up in assistive technology), and designing interfaces that meet user expectations.
- Robust. “Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies,” says WCAG. So your sites and apps can’t frustrate screen readers or Braille displays, for instance. That requires careful backend design.
These principles make up an acronym: POUR. To conform with WCAG 2.1—and comply with Title II—your sites and apps must uphold the WCAG POUR principles.
2. How can you tell if e-learning sites and apps conform to WCAG?
Title II’s web rule requires conformance with WCAG’s “Level AA success criteria.” To understand this term, you have to know what a success criteria is.
A WCAG success criterion is a “testable statement” that is “not technology specific,” says W3C. For example, Success Criterion 1.1.1 – Non-text Content (Level A) states that “All non-text content that is presented to the user has a text alternative that serves the equivalent purpose…”
If all the images on your site have alternative text—and something similar is true for all your non-text content—your site conforms to this success criterion.
3. What does “Level AA” mean in WCAG?
Each WCAG success criteria is classified as Level A, Level AA, or Level AAA.
- Level A includes the core requirements for accessibility. These are the least strict and most achievable success criteria.
- Level AA builds on Level A with additional design requirements. Level AA is the goal for most websites and mobile apps.
- Level AAA success criteria are the most strict. Sites that conform to Level AAA rules are going above and beyond—which, where accessibility is concerned, is a great goal.
Each higher level includes the lower success criteria, so conformance with Level AA requires you to meet all Level A rules, too. Lots of tools can help in this effort. Text to speech (TTS), which automatically translates written text into audible speech, is a particularly powerful example.
How Text to Speech Improves e-Learning Accessibility
There’s no Level AA WCAG criteria that requires you to provide TTS on your learning platform, website, or mobile app. But that doesn’t mean TTS can’t help you comply with Title II. In fact, TTS is one of the most valuable website accessibility tools you can implement.
Here are a few ways TTS can help create more accessible e-learning websites and apps:
- Text to speech is a strong solution for making content perceivable, per the POUR guidelines. People with vision impairments and blindness don’t perceive written text, after all, and TTS translates all your written content into audible speech. Students with developmental disabilities, low literacy, or attention deficits may also find it easier to perceive speech than text.
- WCAG 2.1 Success Criterion 3.1.5 – Reading Level requires particularly complex writing to be available in a “version that does not require reading ability more advanced than the lower secondary education level.” Now, this is a Level AAA criterion, so it’s not strictly required by Title II—but it certainly contributes to a much more accessible website.
- Even prior to the new web rule, Title II best practices required “effective communication” for people with disabilities. That includes the use of “auxiliary aids.” An auxiliary aid is a tool that facilitates communication for people with disabilities—which absolutely includes TTS, ideally available natively on your site or in your app.
In other words, text to speech has always been a go-to solution for compliance with Title II of the ADA. The new web rule only increases its helpfulness.
That just leaves one question: What’s the best way to bring TTS to your public education websites, apps, and digital services?
Text to Speech for More Accessible Digital Learning Tools
ReadSpeaker offers a range of TTS accessibility tools that integrate seamlessly into your learning systems, including:
- Websites
- Mobile applications
- Learning management systems (LMS)
- Assessment platforms
- Augmented and alternative communication (AAC) devices
- And more!
ReadSpeaker’s TTS tools read any digital text, including documents and e-books. Integrate a single tool into your LMS to speech-enable every course. Our TTS products also include a suite of reading, writing, and studying tools to help students succeed.
We use the latest AI technology to construct synthetic voices that sound like the real thing, with accurate pronunciation and expressive speaking styles. Choose from over 50 languages and 200 lifelike voices—or create a custom branded AI voice that your students will recognize, and therefore trust.
ReadSpeaker’s customer service team is always available to help you create more accessible education services. We offer custom pronunciation dictionaries and ongoing linguist support so you can provide the best possible learning experience for every student.
Need help complying with the ADA’s Title II web rule? Contact the TTS experts at ReadSpeaker for powerful digital accessibility tools.
