The compliance dates moved, and that is good news only if you use the extra time well. In April 2026, the Department of Justice extended the ADA Title II web accessibility deadlines, setting April 26, 2027 for public entities serving 50,000 or more people and April 26, 2028 for smaller jurisdictions and special districts. Treat those dates as a planning window, not a reprieve. WCAG 2.1 Level AA conformance is a multi-budget-cycle project, and agencies that scope it now avoid the last-minute patch that costs more and delivers less.
This tutorial walks through the work in sequence. You will learn what the DOJ rule requires and what the extension changed, which deadline applies to your entity, and how school districts face a second deadline track under Section 504. We then cover three scoping steps: auditing what you already publish, folding remediation into your next redesign, and writing testing, documentation, and ongoing conformance into vendor contracts. We close with what remains unsettled, answers to common questions, and next steps for both cycles. OneStop Northwest supports organizations with websites and technology, and this guide is built so internal teams and outside partners can work from the same plan.
The Extension Is a Planning Window, Not a Reprieve
The Department of Justice moved the ADA Title II web accessibility compliance dates. A schedule change is not a scope change. The obligation to make public web content accessible did not shrink; only the calendar did.
The work is date-proof. Content inventory, PDF remediation, template and theme fixes, staff workflow changes, and vendor contract renegotiation take the same effort whether a deadline lands in 2027 or 2028. None of it compresses because a deadline slipped a year.
These dates have already moved once. Plan against the current dates as firm, and build a timeline that can absorb another shift without restarting from zero. An agency that begins remediation in the final budget cycle before April 26, 2027 is not one quarter late; it is two fiscal years short of the work.
What follows is a scoping sequence a city administrator, school business official, or procurement lead can hand to a team, not a technical remediation manual. Treat accessibility as an acceptance criterion in your next redesign, a requirement easier to specify inside a structured professional website design engagement.
What the DOJ Rule Requires and What the Extension Changed
To scope accurately, start with the rule itself. The ADA.gov fact sheet on the Title II web rule summarizes the obligations.
The technical standard is WCAG 2.1 Level A and Level AA conformance at minimum. WCAG means the Web Content Accessibility Guidelines, a set of testable success criteria maintained by the W3C.
Operationally, conformance is a maintained state, not a one-time audit certificate. It applies to everything the agency publishes: staff-written pages, content pulled from third-party platforms, and documents posted for public notice. The rule reaches web content provided directly or through contractual, licensing, or other arrangements, so vendor-delivered content remains the agency’s obligation. The RWG legal alert is a useful secondary read on that coverage point.
The April 20, 2026, interim final rule changed the compliance dates to April 26, 2027, for entities serving 50,000 or more people and April 26, 2028, for smaller entities and special districts. It left the standard, the coverage language, and the 2024 final rule framework intact.
Which Deadline Applies to Your Entity
Start your plan with the date, not the audit.
| Entity category | Compliance date |
|---|---|
| Population of 50,000 or more | April 26, 2027 |
| Population under 50,000 | April 26, 2028 |
| Any special district | April 26, 2028 |
Both tracks come from ADA.gov’s Title II web rule fact sheet.
Population means the most recent decennial Census count for your entity, not service-area estimates, staffing, or budget size. Confirm how you are counted before you pick a date.
Classification matters more than size: every special district gets April 26, 2028 regardless of population served. Settle whether you are a special district, a department inside a larger jurisdiction, or a separate entity, because that answer drives the entire schedule.
Shared content blurs the line: a county publishing on behalf of member cities, a district hosting pages for a smaller partner, a joint portal run by two agencies. Identify which entity’s date governs that content before scoping it.
Most cities, counties, school districts, and special-purpose districts will land inside the rule’s scope, but confirm your classification; that answer drives the entire schedule.
School Districts Also Face a Second Deadline Track
School and health-adjacent agencies have a second clock running. A separate HHS rule under Section 504 of the Rehabilitation Act carries its own web accessibility dates, extended by one year: covered entities with 15 or more employees must comply by May 11, 2027, and smaller entities by May 11, 2028, according to EDUCAUSE Review’s summary of the DOJ and HHS extensions.
HHS coverage follows funding, not entity type. The rule reaches private and public entities that receive HHS funding, which pulls in many school districts, local health departments, and human services programs that might not otherwise track the DOJ date.
One scope point catches school administrators off guard: for educational institutions, Section 504 applies across all institutional operations, not just the HHS-funded program. On that reading, content such as the main district site, athletics pages, and a parent portal is likely in scope; confirm the footprint with counsel.
Planning rule: if both tracks apply, the earlier date governs your project schedule. Build one timeline against the earliest deadline, not two parallel plans.
Because these are separate authorities with separate dates, route funding and coverage questions to counsel. Use this section to keep the second track on the project plan, not to settle it.
Scoping Step 1: Audit What You Already Publish
Whichever date governs your schedule, start by measuring what you already publish. Treat this sequence as a planning recommendation, not a regulatory requirement; no rule mandates an audit, but the extended window makes one affordable.
Inventory by content type, not page count
List policy and procedure pages, board agendas and packets, forms, permits and applications, PDFs and scanned documents, department microsites, and third-party portals for payments, permitting, and learning management. The rule covers all services, programs, and activities delivered online (Coates’ Canons). Many of those PDFs begin as print collateral, so the version control you would want from a commercial printing partner determines how fast a document can be fixed.
Prioritize by consequence, not traffic
Enrollment, utility billing, permits, public notices, and emergency information outrank a busy news page. Anything a resident must complete to receive a service comes first.
Record a reusable baseline
Log what was tested, which success criteria, what failed, and the date. That record becomes your re-test benchmark, budget justification, and vendor handoff.
Assign ownership while it is fresh
Name who is accountable for each category, plus who publishes, approves, and holds admin access. In our experience, conformance fails most often in the publishing workflow, not the codebase.
Document what you set aside
Record each exclusion and why, pending verification of the exemption list in the official text.
Scoping Step 2: Fold Remediation Into the Next Redesign
Turn your audit baseline into a design input, not a filing cabinet document. In our experience, remediation folded into a scheduled redesign usually costs less than a standalone retrofit, because template, navigation, and component fixes ship once instead of twice.
Contract language decides whether conformance ships. Does the request for proposals require WCAG 2.1 AA conformance as an acceptance criterion, or only generic accessibility language? Name who tests, with what method, and against which success criteria.
Budget the line item most agencies miss: content migration. Legacy PDFs, scanned documents, and pages from an outdated editor in our experience can rival or exceed the site build in effort, so they need a budget line and an owner.
Sequence milestones backward from launch, as a 90-day company store launch does. Solicitation drafting, evaluation, board approval, contract execution, and build time all sit between the decision to act and a launched site, so the 2027 and 2028 dates mean scoping now.
Separate one-time from recurring spend. A redesign is capital; conformance is operating, sustained through content updates, staff turnover, and platform upgrades. Structure it like a managed corporate apparel program: a defined setup phase and a named owner for steady state.
Scoping Step 3: Write Accessibility Into the Vendor Contract
Because Title II reaches contractually delivered content, the contract is how vendor-built and vendor-hosted content stays inside your compliance posture. Treat it as the control mechanism, not a formality.
Specify testing, not promises: a named methodology combining automated scanning with manual testing using assistive technology, tested against WCAG 2.1 Level A and AA success criteria, covering a defined set of pages and templates before acceptance.
Require documentation you keep: a conformance report at launch and after major releases, a known-issues log with remediation dates, and a plain-language summary a board or council can read beside the audit baseline.
Assign regression ownership. Name who fixes defects introduced by new features, content updates, or platform upgrades, how those defects are tracked, and that fixes fall under the contract rather than new change orders. The accountability standards public agencies already apply in government procurement for branded products and uniforms translate directly here.
Protect continuity: require documentation, administrative access, and training for content staff, the same vendor evaluation rigor HR teams use to evaluate vendors and structure an apparel program, so conformance does not hinge on one vendor or restart after a transition.
OneStop Northwest is a single-source business solutions partner. A partner handling design, hosting, and procurement in one place can build these requirements into a single scope rather than splitting them across three contracts.
What Is Still Unsettled, and Why That Matters
A signed contract closes one gap, not all of them. Public sources do not describe how DOJ will enforce the 2027 and 2028 dates. The extension is not a grace period, so plan against the current dates as operative.
Treat the exemption list as unverified. Secondary summaries mention content categories exempt from WCAG 2.1 AA, but the categories were not available in reviewed extracts. Pull the list from 28 CFR Part 35 or the official Federal Register text before excluding anything.
There are also no reliable public per-site cost figures. Build your estimate from your audit findings and your vendor’s documented testing methodology, not a conference slide.
The deadlines have already moved once, so set a recurring check against ADA.gov and the Federal Register.
When in doubt, scope more rather than less. Testing content you did not need to fix costs little compared with missing content you did.
Frequently Asked Questions
The unresolved items above drive the questions agencies ask most.
Does the extension apply to special districts? Yes. Any special district lands on the April 26, 2028 date regardless of the population it serves, according to the ADA.gov fact sheet.
Is WCAG 2.1 Level AA still the standard? Yes. The extension changed compliance dates only. The technical standard and the coverage language in 28 CFR Part 35, Subpart H remain in place.
How is the 50,000 person threshold measured? By the most recent decennial Census count for the entity. Service-area estimates, staffing levels, and budget size do not determine the track.
Do school districts face a different deadline? Possibly two. Public school districts fall under the DOJ dates as state and local entities, and HHS Section 504 adds May 11, 2027 or May 11, 2028 for entities receiving HHS funding. Plan one schedule against the earlier applicable date.
What should an accessibility clause in a vendor contract include? A named testing methodology, conformance documentation at launch and after major releases, clear ownership of regression fixes, and training plus documentation so your agency can maintain conformance after the contract ends.
Next Steps for the 2027 and 2028 Cycles
With those questions settled, the remaining work is sequencing. Five actions turn the extended dates into a defensible plan.
1. Confirm your compliance date in writing. Apply the Census-based population threshold and your entity classification, then record that determination in the project file so budget and procurement staff are working from one date.
2. Run the content audit this fiscal year. Prioritize by consequence of failure rather than page count, and convert the findings into a baseline document that carries forward into budget requests and vendor conversations.
3. Lock conformance into the next redesign solicitation. Write WCAG 2.1 AA conformance and testing requirements into the request for proposals before scope is fixed. Adding acceptance criteria after contract signature is far harder than drafting them before.
4. Attach accessibility to every renewal. Web, hosting, and platform agreements should carry testing, documentation, and regression ownership, including contracts already in place.
5. Monitor the schedule. A standing review of ADA.gov and the Federal Register catches a future change during a planning cycle rather than a crisis.
Conclusion
The extended ADA deadlines are a planning window, not permission to wait. Confirm your entity’s compliance date in writing, audit what you publish now, and prioritize fixes by the consequence of failure. Then write WCAG 2.1 AA conformance and testing into redesign solicitations and vendor renewals so accessibility becomes part of how work is bought and maintained. Keep the schedule under review so future changes surface during planning, not during a crisis. The practical next step is to schedule the content audit this fiscal year and turn its findings into a baseline for budget and procurement conversations. If your team needs help turning that baseline into a workable audit, remediation, or vendor contract plan, OneStop Northwest can support that work. Start with one confirmed date and one scheduled audit; that is how a deadline becomes a defensible plan.
