This Rule Is Bigger Than Your Website: What Counts Under The New DOJ Accessibility Standards [Skip to content](#top) # News ## This Rule Is Bigger Than Your Website: What Counts Under The New DOJ Accessibility Standards June 4, 2026 ### Accessibility Isn’t Just About The Homepage ​For years, web accessibility sat in a frustrating gray area for many public-sector teams. Most people understood that digital access mattered, but accessibility isn’t just a website checkbox; it’s every digital service your business, organization, or agency provides.** The Americans with Disabilities Act has always applied online accessibility in some way, but for state and local governments, the question was often the same: What, exactly, are we required to do? The Department of Justice has now finally answered that question more directly. ​In April 2024, the DOJ finalized new guidance under Title II of the ADA, establishing clear and binding requirements for government web content and mobile applications. State and local governments must now ensure their web content and mobile applications meet WCAG 2.1 Level AA, with compliance deadlines beginning April 2027. This is not just a recommendation, but a regulatory rule with real deadlines, and it applies to more than just an organization’s homepage. This guide covers exactly what changed, who it applies to, what counts as in scope, and the practical steps every organization should take now. [Download a Copy of Our Web Accessibility Checklist](#anchor)   ### Does This Rule Apply To Your Organization? The ADA is structured across three key titles, each covering different types of organizations. Use this table to identify where your organization falls and what it means for your compliance obligations.   Organization Type ADA Title Compliance Deadline Enforcement Path State & local governments, public schools, special districts Title II April 2027 (large) / April 2028 (small) DOJ enforcement, investigations, complaint-driven Nonprofits & private organizations serving the public Title III No hard deadline Private lawsuits, settlements, DOJ action Private businesses open to the public Title III No hard deadline Private lawsuits, settlements, DOJ action Vendors & contractors providing digital platforms to government agencies Title II (tied to agency obligation) Tied to agency deadline Agency contract compliance, procurement requirements   Regardless of which category you fall into, WCAG 2.1 Level AA is the de facto standard across all ADA enforcement, for both formal government deadlines and the benchmarks courts reference in private litigation.   DOJ Accessibility Standards: What’s In Scope  - Websites  - Mobile Apps  - PDFs & Documents  - Online Forms  - Payment Portals  - Videos   What The DOJ Changed In April 2024** The[DOJ’s April 2024 update](https://www.ada.gov/resources/2024-title-ii-final-rule/) to Title II of the ADA established specific, enforceable technical standards for digital accessibility. Where guidance was once vague, there is now a clear baseline: state and local governments must ensure their web content and mobile apps meet[WCAG 2.1 Level AA](https://www.ada.gov/resources/2024-03-08-web-rule/). WCAG 2.1 Level AA is the internationally recognized standard for making digital content accessible to people with disabilities. It covers readable text, keyboard navigation, sufficient color contrast, and alt text for images. It is the benchmark for ADA compliance, and the standard courts consistently reference in private-sector litigation. While this update is specific to state and local governments under Title II, it reflects a broader shift across the ADA. Private businesses and nonprofits are still expected to provide accessible digital experiences, with WCAG 2.1 Level AA widely used as the standard. In practice, expectations are becoming more consistent across all organizations.   **Where guidance was once vague, the 2024 rule makes four things explicit:** - The obligation fully extends to the digital realm: websites, apps, documents, forms, portals, and more. - Third-party platforms and vendor-managed tools are included if used to deliver public services. - Compliance deadlines are now firm, tiered by entity size. - Enforcement is increasing across all sectors: government entities, private businesses, and the vendors who serve them.     **Before April 2024** **After April 2024** **Standards** Vague ADA obligations online Specific WCAG 2.1 Level AA requirement **Technical baseline** No defined technical standard Clear scope: web, apps, docs, forms, portals **Enforcement** Inconsistent enforcement Hard compliance deadlines by entity size **Scope** Unclear definition of “digital services” Third-party content included if used for services **Vendors** Third-party vendor responsibility ambiguous Defined expectations with specific criteria   **Deadlines By Entity Size: Know Your Date ** The DOJ built [a tiered compliance timeline into the rule](https://www.ada.gov/resources/2024-03-08-web-rule/), giving larger entities an earlier deadline and allowing smaller entities and special districts more time. Don’t wait until the deadline is imminent, as accessibility remediation takes time, especially for organizations with larger volumes of existing content.    ![](https://liquifiedagency.com/wp-content/uploads/2026/06/In-content-600x600-1.png) While these specific deadlines apply to government entities under Title II, private businesses and nonprofits under Title III do not have a formal compliance deadline. However, they are still required to provide accessible digital experiences, and enforcement through lawsuits and settlements is ongoing, making proactive compliance just as important. ** **   **What Counts As Digital Content Under This Rule ** The DOJ’s 2024 rule’s scope is broad by design. It’s not limited to your main website; it covers every digital touchpoint a person must use to access, apply for, or participate in your services, programs, or activities. This applies whether those services are delivered by a government agency, a nonprofit, or a private business.   **Content Type** **Why It’s In Scope** **Real-World Example** **Websites** Primary channel for service access City homepage, business service portal, nonprofit landing page **Mobile Apps** Explicitly named in the rule alongside web content Utility billing app, park reservations, customer account apps **PDFs & Documents** Used to apply for or access services Permit applications, benefit forms, downloadable contracts **Online Forms** Core pathway for service access License renewal, service requests, customer intake forms **Payment Portals** Part of a complete service transaction Utility bill payment, permit fees, online checkout **Videos** Required to include captions and audio descriptions Public meeting recordings, product demos, instructional content **Public-Facing Workflows** Any multi-step process to access programs or services Benefits enrollment, housing applications, account setup   For government entities, essential services in scope include: applying for healthcare coverage or benefits, housing assistance, unemployment support, tax filing, education enrollment, public safety reporting, and voting information. For private organizations, the same principle applies: if a digital touchpoint determines whether someone can access your service, it falls under ADA expectations.   **Third-Party Content And Vendor Responsibility** One of the most important, and most misunderstood, aspects of this rule is how it applies to third-party content. Many organizations assume that if a vendor builds or manages a platform, accessibility becomes the vendor’s responsibility. [That assumption is incorrect.](https://www.ada.gov/resources/web-guidance/) For government entities, Under Title II, public entities remain responsible for accessibility compliance even when digital content is created, hosted, or maintained by a third-party vendor, as long as that content is used to deliver public services. Outsourcing does not transfer accountability. For vendors and contractors, if your platform powers government-facing services, accessibility is now a procurement requirement. Agencies are required to verify that your product meets WCAG 2.1 Level AA and to hold you contractually accountable. Being able to demonstrate compliance is a meaningful competitive differentiator in the public-sector market. In practice, this means accessibility cannot be treated as an afterthought. It needs to be built into procurement and contracting from the start. The DOJ recommends working with accessible vendors and including clear accessibility requirements in contracts to ensure compliance across all digital services.   **What Government Entities Should Ask Vendors** - Does your platform meet WCAG 2.1 Level AA standards? - Can you provide documentation or proof of accessibility testing? - How often do you audit your content for accessibility compliance? - How do you handle user-reported accessibility issues? - Are accessibility requirements included in your standard contract or terms of service?   **What Vendors and Contractors Should Be Ready to Demonstrate** - A current Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR) - Documentation of manual and automated accessibility testing - A defined process for triaging and resolving reported accessibility issues - A named contact or team responsible for accessibility compliance - Evidence that accessibility is part of your ongoing development cycle, not a one-time audit   **Understanding WCAG 2.1 Level AA In Plain English** The WCAG (Web Content Accessibility Guidelines) is the internationally recognized standard for making digital content usable by people with disabilities.[Version 2.1 Level AA is the baseline that the DOJ rule requires](https://www.ada.gov/resources/2024-03-08-web-rule/). It’s organized around four core principles, often abbreviated as POUR.   **Principle ** **What it means** **Practical examples ** **Perceivable** Content must be presentable to users in ways they can perceive  Alt text on images; captions on videos; sufficient color contrast **Operable** Users must be able to navigate and interact with all functions Full keyboard navigation; no time traps; skip-navigation links  **Understandable ** Information and interface operation must be clear and predictable  Form error messages; consistent navigation; readable language  **Robust** Content must work reliably with assistive technologies  PDFs readable by screen readers; semantic HTML structures   ### **Exceptions And Common Misconceptions** While the rule does include some exceptions, they are narrower than many teams expect. These apply primarily to Title II government entities, though the underlying principles are instructive for any organization assessing scope.   ![](https://liquifiedagency.com/wp-content/uploads/2026/06/In-content-600x700-2.png)   **Why Compliance Matters (Beyond The Law)** It’s easy to think of accessibility as a legal requirement, but it’s really about delivering better digital services. Features like clear form labels, strong color contrast, and keyboard navigation[improve usability for everyone](https://www.w3.org/WAI/fundamentals/accessibility-intro/), not just people with disabilities. Accessibility isn’t an add-on or a checkbox; it’s a foundation of[modern digital experiences](https://digital.gov/topics/usability/). It also directly impacts public trust.[Inaccessible services signal exclusion](https://www.ada.gov/resources/web-guidance/), while accessible ones show that your organization is building for everyone who relies on them. This expectation is expanding beyond government; Vendors, nonprofits, and partners supporting public entities under Title II are increasingly expected to meet WCAG 2.1 Level AA, as the DOJ’s 2024 rule extends accessibility requirements to third-party digital platforms used by government agencies.     **What Happens If You Miss the Deadline?** [There are no automatic fines the moment a deadline passes](https://www.ada.gov/file-a-complaint/). Enforcement is typically complaint-driven, meaning action is usually triggered if someone files a complaint or the DOJ initiates an investigation. Most cases allow time for organizations to fix issues, and penalties are often[reduced or avoided through good-faith efforts.](https://www.ada.gov/resources/web-guidance/) The most important step is to show progress. Having an accessibility statement, documenting improvements, and maintaining a clear plan can significantly reduce risk, even if full compliance isn’t complete yet. The consequences differ by organization type, but the risk is real across the board.   **Organization Type** **Primary Risk** **What Mitigates It** **Government entities (Title II)** DOJ enforcement actions, investigations, consent decrees Documented plan, accessibility statement, demonstrated progress **Private businesses & nonprofits (Title III)** Private lawsuits, serial litigation, settlement costs Proactive WCAG compliance, documented remediation efforts **Vendors & contractors** Lost contracts, failed procurement, reputational damage VPAT documentation, accessibility testing, defined remediation process   ### **Practical First Steps ** The path to compliance doesn’t have to be overwhelming. Start with high-impact actions that address your most-used services first, then build toward broader coverage over time. - **Create a dedicated accessibility page**** **Publish a page that outlines your commitment to accessibility, the standards you’re working toward (WCAG 2.1 Level AA), any known limitations, and a clear way for users to report issues. This is a simple, high-impact step that demonstrates good faith and helps reduce risk.   - ** Run automated accessibility scans**** **Use tools like WAVE or axe DevTools to quickly identify common issues such as low color contrast, missing alt text, and form errors. While these tools don’t catch everything, they’re an efficient way to surface and prioritize key fixes.   - ** Prioritize high-impact pages and services**** **Focus on the pages residents rely on most—online forms, payment portals, applications, and permit processes. Improving these areas delivers the greatest impact and addresses the highest-risk gaps first.   - ** Audit your vendor contracts**** **Government entities: Review agreements with any vendor providing digital services. Ensure accessibility requirements are included and request testing documentation.** Vendors and contractors: Prepare your VPAT and define your remediation process now. Agencies are already asking — being able to answer confidently is a meaningful competitive advantage. - Train your staff and build ongoing practices**** **Accessibility isn’t a one-time effort. Equip content managers, communications teams, and developers with the basics, and build accessibility checks into your regular publishing and update workflows.  **Budget Considerations:** Initial costs typically include: accessibility audits (automated and manual), website and app remediation, document remediation for high-traffic content, staff training, and vendor contract reviews. Ongoing costs include: regular audits, content updates, training refreshers, and vendor accountability monitoring. When approached strategically, these investments strengthen the overall quality and usability of your digital services, not just your compliance posture. Still not sure where to start? Download our Accessibility Readiness Checklist to quickly assess where you stand and identify the next steps to move forward with confidence.   **Start Now, Build Forward** The DOJ’s updated rule makes one thing clear: accessibility is no longer optional, and it’s far bigger than your website alone. It touches every digital interaction your organization offers, from forms and payments to applications and essential public services. The good news is that compliance doesn’t require perfection on day one. What matters most is starting with a clear plan, prioritizing high-impact areas, and demonstrating consistent progress. If you’re ready to take the first step, download Liquified’s Accessibility Readiness Checklist to quickly assess where you stand and identify immediate opportunities for improvement. And if you’re looking for a partner to help navigate requirements, prioritize efforts, and implement accessible digital experiences at scale, Liquified is here to help. ## **Frequently Asked Questions: ADA Digital Accessibility**   ### **For Government Entities** **What is the compliance deadline for DOJ Title II digital accessibility?** The deadline is April 24, 2027 for public entities serving populations of 50,000 or more. Smaller entities and special district governments have until April 26, 2028. The required standard is WCAG 2.1 Level AA across web content, mobile apps, documents, forms, and third-party platforms used to deliver services. **Does the DOJ ADA rule apply to third-party vendors we use?** Yes. If a vendor’s platform is used to deliver public services, your organization is still responsible for ensuring it meets WCAG 2.1 Level AA. Outsourcing does not transfer legal accountability. Accessibility requirements should be built into procurement and vendor contracts from the start. **Are old PDFs and archived documents covered by the rule?** Preexisting documents are exempt only if they are not used to access current services. If residents actively rely on a PDF to apply for a benefit, renew a permit, or complete any process, it is in scope. Archived content is exempt only if created before the compliance date, stored in a labeled archive, and not modified since. **What happens if we don’t meet the government compliance deadline?** There are no automatic fines at the deadline. Enforcement is complaint-driven. However, organizations that receive complaints with no documented accessibility plan face significantly greater risk than those who can show good-faith progress. DOJ investigations, consent decrees, and reputational impact are real consequences of inaction.   ### **For Private Businesses and Nonprofits** **Does ADA digital accessibility law apply to private businesses?** Yes. Title III of the ADA requires private businesses and nonprofits that serve the public to provide accessible digital experiences. While there is no formal compliance deadline like the government’s Title II rule, private ADA lawsuits targeting inaccessible websites and apps have increased sharply in recent years. WCAG 2.1 Level AA is consistently referenced as the standard in court decisions and settlements. **What is the legal risk for private organizations that aren’t ADA compliant?** The primary risk is private litigation. Serial plaintiffs and disability advocacy organizations actively file ADA accessibility lawsuits against businesses with inaccessible websites, e-commerce platforms, booking systems, and customer portals. Settlement costs, legal fees, and remediation requirements are common outcomes. Organizations with documented accessibility efforts consistently receive more favorable results. **What does WCAG 2.1 Level AA mean for a private business?** It means your website, app, and digital tools should be navigable by keyboard, include alt text on images, provide captions on videos, maintain sufficient color contrast, and work reliably with screen readers. These aren’t just legal requirements — they improve usability for all users and expand your addressable audience.   ### **For Vendors and Contractors** **If I’m a vendor providing a platform to a government agency, am I responsible for accessibility?** Shared responsibility. The government agency is ultimately accountable under Title II — but agencies are required to ensure their vendors meet WCAG 2.1 Level AA through procurement requirements and contract language. In practice, your platform’s accessibility directly affects whether agencies can contract with you, renew agreements, or expand your relationship. **What documentation should a vendor have ready for government procurement?** At minimum: a current Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR), documentation of both automated and manual accessibility testing, a defined issue resolution process, and evidence that accessibility is part of your ongoing development cycle. Being prepared to answer these questions confidently is a meaningful differentiator in public-sector sales.   ### **General** **What is WCAG 2.1 Level AA?** WCAG 2.1 Level AA (Web Content Accessibility Guidelines) is the internationally recognized standard for digital accessibility. It requires that web content be Perceivable, Operable, Understandable, and Robust — covering alt text, keyboard navigation, captions, color contrast, and screen reader compatibility. It is the specific technical standard the DOJ rule requires for government entities, and the benchmark courts reference in private ADA litigation. **What digital content is exempt from ADA accessibility requirements?** For government entities, exemptions include: archived content not used for current services (clearly labeled and unmodified), preexisting social media posts made before the compliance date, and individualized documents secured behind a login. These exemptions are narrow. For private organizations, there are no formal exemptions — but courts generally consider good-faith remediation efforts and documented progress when determining outcomes.   ![](https://liquifiedagency.com/wp-content/uploads/2026/06/checklist.png) <<>> [ALL Articles](/news) ACTIVELY STALK US <<>> Copyright © 2006 - 2026 Liquified Agency