Publications US

ADA Title II and public pension plans: What the April 2026 deadline means for your digital services

Written by Heywood | 2/10/26 12:30 PM

If your public pension plan offers online member services (portals, benefit calculators, mobile apps, annual statements) the updated ADA Title II rule applies to you. The first compliance deadline is April 24, 2026, and for many plans, the gap between where they are today and where they need to be is significant.

The Department of Justice's 2024 update to Title II of the Americans with Disabilities Act sets WCAG 2.1 Level AA as the technical standard for all digital content and services provided by state and local government entities. That includes public pension and retirement plans.

This isn't a recommendation. It's a legal requirement with real enforcement consequences, including DOJ investigations, private lawsuits, and settlement costs that can run into the hundreds of thousands of dollars before you even factor in remediation.

Here's what pension plan administrators need to know, what to prioritize, and how to approach this practically.

Who needs to comply and by when

ADA Title II applies to any state or local government entity that provides digital services. For public pension plans, that means your member-facing tools (portals, online benefit statements, retirement calculators, mobile apps, and digital documents like PDFs) all need to meet WCAG 2.1 Level AA standards.

There are two compliance deadlines:

  • April 24, 2026 for entities serving populations of 50,000 or more
  • April 26, 2027 for smaller entities and special districts

These deadlines apply to the full digital experience, not just new tools in development. If your member portal went live five years ago and hasn't been tested for accessibility, it's still in scope.

What WCAG 2.1 Level AA actually requires

WCAG standards are organized around four principles: content must be perceivable, operable, understandable, and robust. In practice, for pension plans, this translates into specific requirements across your digital tools.

Screen reader compatibility: All content must work with assistive technologies. This means proper heading structures, meaningful alt text on images and charts, and correct labeling of form fields. Many pension portals fail here because they were built as visual-first experiences without semantic markup.

Keyboard navigation: Every function (logging in, running a benefit estimate, downloading a statement) must be fully accessible using only a keyboard. Drop-down menus, modal windows, and interactive calculators are common failure points.

Color contrast and text: Text must have a minimum contrast ratio of 4.5:1 against its background. Text must be resizable up to 200% without losing content or functionality. Pension statements that rely on color-coded charts or small-print tables often fall short here.

Captions and alternatives: Any video or audio content needs captions. Any time-based media needs transcripts or audio descriptions.

Forms and error handling: When a member makes an error on a form (entering an invalid date of birth, for example) the system must clearly identify the error and suggest how to fix it in an accessible way.

This is not an exhaustive list. WCAG 2.1 Level AA includes 50 individual success criteria. But these are the areas where pension plan digital tools most commonly fail.

Why pension plans face a bigger challenge than most

Most public-facing government services, like a city website or a library catalog, are relatively straightforward digital experiences. Pension plan member portals are different. They're data-heavy, personalized, and often built on legacy administration systems that were never designed with accessibility in mind.

Common problems include:

Legacy platforms: Many pension administration systems were built 10 or 15 years ago, when accessibility wasn't a development priority. Retrofitting accessibility into these platforms is expensive and often technically constrained by the underlying architecture.

Complex documents: Annual benefit statements, retirement projections, and plan summaries are frequently generated as PDFs from batch processes. These PDFs are rarely tagged for accessibility, making them effectively invisible to screen readers.

Third-party tools: If your plan uses a third-party calculator, document generator, or mobile app, you're still responsible for its accessibility. The DOJ rule explicitly covers digital content provided through contractual or licensing arrangements.

Personalized data: Pension portals display individualized financial information, including contribution histories, projected benefits, and survivor options. Ensuring this dynamic content is accessible adds complexity that static websites don't face.

What to do now: a practical approach

With the April 2026 deadline approaching, here's how to prioritize.

Start with an audit. Test your member portal, benefit calculators, mobile app (if you have one), and any documents you publish digitally against WCAG 2.1 Level AA. Use both automated scanning tools and manual testing with actual assistive technologies like screen readers. Automated tools catch roughly 30 to 40 percent of accessibility issues. Manual testing is essential for the rest.

Prioritize by member impact. You probably can't fix everything at once. Focus first on the journeys that matter most: logging in, viewing a benefit statement, running a retirement estimate, updating personal details, and contacting support. These are the services members rely on most, and they're where accessibility failures cause the most harm.

Assess your vendor. If you work with a pension administration or member engagement vendor, ask them directly: does your platform meet WCAG 2.1 Level AA? Can you provide a VPAT (Voluntary Product Accessibility Template) documenting your current compliance status? How are accessibility updates delivered, through regular release cycles, or do they require a separate project?

Plans that rely on vendors with modular, cloud-based platforms and regular release cycles will generally find it easier to maintain compliance over time. Platforms that bake accessibility into their development process, rather than treating it as a bolt-on, are better positioned to keep pace as standards evolve.

Don't forget documents and communications. Accessibility applies to more than your website. Benefit statements, annual reports, and member communications that are published digitally or sent electronically need to meet the same standards. Consider whether alternative formats, like personalized video explanations of benefit statements, might serve more members more effectively than static documents alone. We explore this area in more detail in our What modern pension communications requires in 2026 article. 

Build it into your roadmap. Accessibility isn't a one-off project. It needs to be part of how you develop, test, and release digital services going forward. Any new feature, any content update, any system change should be tested for accessibility before it goes live. Read Building a future-ready roadmap for pension software for more details around this.

Accessibility is a better member experience for everyone

The compliance deadline is real and the consequences of missing it are serious. But it's worth recognizing that accessibility improvements don't just serve members with disabilities. They make digital services better for everyone.

Clearer navigation, simpler language, well-structured content, and alternative formats for complex information all reduce friction. They reduce the volume of support calls from confused members. They improve engagement with digital tools. And they help more members actually understand their pension benefits, which is the point of providing these services in the first place.

Plans that have invested in accessible, modern member engagement tools consistently report higher engagement rates and fewer support queries. One approach that's gaining traction is personalized video, which can take complex benefit statement data and explain it in plain language, with built-in accessibility features including multilingual support and compatibility with assistive technologies.

How Heywood supports accessible pension services

At Heywood, accessibility is built into how we develop our pension technology platform and member engagement tools, not bolted on after the fact.

Our member engagement solutions, including Heywood Engage (our member portal) and Video Engage (our personalized video platform), are designed to meet WCAG accessibility standards. Video Engage is particularly relevant in the context of ADA Title II: it transforms complex benefit statement data into personalized, on-demand video experiences that members can access on any device, in any language. It's built with accessibility at its core, supporting members with visual impairments, learning differences, and limited familiarity with pension terminology.

The results speak for themselves: 88% of Video Engage users demonstrate a better understanding of their pension benefits, and plans using the tool have seen up to an 80% increase in engagement rates for active annual benefit statements.

If you're assessing your plan's readiness for ADA Title II, or if you want to understand how modern member engagement tools can help you meet compliance requirements while genuinely improving the member experience, we'd welcome the conversation.