This article is based on real-world guidance from UsableNet’s work with public sector organizations preparing for ADA Title II digital accessibility requirements now in effect.
The deadline has arrived—and most organizations are not fully prepared
As of April 2026, ADA Title II requires many public entities to provide accessible digital content.
This is not a future requirement. It is an active compliance obligation.
ADA Title II compliance is no longer measured by whether your website works—it is measured by whether users can complete real tasks independently.
Most organizations will not be fully compliant today. That alone is not the primary risk.
The real risk is operating without a clear, documented plan to address accessibility gaps.
Key Takeaways
- ADA Title II digital accessibility requirements are now in effect for many public entities
- WCAG 2.1 Level AA is the required compliance standard
- Accessibility obligations extend to vendors, apps, and social media
- Automated testing alone identifies only a portion of accessibility issues
- Organizations must act proactively, not in response to complaints
Common Misconceptions About ADA Title II
Many organizations are still operating under outdated assumptions about what ADA Title II requires.
Myth: “We just need to make our website accessible.”
Reality: ADA Title II applies to websites, mobile apps, social media, and third-party tools—not just your homepage.
Myth: “Our vendor handles accessibility.”
Reality: If a vendor supports your services, your organization remains responsible for ensuring that content and functionality are accessible.
Myth: “We can wait for a complaint before acting.”
Reality: ADA Title II requires proactive accessibility. Waiting for a request or complaint is not a compliant approach.
Myth: “Existing content is automatically exempt.”
Reality: Limited exceptions exist, but many types of content still require review, evaluation, and documentation to determine whether they meet accessibility requirement
Digital accessibility is now an explicit legal requirement
ADA Title II has always required equal access to programs and services.
What has changed is this:
Digital accessibility is now explicitly defined and enforceable.
Public entities must ensure accessibility across:
- Websites
- Mobile applications
- Online services such as payments and applications
- Digital content delivered through third parties
If a user cannot complete a transaction independently, the experience is not compliant.
Vendor tools are a major source of hidden risk
Many accessibility gaps originate from third-party tools.
Payment systems, scheduling platforms, and other vendor-provided services are often unaudited and assumed to be compliant.
Every unaudited vendor tool is an open, unquantified exposure.
If vendor tools are not audited, the organization still carries the liability.
If it is part of your service delivery, it is part of your compliance obligation.
Not everything must be fixed immediately—but everything must be evaluated
The scope of accessibility can feel overwhelming, especially for large organizations.
The regulations include limited exceptions, such as:
- Archived content
- Pre-existing documents created before the deadline
- Certain individualized, secured documents
However, these are not shortcuts.
If you rely on an exception, you must formally document and justify that decision.
Compliance is not about perfection overnight. It is about making informed, defensible decisions.
Prioritization is the most important step right now
Trying to fix everything at once is not realistic.
Organizations need to focus on:
- Core public services (payments, applications, benefits access)
- High-impact user journeys
- Frequently used digital content
If users cannot complete essential tasks, you already have a meaningful accessibility risk.
A scan report is not a defense
Automated tools are useful, but incomplete.
They typically identify only a portion of accessibility issues. Many WCAG requirements require manual validation using assistive technologies.
A scan catches only a fraction of accessibility barriers. The majority of issues require manual testing and real user validation.
An accessibility audit that relies only on automated testing is not sufficient for compliance.
Waiting for complaints is not compliant
A reactive approach does not meet ADA Title II requirements.
Organizations cannot wait for:
- complaints
- accommodation requests
- user feedback
If accessibility is addressed only after complaints, the organization is already out of step with ADA Title II requirements.
What enforcement risk actually looks like
Non-compliance can lead to:
- Department of Justice investigations
- Legal action by private parties
- Court orders requiring remediation
- Responsibility for attorney’s fees
These outcomes are not theoretical. Legal activity around digital accessibility continues to evolve, with enforcement coming from both regulators and private parties.
Enforcement does not require full non-compliance—failure to demonstrate a defensible accessibility program can be enough to trigger risk.
What a defensible accessibility program looks like
At this stage, public entities should be able to demonstrate:
- A documented accessibility roadmap with clear priorities and timelines
- Defined ownership across departments
- Ongoing audits that include manual testing
- Training for teams managing digital content
- Vendor requirements for WCAG conformance and accessibility documentation
- Written justification for any exceptions or limitations
A documented, ongoing accessibility program is required to maintain compliance as digital services evolve, including prioritizing remediation and maintaining accessibility across releases.
Accessibility is now an operational requirement, not a one-time project.
Common Questions
What standard is required right now?
WCAG 2.1 Level AA is the required standard for ADA Title II digital accessibility compliance.
How should we approach accessibility testing?
Accessibility testing should combine automated tools with manual validation using assistive technologies. Automated testing helps identify common issues at scale, but manual testing is required to evaluate usability and real user workflows. This combined approach creates a more complete and defensible record of accessibility efforts.
What if we are not fully compliant today?
Most organizations are not fully compliant today. The priority should be to establish a documented plan, define clear priorities, and demonstrate ongoing progress in addressing accessibility gaps.
Are third-party tools included?
Yes. If third-party tools support your services, they must meet accessibility requirements. The responsibility for accessibility remains with your organization, even if a vendor provides the technology.
Do we need to make all content accessible?
Not necessarily. Certain archived or pre-existing content may qualify for limited exceptions, but these cases must be evaluated carefully and documented. Organizations are still expected to provide accessible access to services to the maximum extent possible.
Final Thought
ADA Title II compliance is no longer a future initiative. It is a current operational requirement.
The organizations in the strongest position today are not the ones that are finished. They are the ones that can clearly show what they are doing next—and why.
Take the Next Step
If you’re evaluating your current accessibility risk or need to build a defensible plan, our team can help.
Contact UsableNet to assess your digital properties, prioritize remediation, and implement a sustainable accessibility program.
