The April 24, 2026 deadline for government website accessibility compliance under ADA Title II has passed. For state and local government agencies, public universities, school districts, and special districts, this is no longer a future planning exercise. It is a present legal obligation with active enforcement consequences.
This guide answers 56 questions that government IT directors, ADA coordinators, legal teams, and web managers are actively searching for right now. Questions are organized by where your agency is in the compliance journey, from understanding whether the deadline is real to building a sustainable ongoing compliance program.
Every answer is written to be direct, accurate, and actionable. This is an informational guide and does not constitute legal advice. Consult qualified legal counsel for guidance specific to your agency’s situation.
Section 1: Is the Deadline Even Real?
Key Insight
The April 24, 2026 deadline remains federal law as of publication. An Interim Final Rule was submitted to OIRA in February 2026 but has not been published. Private ADA web lawsuits were filed 8,667 times in 2025 before any federal deadline existed. Do not pause compliance work based on rumour or speculation.
Q01. Is the April 24, 2026 ADA web accessibility deadline still legally in effect?
Yes. The deadline remains federal law. The DOJ submitted an Interim Final Rule (IFR) to the Office of Information and Regulatory Affairs (OIRA) in February 2026 that could modify the rule, but as of publication, nothing has been officially published or changed in the Federal Register. Until a revised rule is published, the April 24 deadline for entities serving populations of 50,000 or more is legally binding.
The underlying legal obligation under the ADA has existed since 1990. The 2024 rule defined the technical standard. Rescinding the rule would not eliminate the underlying obligation.
| Entity type | Compliance deadline | Population basis |
|---|---|---|
| State/local governments, public universities, public schools | April 24, 2026 | Serving 50,000 or more (2020 Census) |
| State/local governments, public universities, public schools | April 26, 2027 | Serving fewer than 50,000 |
| Special districts (water boards, transit, library districts) | April 26, 2027 | All special districts regardless of size |
Q02. What is an Interim Final Rule, and could it delay or cancel the April 2026 ADA deadline?
An IFR is a regulatory mechanism that allows an agency to modify rules without the standard public comment period. The DOJ submitted one to OIRA in February 2026, unprecedented for an accessibility regulation. If published, it could delay the deadline or alter technical requirements. As of today, none has been published. Major disability rights organizations are actively opposing any modifications.
An IFR that modifies the technical rule does not eliminate the ADA’s underlying requirement that government services be accessible to people with disabilities. That obligation has existed since the ADA was passed in 1990.Q03. If the federal ADA web rule is rescinded, does our agency still have to make its website accessible?
Yes. Three parallel legal pressures remain regardless of the federal rule’s status:
- Private lawsuits under ADA Title II can be filed independently of the technical rule. Federal courts have applied WCAG as the de facto accessibility standard in government website cases since at least 2015.
- State laws in Colorado, Minnesota, California, and New York enforce their own requirements independently, with their own financial penalties.
- Section 504 of the Rehabilitation Act applies to all agencies receiving federal financial assistance, separately from ADA Title II.
Q04. Can we pause our accessibility work while the DOJ rule is under review?
No. Pausing is one of the highest-risk decisions an agency can make in 2026. Three reasons:
- Private lawsuits do not pause. 8,667 ADA web accessibility lawsuits were filed in 2025 before any federal deadline was in effect, according to UsableNet’s annual ADA lawsuit tracking report.
- State laws continue enforcing independently of the federal rule.
- If the federal deadline holds, agencies that paused will have no documented good-faith effort, which is the primary mitigating factor in DOJ enforcement decisions.
Q05. If the federal deadline is delayed, do state accessibility laws still apply to us?
Yes. Several states enforce their own digital accessibility laws independently of the federal rule. Federal delay or rescission does not affect these obligations.
States with active enforcement and financial penalties:
- Colorado: HB21-1110 has been enforcing since July 2024. Penalty: $3,500 per violation, payable directly to the plaintiff. Enforced through state courts.
- Minnesota: Statutes 363A.42 and 363A.43 have been enforcing since 2013. Penalty: $500 per violation plus attorney fees. Updated to WCAG 2.1 AA in July 2024. Following August 2024 amendments, courts may also award unlimited punitive damages.
- California: The Unruh Civil Rights Act allows $4,000 per violation and applies to government websites.
- New York: State agencies have been required to conform to WCAG standards since 2019. Residents can sue under state civil rights law. New York ranks first nationally for ADA web accessibility lawsuit filings.
State law coming into effect soon:
- New Mexico: HB295 requires WCAG 2.1 AA compliance for all state agencies by April 1, 2027.
Q06. Private ADA lawsuits were filed 8,667 times in 2025. Can citizens sue us even without a federal deadline?
Yes. Private lawsuits under ADA Title II exist independently of the DOJ technical rule. Courts have consistently held that government websites must be accessible under the ADA. Even if the federal rule is modified, plaintiff attorneys continue filing. AI-assisted complaint drafting has accelerated the pace significantly. The average total settlement cost exceeds $75,000 before legal fees and mandatory monitoring requirements are included.Section 2: What Actually Happens to Us?
Key Insight
The average ADA web accessibility settlement exceeds $75,000, not counting legal defense costs or mandatory monitoring. Civil penalties in DOJ-initiated enforcement can reach $150,000 for repeat violations. Starting remediation now costs a fraction of defending a complaint.
Q07. What are the actual penalties for a government agency that misses the ADA web compliance deadline?
Non-compliance can result in several consequences:
| Consequence | Triggered by | Typical outcome |
|---|---|---|
| DOJ investigation | Complaint from resident or DOJ-initiated review | Voluntary negotiation, then consent decree if unresolved |
| Private lawsuit | Individual plaintiff or plaintiff law firm | Settlement averaging $75,000+ including legal fees |
| Consent decree | Failed voluntary negotiation with DOJ | Multi-year federal oversight with compliance reporting |
| Federal funding risk | Section 504 enforcement by funding agency | Funding conditions or suspension |
| Civil penalties | DOJ-initiated litigation | Up to $75,000 first violation, $150,000 repeat |
Actual penalties are discretionary. Agencies with documented good-faith compliance effort are consistently treated more leniently in enforcement decisions.
Q08. Can we be sued for an inaccessible website even if the DOJ never contacts us?
Yes, and this is where many agencies underestimate their exposure. Private lawsuits under ADA Title II operate entirely independently of DOJ enforcement. Plaintiffs cannot recover monetary damages under the federal ADA, but they can recover attorneys fees and legal costs, making these cases financially viable for plaintiff firms that file them at scale.
Settlements typically require mandatory remediation timelines, accessibility monitoring requirements, and legal fee reimbursement. Average total cost: $75,000 or more. The DOJ never needs to be involved for a complaint to cost your agency six figures.Q09. How does a DOJ investigation into a non-compliant government website actually work?
Most investigations start with a complaint from a resident encountering access barriers. The typical process:
- DOJ notifies the agency and requests information about its digital content.
- DOJ attempts resolution through voluntary negotiation before pursuing legal action.
- If negotiation fails, the DOJ may enter a consent decree or file suit in federal court.
- Agencies under consent decrees must report compliance progress to the DOJ at regular intervals.
Q10. Does ADA web non-compliance affect our federal funding or Section 504 obligations?
Yes. Agencies receiving federal financial assistance must also comply with Section 504 of the Rehabilitation Act, enforced by the relevant funding agency such as HHS or the Department of Education. Non-compliance can trigger separate investigations and funding conditions. WCAG 2.1 Level AA compliance satisfies both ADA Title II and Section 504 digital accessibility requirements simultaneously, so a single remediation effort addresses both obligations.Q11. What is a consent decree, and could our agency end up under one?
A consent decree is a court-approved agreement between the DOJ and your agency specifying required corrective actions, timelines, and ongoing federal oversight. Consent decrees are binding and can last several years, requiring regular compliance reports to the DOJ. They are typically the outcome when voluntary compliance fails. Historical examples include agreements with state agencies, transit authorities, and public universities across the country. They are a real enforcement tool, not a theoretical one.Q12. What is the average cost of an ADA web accessibility lawsuit or settlement for a government agency?
According to UsableNet’s annual ADA lawsuit tracking, the average ADA web accessibility settlement exceeds $75,000. That figure excludes legal defense costs, mandatory remediation expenses, and the ongoing monitoring requirements that settlements typically impose. One public school district case estimated total costs of $665,000 to $815,000 when remediation, legal fees, coordinator hiring, and staff training were all included. Proactive remediation is substantially cheaper than reactive settlement in every size category.Q13. Does a complaint have to be filed for the DOJ to investigate us, or can they initiate on their own?
Both are possible. The vast majority of DOJ investigations begin with complaints from residents who encounter access barriers. The DOJ can also initiate compliance reviews independently, particularly targeting entities with known or widespread failures. Complaint-driven investigations are far more common in practice. Every resident who encounters an access barrier on your site is a potential enforcement trigger.Need compliance help now?
Schedule a free consultation with our government accessibility specialists.
Schedule Free ConsultationSection 3: Does This Apply to Our Agency?
Key Insight
Your deadline is determined by the parent jurisdiction population from the 2020 Census, not your department size, headcount, or the number of people you serve. A library branch serving 3,000 patrons uses its county population. A university with 40,000 students uses the state population.
Q14. Does the 50,000 population threshold apply to our department or the parent government entity?
It applies to the parent entity, not your department. The population used is not your office headcount, the number of people you serve, or your program enrollment. It is the parent government jurisdiction population from the 2020 decennial Census. According to ADA.gov’s official rule guidance:
- A small parks department with 10 employees is covered by its city or county population.
- A branch library serving 3,000 patrons uses its county population figure.
- A university with 40,000 students uses the state population, not enrollment.
Q15. Our institution serves fewer than 50,000 people but is part of a larger jurisdiction. Which deadline applies?
The larger jurisdiction deadline applies. If the county you belong to has 200,000 residents, your deadline is April 24, 2026, regardless of how many people your specific branch, office, or program directly serves. The parent jurisdiction Census population is the controlling figure. This surprises many smaller departments and sub-agencies who assume their small service footprint places them in the later deadline category.Q16. Are special districts, including water boards, transit authorities, and library districts, covered under ADA Title II?
Yes. Special districts are explicitly covered under ADA Title II. However, they have a separate compliance deadline: April 26, 2027, regardless of population size. The DOJ granted all special district governments the 2027 deadline because the Census Bureau does not calculate separate populations for them. The compliance standard is identical: WCAG 2.1 Level AA. The 2027 deadline is a later start, not an exemption from the requirement.Q17. Does ADA Title II cover our mobile app and online portals, or just our main website?
Both websites and mobile applications are covered. The rule applies to any digital product used to deliver government programs, services, or activities. This includes:
- Citizen portals and self-service dashboards
- Online permit, license, and registration applications
- Payment systems and fee portals
- Dedicated mobile apps for government services
Q18. Does ADA Title II apply to our internal staff systems and intranet, or only public-facing content?
Primarily public-facing content. The rule focuses on services, programs, and activities provided to the public. Internal HR systems, staff intranets, and employee-only tools are not the primary target of the 2024 rule. The ADA’s general employment provisions still apply to employee-facing tools in a broader sense, but for this specific compliance deadline, focus your effort first on anything a citizen can access.Q19. How do we calculate our jurisdiction population for the ADA deadline using the correct Census data?
Use the 2020 decennial Census population for your state or local government. Two exceptions apply:
- Independent school districts use the 2022 Small Area Income and Poverty Estimates instead of Census data.
- Entities without their own Census population use the parent government Census figure.
Section 4: What Do We Need to Fix?
Key Insight
Section 508 compliance does NOT satisfy ADA Title II. Section 508 references WCAG 2.0; ADA Title II requires WCAG 2.1, which adds 12 new success criteria. Government websites average 307 WCAG violations per page according to AudioEye’s Government Accessibility Report.
Q20. We are already Section 508 compliant. Does that satisfy the ADA Title II WCAG 2.1 requirement?
Not fully. This is one of the most dangerous misconceptions in government IT. Section 508 references WCAG 2.0 Level AA. ADA Title II requires WCAG 2.1 Level AA. WCAG 2.1 adds 12 new success criteria beyond WCAG 2.0, covering:
- Mobile accessibility and touch interactions (Success Criteria 2.5.1 through 2.5.4)
- Orientation lock requirements (1.3.4)
- Input purpose detection for form fields (1.3.5)
- Updated contrast requirements for non-text content such as icons and UI components (1.4.11)
If your Section 508 compliance was achieved against WCAG 2.0, you have a real gap. Review those 12 additional criteria before assuming you are covered.
| Level | Success criteria | Status under ADA Title II |
|---|---|---|
| Level A | 30 criteria (basic requirements) | Required: minimum baseline |
| Level AA | 20 additional criteria (most impactful barriers) | Required: ADA Title II mandate |
| Level AAA | 28 additional criteria (highest standard) | Not required |
| WCAG 2.0 AA | Covered by Section 508 since 2018 | Does NOT satisfy ADA Title II: missing 12 criteria |
| WCAG 2.1 AA | 50 criteria total (A + AA) | Required under DOJ 2024 rule |
| WCAG 2.2 AA | Backwards compatible with 2.1 | Not required but future-proofs your site |
Q21. What is WCAG 2.1 Level AA, and what is the difference between Level A, AA, and AAA?
WCAG 2.1, published by the World Wide Web Consortium (W3C), is the international standard for web accessibility. It is built on four principles known as POUR: Perceivable, Operable, Understandable, and Robust.
- Level A: 30 basic criteria covering the absolute minimum accessibility requirements.
- Level AA: 20 additional criteria addressing the most common and impactful barriers. This is the ADA Title II legal requirement.
- Level AAA: The highest tier, often impractical for general government websites and not required under the rule.
Q22. What are the most common WCAG failures on government websites right now?
Government websites average 307 WCAG violations per page. The most common failures found consistently across government site audits are:
- Missing or inadequate image alt text
- Unlabeled form fields and submit buttons
- Insufficient color contrast (minimum 4.5:1 ratio required for normal text under WCAG 1.4.3)
- Videos without closed captions or audio descriptions
- Keyboard navigation failures in menus, modals, and dropdowns
- PDFs with no accessible tagging or logical reading order
- Missing skip navigation links
- Broken heading hierarchy across pages
Q23. Is WCAG 2.2 required, or is WCAG 2.1 still the official ADA Title II standard?
WCAG 2.1 Level AA is the legal requirement under the DOJ 2024 rule. WCAG 2.2, published by the W3C in October 2023, is backwards compatible, meaning WCAG 2.2 conformance automatically satisfies all WCAG 2.1 requirements. If you are starting a remediation project now, building to WCAG 2.2 future-proofs your site without significant additional effort and positions your agency ahead of any future rule updates.Q24. Do our PDFs, Word documents, and online forms need to meet WCAG 2.1 too?
Yes, with limited exceptions. Any document that delivers a government service or program must be accessible. Scanned image-only PDFs are particularly problematic: they require OCR processing and accessibility tagging to be readable by screen readers. Prioritize documents for your highest-traffic services: permit applications, benefit enrollment forms, public notices, and meeting agendas.
Pre-existing documents created before your compliance deadline may qualify for an exception under specific conditions covered in Section 6. New documents published after your deadline must comply without exception.Q25. Do our embedded videos and multimedia content need captions and audio descriptions?
Yes. Video is consistently the most-failed WCAG criterion on government websites. Requirements by content type:
- Pre-recorded videos require closed captions and audio descriptions (WCAG 1.2.3 and 1.2.5).
- Live video requires real-time captions (WCAG 1.2.4).
- Auto-generated captions such as YouTube default captions do not satisfy the requirement. Captions must be accurate, synchronized, and properly formatted.
Q26. Do our social media posts need to be WCAG compliant after April 2026?
New posts made after your compliance deadline must be accessible. Images need alt text. Videos need captions. Pre-existing posts made before your deadline are exempt under the pre-existing social media posts exception in the rule. You are not responsible for making the entire social platform accessible, covering only your agency’s own posts published after your deadline. Third-party comments on your posts are also exempt.Section 5: How Do We Audit and Fix It?
Key Insight
Accessibility overlay widgets do not constitute compliance. Automated tools detect only 30 to 40 percent of violations. A documented good-faith plan significantly reduces enforcement risk even if you miss the deadline. Manual testing with actual assistive technologies is required for complete compliance.
Q27. How much does ADA compliance remediation realistically cost for a government website?
Cost varies significantly by site complexity. Compare these figures against the average lawsuit settlement of $75,000 or more. Remediation is substantially cheaper in every scenario.
| Site size | Typical timeline | Estimated cost | Ongoing per year |
|---|---|---|---|
| Small (under 100 pages) | 4 to 8 weeks | $5,000 to $20,000 | $3,000 to $6,000 |
| Mid-size (100 to 500 pages) | 8 to 16 weeks | $20,000 to $75,000 | $5,000 to $12,000 |
| Large (500+ pages, heavy media) | 6 to 12 months | $75,000 to $200,000+ | $10,000 to $15,000+ |
Q28. Do accessibility overlay widgets make our government website ADA compliant?
No. The DOJ guidance is unambiguous: WCAG 2.1 Level AA conformance is the legal standard, not the presence of a plugin. Overlay tools use automated scanning that detects only 30 to 40 percent of accessibility issues. They do not fix underlying code. They have been the subject of FTC enforcement actions for misleading compliance claims. Several lawsuits have been filed specifically against organizations that relied on overlays as their sole compliance strategy. Overlays increase legal exposure, not reduce it.
The W3C’s Web Accessibility Initiative does not endorse overlays as a mechanism for achieving WCAG conformance, and major disability rights organizations have formally opposed their use as compliance solutions.Q29. Why do automated scanning tools only catch 30 to 40 percent of accessibility issues on our website?
This figure is well-documented in W3C accessibility evaluation guidance. Automated tools are effective at measurable, technical checks such as color contrast ratios, missing alt text tags, and form label presence. They cannot evaluate:
- Whether alt text meaningfully describes an image, not just that the attribute exists
- Whether a screen reader user can navigate complex interactive menus effectively
- Whether the logical reading order makes sense to someone using assistive technology
- Whether form error messages are clear and actionable
Q30. What should we fix first on our website if time and budget are limited?
Prioritize by impact per fix. In order:
- Color contrast failures across your theme or template: one fix, site-wide impact.
- Missing alt text on images: fast to add, high accessibility impact.
- Unlabeled form fields and submit buttons.
- Keyboard navigation failures in menus, modals, and dropdowns.
- Video captions, starting with your most-viewed content.
- PDF accessibility for your top 20 most-used documents.
Q31. Does our website platform’s accessibility conformance report cover our entire site, or just the core platform?
Just the core platform. An accessibility conformance report (also called a VPAT or ACR) from your CMS or platform vendor documents the accessibility of their base product only. It does not cover your custom design, added modules or plugins, content entered by your team, or third-party integrations. Your agency is responsible for the accessibility of everything published under your domain, regardless of where it originated. Request VPATs from all vendors, but do not treat them as your own compliance documentation.Q32. How long does it realistically take to remediate a government website for WCAG 2.1 compliance?
A phased approach that prioritizes high-traffic services is more defensible than attempting everything at once. Typical timelines:
- Small sites (under 100 pages): 4 to 8 weeks
- Mid-size government sites (100 to 500 pages): 8 to 16 weeks
- Large or complex sites (500 or more pages, heavy PDF and video content): 6 to 12 months
Q33. Does a documented good-faith compliance plan protect our agency if we miss the deadline?
Yes, significantly. The DOJ’s own guidance confirms that documented good-faith effort matters when it evaluates enforcement action. A credible good-faith record includes:
- A published accessibility statement on your website
- A named ADA coordinator with documented responsibilities
- A completed content and digital asset inventory
- A dated accessibility audit with results documented
- A prioritized remediation roadmap with milestones
- Vendor outreach records requesting WCAG 2.1 conformance documentation
- Staff training records
Q34. What free tools can we use to start scanning our website for accessibility violations today?
- WAVE by WebAIM (wave.webaim.org): visual, page-by-page scanning with clear error indicators, free to use in browser
- Google Lighthouse: built into Chrome DevTools, runs an automated accessibility audit with a scored report
- Color Contrast Checker by WebAIM (webaim.org/resources/contrastchecker): tests specific color combinations against WCAG ratios
Ready for a complete audit?
Automated, manual, and assistive technology testing combined. Get a prioritized violation report.
Book Your Free Accessibility AuditSection 6: What Can We Skip?
Key Insight
Moving files to an “archive” folder does not automatically create an exemption. The archived content exception requires the content was created before your deadline, has not been updated since, and is stored in a clearly labeled archive section. All five exceptions have strict, specific conditions that must all be satisfied simultaneously.
Q35. What content is legally exempt from WCAG 2.1 compliance under the ADA Title II rule?
Five narrow exceptions exist under 28 CFR Part 35, Subpart H:
| Exception | What qualifies | Common trap to avoid |
|---|---|---|
| Archived web content | Created before deadline, not updated, in clearly labeled archive area | Any update after deadline removes the exemption immediately |
| Pre-existing documents | PDFs/Word files created before deadline, kept for reference only, not updated | Active program documents do not qualify even if old |
| Third-party content | Content posted entirely at public initiative, not commissioned by agency | Vendor tools used to deliver services are NOT exempt |
| Pre-existing social media | Agency posts made before the compliance deadline | New posts after deadline must have alt text and captions |
| Password-protected individualized docs | Personal records sent to one specific individual | General login-protected portals accessible to many are NOT exempt |
These exceptions are narrow. The age of content alone does not make it exempt. Each exception requires all its specific conditions to be satisfied simultaneously.
Q36. Can we move old documents and pages to an archive folder to exempt them from WCAG compliance?
Not automatically. Moving files to a folder named “archive” does not satisfy the exception. The archived content exception requires all of the following to be true at the same time:
- The content was created before your compliance deadline.
- It is kept only for reference, research, or recordkeeping purposes.
- It has not been updated at all since it was archived.
- It is stored in a section of the site clearly designated and labeled as archived content.
Q37. Are pre-existing documents like meeting minutes, agendas, and council records exempt from WCAG?
Partially. Meeting minutes from 2022 stored for historical reference may qualify under the pre-existing documents exception. The agenda for your next public meeting does not, because it supports an active current program. When the distinction is unclear, the safer approach is to make the document accessible or provide an accessible alternative upon request. The cost of making a document accessible is almost always lower than the cost of defending the exception under enforcement scrutiny.Q38. Does third-party content embedded on our site, including maps, payment portals, and permit forms, need to be accessible?
Yes. Content your agency embeds or uses as part of delivering a government service must be accessible even if a vendor built it. The third-party exception covers only content posted by members of the public at their own initiative, such as public comments on your social media page. If you chose to deploy a vendor tool to deliver a citizen service, you are responsible for its accessibility. Update all vendor contracts to require WCAG 2.1 AA conformance.Q39. What does undue burden mean under ADA Title II, and how do we claim it?
Undue burden is an extremely high-bar exception that applies when compliance would impose severe financial hardship or fundamentally alter the nature of the service. To claim it, you must document the financial impact with specific, detailed evidence, formally invoke the exception in writing, and still provide effective communication through alternative means such as phone, in-person service, or email. Undue burden does not excuse non-compliance outright. It must be formally invoked, documented, and justified. Consult qualified legal counsel before claiming this exception.Q40. Are password-protected individual documents, such as utility bills or tax records, exempt from WCAG?
Yes, with conditions. Individualized, password-protected documents sent to specific individuals are exempt under the rule. The key requirement is that the document is individualized, meaning it is intended for one specific person, such as a personal utility bill or an individual tax notice. General password-protected portals or pages accessible by many users are not exempt. The exemption covers private personal communications, not general login-protected systems or member portals.Section 7: Are We Liable for Our Vendors?
Key Insight
Your agency is fully liable for accessibility failures introduced by vendors and contractors. Outsourcing does not transfer your compliance obligation. Update all vendor contracts to require WCAG 2.1 AA conformance before work begins, not after a complaint arrives.
Q41. Are we legally liable if our third-party vendors and contractors are not WCAG 2.1 compliant?
Yes, fully. Your agency remains legally responsible for the accessibility of all digital services you provide to the public, regardless of who built or maintains them. You can pursue contractors for breach of contract, but only if your contract required WCAG 2.1 AA compliance in the first place. Add that language now to all new contracts and RFPs before any work begins.Q42. Our website is designed and maintained by an outside agency. Are we still responsible for compliance?
Yes. The ADA Title II obligation belongs to your government entity, not your vendor. Your web agency is a contractor working on your behalf. Their accessibility failures become your legal failures. Include WCAG 2.1 AA requirements explicitly in all contracts and RFPs. Require vendors to demonstrate conformance through independent testing and documentation, not just written assertions.Q43. What contract language should we add to require all vendors to deliver WCAG 2.1 compliant work?
Include at minimum:
- “All deliverables must conform to WCAG 2.1 Level AA as defined in 28 CFR Part 35.”
- Require a VPAT or ACR demonstrating conformance before final payment is released.
- Specify remediation timelines and vendor responsibility if issues are found post-launch.
- Include indemnification language protecting your agency from accessibility lawsuits arising from vendor-introduced barriers.
- Reserve the right to audit vendor tools and review compliance documentation at any time.
Q44. What is a VPAT and how do we use it to evaluate whether a vendor is actually accessible?
A VPAT (Voluntary Product Accessibility Template), also called an Accessibility Conformance Report (ACR), is a vendor’s self-reported assessment of their product’s WCAG 2.1 conformance. To evaluate a VPAT effectively:
- Look for clear “Supports” or “Partially Supports” ratings for each criterion.
- Read the remarks carefully. Vague language such as “mostly accessible” or “working toward compliance” is a red flag.
- Request the version aligned to WCAG 2.1 AA, not the older Section 508 or WCAG 2.0 version.
- Verify key claims through your own independent testing rather than relying solely on the vendor document.
Q45. Does a Section 508 VPAT from our platform vendor mean we meet WCAG 2.1 AA?
No. Section 508 VPATs reference WCAG 2.0 Level AA, which is an older standard. WCAG 2.1 adds 12 additional success criteria not present in WCAG 2.0. A product with a clean Section 508 VPAT may still fail multiple WCAG 2.1 requirements, particularly around mobile accessibility and updated contrast rules for non-text content. Always request a WCAG 2.1-specific conformance report and verify claims through independent testing before accepting a vendor deliverable.Q46. We received an ADA demand letter. What do we do right now?
Act immediately. Do not ignore it.
- Alert your legal counsel within 24 hours. Do not respond directly without legal guidance.
- Document the current state of your website with screenshots and any audit reports you have.
- Begin or accelerate your accessibility remediation immediately.
- Compile all evidence of good-faith compliance work already completed.
- Prepare a written remediation timeline if one does not already exist.
Q47. Does our existing municipal or institutional insurance cover ADA web accessibility lawsuits?
Possibly, but check your policy carefully. Some general liability and public entity policies cover ADA civil rights claims. Others specifically exclude them. Employment Practices Liability Insurance (EPLI) typically does not cover website accessibility claims. Ask your insurer specifically about digital accessibility or ADA Title II web compliance coverage. If you are uncovered, the average settlement cost of $75,000 or more comes directly from your operational budget.Section 8: What Do We Do Now?
Key Insight
Publishing an accessibility statement today is the single fastest thing your agency can do to demonstrate good-faith compliance. A named ADA coordinator, a dated audit, and a written remediation roadmap together form your legal protection if you are past the deadline and still remediating.
Q48. What should a government agency’s good-faith ADA compliance plan include, and where do we start?
A credible good-faith plan that holds up under DOJ scrutiny includes:
- Publish an accessibility statement on your website today.
- Name an ADA coordinator with documented responsibilities.
- Complete a content and digital asset inventory.
- Run and document an automated accessibility audit with the date recorded.
- Build a prioritized remediation roadmap with realistic milestones.
- Reach out to all vendors requesting WCAG 2.1 conformance documentation.
- Record staff training completion.
Publish the plan publicly. The DOJ looks for evidence that you took the obligation seriously and are actively working toward compliance, not that you achieved perfection immediately.
| Phase | Priority actions | Owner |
|---|---|---|
| Days 1 to 7 | Publish accessibility statement. Name ADA coordinator. Complete digital asset inventory. | Leadership + IT |
| Days 8 to 30 | Run automated audit across all pages. Document results with date. Identify top 10 critical violations. | IT / Web team |
| Days 31 to 60 | Fix template-level violations (contrast, navigation, skip links). Add alt text to all images. Begin PDF remediation. | Web development team |
| Days 61 to 90 | Manual audit of high-traffic pages. Caption top 20 videos. Update all vendor contracts. Staff training. | IT + Procurement + HR |
Q49. What should we publish as an accessibility statement on our government website?
Your accessibility statement should include:
- Your agency’s commitment to WCAG 2.1 Level AA
- Your current compliance status: be honest if partial compliance is your current reality
- Known limitations and what you are doing to address them
- A mechanism for users to report accessibility barriers: email address, phone number, or online form
- Your ADA coordinator’s name and contact information
- An alternative access option for content not yet accessible
Q50. Who should be our ADA coordinator and what are they actually responsible for under the rule?
Agencies with 50 or more employees must designate an ADA coordinator per 28 CFR Part 35.107. This does not require a new hire. An existing IT director, compliance officer, or communications lead can serve in this role. The coordinator is responsible for:
- Receiving and investigating accessibility complaints
- Coordinating compliance efforts across departments
- Overseeing the accessibility plan and remediation progress
- Serving as the primary contact for DOJ inquiries and audits
Q51. How do we handle citizen complaints about our website accessibility, and what process do we need?
You need a documented complaint process with these components:
- A public-facing mechanism to submit accessibility complaints: email address, online form, or phone number.
- An acknowledgment response within a defined timeframe, ideally 5 to 10 business days.
- An investigation process: review the reported barrier, test it, and document your findings.
- A resolution response to the complainant with a timeline for fixing the issue.
- Records of all complaints and resolutions stored and accessible for DOJ review if requested.
Q52. What training do staff who publish and manage web content need for ADA compliance?
Content publishers need practical training on:
- Writing meaningful alt text for different image types, not just generic labels like “image” or a file name
- Creating documents with logical heading hierarchy before uploading
- Making PDFs accessible before uploading, not as a post-upload remediation step
- Adding accurate captions to video content
- Writing descriptive link text: “Download the permit application” rather than “Click here”
- Using your platform’s built-in accessibility checker before publishing content
Q53. Is ADA web compliance a one-time fix or an ongoing obligation after the deadline?
Ongoing, permanently. Every new page, document, image, video, or form published after your deadline must meet WCAG 2.1 AA. Accessibility degrades naturally as content is added without proper practices in place. Ongoing obligations include:
- Regular accessibility monitoring: automated scans at minimum monthly
- Staff training as team members change
- Vendor oversight and periodic conformance verification
- A public feedback mechanism for reporting new barriers
- Continuous remediation of newly identified issues
Q54. How do we maintain WCAG compliance as editors keep adding new pages, PDFs, and forms over time?
Three practices maintain compliance sustainably:
- Workflow integration: Build accessibility checks into your content publishing process before anything goes live. Drupal and WordPress both support editorial accessibility workflows that flag issues before content is published.
- Automated monitoring: Run regular scans to catch new violations as they are introduced, at minimum monthly.
- Staff training and accountability: Content publishers who understand their role in maintaining conformance create far fewer violations than those who treat accessibility as someone else’s problem.
Q55. Our online forms and citizen-facing portals are managed by separate vendors. How do we ensure they are compliant?
Government forms are the top source of citizen accessibility complaints because they block access to essential services. Three steps:
- Request a WCAG 2.1 AA conformance report from every vendor managing a citizen-facing tool.
- Test the tools independently through automated and manual testing, rather than relying solely on vendor documentation.
- Update all contracts to require WCAG 2.1 AA conformance and specify remediation timelines if issues are found after deployment.
Q56. How does ADA Title II apply to public university course content, learning management systems, and student portals?
Public universities are covered under ADA Title II. All public-facing websites, student portals, and online course materials must meet WCAG 2.1 AA. This covers:
- Your LMS platform and all course content published within it
- Syllabi, lecture slides, and handouts uploaded by faculty
- Videos in courses: all require accurate captions
- Third-party tools integrated into the LMS: these remain your institution’s responsibility, not the tool vendor’s
Quick Reference
Deadline quick reference
| Who | Deadline | Standard required |
|---|---|---|
| State/local governments serving 50,000 or more | April 24, 2026 | WCAG 2.1 Level AA |
| State/local governments serving fewer than 50,000 | April 26, 2027 | WCAG 2.1 Level AA |
| All special district governments | April 26, 2027 | WCAG 2.1 Level AA |
| Private businesses (Title III) | No specific federal date. Courts apply WCAG 2.1 AA | WCAG 2.1 AA in practice |
Key facts
| Fact | Detail |
|---|---|
| WCAG 2.1 Level AA criteria | 50 total: 30 Level A + 20 Level AA |
| Section 508 vs WCAG 2.1 | Section 508 covers WCAG 2.0. Missing 12 criteria. Does not satisfy ADA Title II. |
| Automated tool detection rate | 30 to 40 percent of violations. Manual testing required for the rest. |
| Average settlement cost | $75,000 or more, not including legal fees or mandatory monitoring |
| Private lawsuits in 2025 | 8,667 filed before any federal deadline was in effect |
| Penalty range (DOJ-initiated) | Up to $75,000 first violation, $150,000 for repeat violations |
| Remediation timeline (mid-size site) | 8 to 16 weeks for a typical government site (100 to 500 pages) |
| Number of WCAG exceptions | 5 narrow exceptions: archived content, pre-existing docs, third-party, social media, individualized docs |
Immediate action checklist
Check the status as you complete
| Priority | Action | Status |
|---|---|---|
| P1: Today | Publish an accessibility statement on your website | |
| P1: Today | Name an ADA coordinator with documented authority | |
| P1: This week | Run a free automated scan (WAVE or Lighthouse) | |
| P1: This week | Document your current compliance status with date | |
| P2: Week 2 | Fix template-level violations (contrast, skip links, navigation) | |
| P2: Week 2 | Add alt text to all images across your site | |
| P2: Week 3 | Add captions to your top 20 most-viewed videos | |
| P2: Week 4 | Make your top 20 most-used PDFs accessible | |
| P3: Month 2 | Update all vendor contracts to require WCAG 2.1 AA | |
| P3: Month 2 | Complete staff training for content publishers | |
| P3: Month 3 | Commission manual audit of high-traffic pages | |
| Ongoing | Run monthly automated scans and remediate new violations |
Ready to start?
TheBinaryWorks offers a free accessibility audit for government agencies. Automated, manual, and assistive technology testing combined.
Book Your Free Accessibility AuditLorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.