Welcome to the TTA Community. TTA Connect is where you can manage and update your profile, search, and view opportunities, manage your work, track payments, and more.
Accessible instructional design gives every learner equitable access to training while helping organizations prepare for changing digital accessibility requirements. This blog explains the updated compliance deadlines, common accessibility barriers, and practical ways to incorporate WCAG requirements into storyboards, development, and testing. It also shows how early planning can reduce remediation work, strengthen content quality, and prepare learning programs for compliance.
Accessibility deadlines moved in April 2026, but the standard didn’t change. The Department of Justice extended ADA Title II web compliance to April 26, 2027, for large public entities and April 26, 2028, for smaller ones, while keeping WCAG 2.1 Level AA as the standard. Instructional design learning teams should use the extra time to build accessibility into storyboards now. Remediating a published course library takes longer than most teams expect, and a year passes quickly when several programs are already underway.
The DOJ explained why it extended the deadlines: it had overestimated what covered entities could accomplish in the original time frame. The agency cited staffing limits and noted that generative AI hasn’t reliably remediated inaccessible content at scale. Learning teams that were counting on a tool to handle the work should revise their plans.
The rule requires web content and mobile apps to meet WCAG 2.1 Level AA. That means providing captions and transcripts for video, text alternatives for images, sufficient color contrast, keyboard access, and structure that screen readers can navigate. Browser-based training falls within that scope.
Europe acted earlier. The European Accessibility Act has applied since June 28, 2025, and covers private companies that sell certain products and services in the EU, not just public bodies.
Private U.S. employers may also face accessibility requirements through contracts. When a state agency, university, or municipality must meet Title II, it may include WCAG conformance in its statement of work. Vendors that build courses for those clients then share responsibility for meeting the standard.
Federal website accessibility lawsuits rose again in 2025. Seyfarth Shaw, which has tracked ADA Title III filings since 2015, counted 3,117 federal website accessibility lawsuits in 2025, up 27 percent from 2,452 in 2024. These cases represented 36 percent of all federal Title III filings, compared with 28 percent the year before.
Keep that figure in context when discussing it with sponsors. Most cases involve public-facing retail and e-commerce websites, and Seyfarth doesn’t publish an industry breakdown. The data doesn’t show that companies are being sued over training modules. It does show that digital accessibility claims are rising as Title II requirements begin appearing in corporate contracts.
Employer obligations are separate from these website deadlines. If an employee can’t complete required compliance training because a module requires a mouse, the organization must address the barrier. TTA covered the original Title II changes in this explainer on the ADA updates, but its dates predate the April 2026 extension.
Each of these choices can exclude someone from training the organization may be legally required to provide. The scale is easy to miss. U.S. Bureau of Labor Statistics data for 2025 shows an employment-population ratio of 22.8 percent for people with a disability, compared with 65.2 percent for people without one. Many disabilities also go undisclosed. Design choices that improve eLearning for engagement often improve accessibility too. Captions, clear structure, and readable contrast help everyone, including employees watching on a phone in a noisy workplace.
Make these five decisions in the same order you build the course. A designer can handle each one without a specialist.
Add a line for every image that explains what the learner needs to understand. Waiting until later means reopening authoring files and republishing modules through the LMS.
Decide how learners will complete each interaction using only a keyboard. For example, drag-and-drop activities need another way to reach the same answer, designed from the start rather than added later.
Correct and incorrect states, status indicators, and category labels shouldn’t rely on color alone.
The narration script is already in the storyboard, so creating a caption file takes little extra work. Auto-captions often misstate technical or regulated terms and still require review.
Name WCAG 2.1 Level AA, identify who will test the course, and assign responsibility for fixes. When accessibility appears in the SOW, vendors can price it into the bid. Leaving it out often means paying for remediation later.
Automated checkers handle only part of the job. They can flag missing alternative text, contrast failures, and absent captions. They can’t judge whether alternative text is useful, whether the keyboard path makes sense, or whether a screen reader announces an interaction in a usable order. Federal agencies show the gap: GSA reported that 70 to 72 percent of agencies run automated document and web checks, while only 12 to 17 percent conduct usability testing with people with disabilities before deployment.
These agencies already operate under a legal mandate, so corporate L&D teams may test even less. Usability testing with people who use assistive technology is often the first step dropped, yet it catches problems scanners can’t: alternative text that exists but says nothing useful, or a knowledge check that a screen reader presents out of order.
At minimum, run an automated check on every module and test one module per program using only a keyboard. For workforce-wide training, pay two or three employees who use assistive technology to review it. TTA has written about building inclusion that encompasses disabilities, and a standing review panel is a practical way to put that principle to work in L&D.
WCAG 2.1 Level AA is the standard named in the DOJ’s ADA Title II rule and commonly referenced in procurement. Section 508 applies to federal agencies and their contractors, while the European Accessibility Act covers organizations that sell certain products and services in the EU.
The ADA Title II deadlines apply to state and local government entities. Private employers may still face accessibility requirements through public-sector contracts, ADA Title I obligations to employees, or the European Accessibility Act when they serve EU markets.
No. Automated tools can find missing alternative text, contrast failures, and absent captions. A person still needs to judge whether the text is useful, keyboard navigation is logical, and a screen reader presents each interaction in a sensible order.
Very little when accessibility is planned in the storyboard. Much of the work involves writing alternative text and mapping keyboard paths while the designer is already making content decisions. Retrofitting a published library takes far longer because teams must reopen source files, re-record narration, retest interactions, and republish courses.
Many learning teams understand the standard but don’t have the time or specialized experience to apply it across a backlog. TTA connects organizations with instructional designers and eLearning developers who build to WCAG from the storyboard, as well as remediation specialists for published course libraries. Its network includes more than 5,000 instructional design professionals across 30 industries.
Find instructional design talent on TTA Connect
