Digital accessibility in the U.S. has always existed in a kind of fog. Everyone agrees it’s important, but the lingering question is simple: Does the ADA actually require my website or app to be accessible?

For years, that answer has depended on where you are and who you ask. Some courts say yes. Others hesitate. Agencies offer guidance but stop short of making it binding. For organizations trying to do the right thing, the result has been confusion—and a fair amount of frustration.

That may soon change.

H.R. 3417, known as the Websites and Software Applications Accessibility Act of 2025, is Congress’s latest effort to clear the air and make digital accessibility a matter of law, not interpretation. Let’s unpack what it aims to do, why it matters, and what steps you can take to prepare before it takes effect.

What the Bill Proposes

Introduced in May 2025 by Rep. Pete Sessions (R-TX), H.R. 3417 takes on something that’s been missing for far too long—a single, consistent standard for digital accessibility under the Americans with Disabilities Act.

It brings long-needed structure to how accessibility is defined and maintained online.

Under the bill:

• The Department of Justice (DOJ) would oversee regulations for Titles II and III, covering state and local governments as well as public accommodations.
• The Equal Employment Opportunity Commission (EEOC) would manage Title I, which is focused on employment.

Together, these agencies would be responsible for creating clear, enforceable rules—and updating them every three years so the law evolves alongside technology instead of chasing it.

Rooted in the POUR Principles

The framework builds on the four POUR principles that continue to shape accessibility standards worldwide:

• Perceivable: Information should reach people through more than one sense.
• Operable: Interfaces must respond to different types of input.
• Understandable: Content should be predictable, consistent, and easy to follow.
• Robust: It needs to work with assistive technologies—both now and as they advance.

These principles aren’t new, but their inclusion helps bridge the gap between policy and real-world design. It connects legislation to the human experience of using digital tools—the moments when clarity, contrast, and focus truly matter.

A Step Forward for Digital Inclusion

Advocacy groups, including the National Federation of the Blind and the American Council of the Blind, have voiced strong support for the bill. For many, it marks a long-awaited turning point—one that reinforces what accessibility professionals have long understood: inclusion isn’t limited to ramps and doorways. It belongs in every digital space where people work, learn, and live their daily lives.

Why H.R. 3417 Matters

When the ADA became law in 1990, the web wasn’t yet central to daily life. Today, nearly everything happens online—shopping, learning, applying for jobs, and even managing health care. Yet the law never clearly said how accessibility applies to the digital world.

Under Title III, businesses and nonprofits can’t discriminate. Yet there’s still no binding rule that defines what accessibility actually means for websites or apps. Courts have often relied on WCAG (Web Content Accessibility Guidelines) as a reference, but WCAG itself isn’t law. The result is a patchwork of interpretations and uneven enforcement.

H.R. 3417 would change that by replacing uncertainty with structure. It extends accessibility expectations to private businesses, nonprofits, and employment platforms—aligning them with the clarity already provided to public entities under the 2024 DOJ web rule for Title II.

It also ensures the right people are guiding the process. The bill requires an advisory committee—led primarily by individuals with disabilities—to help shape standards that work in real life, not just on paper.

What the Bill Would Do

At its core, H.R. 3417 says this: maintaining an inaccessible website or app would violate the ADA. No more gray zones. No more “we didn’t know.”

The DOJ and EEOC would create detailed accessibility standards—likely drawing from WCAG 2.2 Level AA or its successor—and require all covered entities to comply.

To make adoption realistic, the bill supports smaller organizations with grants up to $10,000, access to a technical assistance center, and longer compliance timelines—up to three years after the final rule takes effect.

It also preserves individuals’ right to sue if barriers remain. Courts could require fixes and award damages or attorney fees. To back it all, Congress plans to allocate $35 million per year for enforcement and oversight from 2026 through 2035.

Who’s Covered

• Employers and employment agencies (Title I)
• Public entities like state and local governments (Title II)
• Businesses, nonprofits, and testing providers (Title III)

That reach is broad—and that’s exactly the point. If you’re already subject to the ADA, your digital platforms will soon fall under the same expectations.

What H.R. 3417 Could Change

If passed, H.R. 3417 would finally give organizations a single, national rulebook for digital accessibility. It would eliminate the guesswork that’s led to years of inconsistent rulings and conflicting advice. For most organizations, that means a clearer sense of what compliance looks like—and how to plan for it.

It would also shift responsibility to where it belongs. For decades, people with disabilities have carried the burden of filing complaints and lawsuits to gain access. This bill would make accessibility an active obligation, not a reaction to litigation.

Of course, laws are only as strong as their enforcement. While the bill includes funding, it doesn’t yet specify how the DOJ or EEOC will prioritize or staff digital accessibility enforcement. Some expect a wave of early lawsuits—similar to what we saw with Section 508 and GDPR—but that initial pressure could drive lasting improvement.

The Act doesn’t explicitly address international harmonization either, though alignment with WCAG would naturally connect it to Europe’s EN 301 549 standard. That keeps global compliance more straightforward for companies working across borders.

The bottom line is that this bill sends a message that’s been coming for a long time—digital accessibility is no longer optional.

What Organizations Can Do Now

There’s no need to wait for the ink to dry—you can start preparing today.

Take a close look at your digital environment: your website, apps, internal portals, and documents. Ask the simple questions first. Can users navigate without a mouse? Are forms labeled clearly? Do videos include captions? Small discoveries today prevent bigger problems tomorrow.

Start With What Matters Most

Focus on the areas people use most—where they log in, fill out forms, or complete purchases. Fix the issues that stop someone from moving forward, like missing labels, alt text, or keyboard navigation.

Include Your Documents

PDFs and digital forms often get overlooked, but are a common source of frustration. Add proper tags, label form fields, and set a logical reading order. Once your templates are structured correctly, every new document follows suit.

Make Accessibility a Shared Effort

It’s not a job for one department. Developers, designers, content creators, and leadership all play a part. Build accessibility checks into your regular workflows and let people know how to report issues.

Collaborate With Your Vendors

Include accessibility expectations in contracts and RFPs. Ask for VPATs or accessibility documentation before new tools go live.

Keep Learning and Documenting

Train your team, stay informed about new regulations, and track your progress. A simple paper trail of audits, fixes, and training sessions shows commitment that goes beyond compliance.

When accessibility becomes part of your process—not a last-minute fix—it strengthens everything: your brand, your usability, and your connection with every user.

The End of Uncertainty—and the Start of Accountability

H.R. 3417 isn’t just another bill. It’s a signal that the era of uncertainty is ending. It tells organizations, large and small, that accessibility isn’t a nice-to-have—it’s a right.

Whether it passes this year or the next, the direction is clear. Start building accessibility into your workflow now, not later.

At 216digital, we see this as a turning point—one that rewards teams who act early and design with everyone in mind. If you’re ready to take the next step, consider scheduling an ADA briefing with our team. These sessions help organizations identify accessibility gaps, plan remediation, and prepare for compliance with confidence.

The web was built for all of us. This bill helps make sure it finally works that way.