DOJ’s Title II web and mobile accessibility rule now gives larger public entities until April 26, 2027 and smaller entities or special district governments until April 26, 2028. For WDBs and AJCC systems housed in state or local government, the job now is to inventory the full digital service environment and remediate high-impact barriers before the deadline.
Source + trust record
Source checked as of September 18, 2026. Primary authority: DOJ ADA Title II web/mobile rule and the 2026 compliance-date update.
Check result: DOJ’s Title II rule requires covered state and local public entities to meet WCAG 2.1 Level A and AA for covered web content and mobile apps, subject to the rule’s exceptions and defenses. The 2026 interim final rule extended compliance to April 26, 2027 for entities with populations of 50,000 or more and April 26, 2028 for smaller entities and special district governments. This AI-assisted brief does not receive human legal or compliance review. Official sources control.
WDB decision strip
| Status | Action | Primary owners | Compliance date | Impact |
|---|---|---|---|---|
| FINAL RULE · DEADLINES EXTENDED IN 2026 | INVENTORY + REMEDIATE | Public entity · ADA/EO · IT · Procurement · WDB | April 26, 2027 or April 26, 2028 | Websites · PDFs · Forms · Portals · Mobile apps · Vendors |
The bottom line
Treat accessibility as a service-delivery requirement, not a website cleanup project.
The rule requires covered state and local public entities to ensure that web content and mobile apps they provide or make available, including through contractual or licensing arrangements, meet WCAG 2.1 Level A and AA unless an applicable exception or defense applies. For workforce systems, that can reach customer-facing pages, forms, PDFs, appointment systems, board materials, portals, mobile interfaces, and vendor-hosted tools.
Which deadline applies?
| Public entity | Current compliance date | WDB action |
|---|---|---|
| Population 50,000 or more | April 26, 2027 | Work backward from the public entity’s enterprise remediation plan and prioritize workforce systems with high customer impact. |
| Population 0-49,999 | April 26, 2028 | Use the additional time to build accessible content creation and procurement into normal operations. |
| Special district governments | April 26, 2028 | Confirm that the entity actually qualifies as a special district under DOJ’s rule. |
Watch out: the deadline is based on the covered public entity’s status and population methodology, not the number of people the WDB serves or the size of the workforce program. Confirm applicability with the county, city, state, or other public entity that houses the system.
What belongs in the inventory
| Asset | Typical workforce example | Test |
|---|---|---|
| Public web pages | AJCC locations, service descriptions, eligibility information, hiring events, board pages | Can people using keyboards and assistive technology navigate, understand, and use the content? |
| Documents | Policies, agendas, minutes, flyers, forms, reports, board packets | Is the document structurally accessible, not merely readable on screen? |
| Forms + portals | Appointment requests, interest forms, applications, customer and employer tools | Can a user complete the full transaction without inaccessible controls, labels, validation, or instructions? |
| Vendor products | Scheduling, chat, learning, LMI, recruiting, case-management, and assessment tools | Does the contract require accessibility, documentation, testing, and remediation? |
| Mobile content | Apps and mobile interfaces provided by or for the public entity | Does the mobile experience meet the same applicable standard? |
Operational considerations for WDBs
- Confirm the governing public entity and deadline. Coordinate with ADA, legal, IT, and equal-opportunity leads rather than assuming the WDB is the compliance unit.
- Inventory the whole digital service chain. Include public web pages, PDFs, forms, portals, board materials, vendor tools, and mobile apps.
- Prioritize high-consequence functions first. Start with applying for services, scheduling, finding locations, requesting accommodations, accessing public meetings, and completing customer or employer transactions.
- Fix content creation at the source. Train staff who create PDFs, Word documents, web pages, flyers, forms, and board materials so accessibility is not a downstream remediation task.
- Change procurement and renewal language. Require accessibility evidence, testing, remediation obligations, and vendor accountability for digital products.
- Create a remediation queue. Assign owners, severity, due dates, verification, and escalation instead of relying on ad hoc fixes.
- Test with people, not only tools. Automated checks are useful but do not replace keyboard, screen-reader, zoom, contrast, form, and workflow testing.
Required / local choice / good practice / watch out
| Label | How to apply it |
|---|---|
| Required | Covered public entities must meet the applicable Title II web/mobile accessibility requirements by the relevant compliance date. |
| Local choice | The entity decides how it organizes governance, testing, remediation, training, and procurement to achieve compliance. |
| Good practice | Prioritize the customer journeys with the highest consequence and build accessibility into normal content and procurement workflows. |
| Watch out | Do not treat vendor-hosted systems, PDFs, mobile apps, or overlays as automatically outside the compliance problem. |
Why PDFs need their own workstream
Workforce systems publish large volumes of PDFs: board packets, policy manuals, outreach flyers, applications, reports, labor-market products, and grant documents. A webpage can be accessible while the linked document is not. Boards should distinguish between remediating high-value legacy documents and changing how new documents are created so the backlog stops growing.
How this fits WIOA accessibility duties
ADA Title II web accessibility is distinct from WIOA Section 188 and 29 CFR Part 38. A public workforce system may have obligations under both. Operationally, the strongest approach is to coordinate ADA, WIOA equal-opportunity, IT, procurement, communications, and board-administration work rather than creating parallel accessibility programs.
By role
WDB leadership
Make digital accessibility an operating risk and customer-access issue, not just an IT assignment.
IT / procurement
Own platform testing, vendor requirements, technical remediation, and renewal controls.
ADA / EO / communications
Set content standards, train creators, manage accommodation pathways, and verify public-facing materials.
Source authority
- DOJ ADA.gov — Title II Web and Mobile Accessibility Rule Fact Sheet
- DOJ ADA.gov — First Steps Toward Compliance
- DOJ — 2026 Interim Final Rule extending compliance dates
Interpretation note: DOJ’s rule and 2026 interim final rule control the federal requirements and deadlines. Inventory sequencing, remediation governance, role assignments, and procurement recommendations above are Workforce Wonkery implementation guidance and not legal advice.
Leave a Reply