2026-05-17 · 5 min read
Jacksonville Government Website Accessibility: What the DOJ Title II Rule Means for Duval County
# Jacksonville Government Website Accessibility: What the DOJ Title II Rule Means for Duval County
Jacksonville and Duval County operate one of Florida's largest consolidated city-county governments — a single municipal government serving roughly 950,000 residents. That population figure places the City of Jacksonville firmly within the first compliance tier of the DOJ's Title II web accessibility rule: WCAG 2.1 Level AA conformance required by April 26, 2027.
This post explains what the rule requires, what it covers, and what a realistic compliance timeline looks like for a government of Jacksonville's size and complexity.
Why This Rule Applies to Jacksonville
Title II of the ADA has always prohibited disability discrimination in government programs. What changed in March 2024 is that the Department of Justice published a Final Rule establishing a specific technical standard: WCAG 2.1 Level AA. Previously, governments faced Title II obligations but no codified definition of "accessible." The Final Rule resolves that ambiguity.
Jacksonville's status as a consolidated city-county government with a population exceeding 50,000 places it in the first compliance cohort. The April 26, 2027 deadline is the compliance date — not a planning deadline, not a "begin work by" date. Full conformance is required by that date.
What Must Be Accessible
The rule covers all web content and mobile applications that the City of Jacksonville:
- Makes available to the public
- Uses to offer programs, services, or activities
For a government of Jacksonville's scope, that includes:
coj.net and associated subdomains — The main city portal, department pages, and any subdomain hosted under city infrastructure.
Citizen-facing web applications — Permit portals (Jacksonville's LPS building permit system), utility payment portals, parks registration, tax payment systems, and online license applications.
PDF and document libraries — Meeting agendas, zoning documents, public notices, budget documents, and reports published on city or JEA websites. Each published document must meet accessibility standards.
JEA's public-facing web presence — JEA operates as an independent public utility, but to the extent its digital services are offered in connection with government programs, they fall within scope.
JTA's public-facing web and mobile apps — The Jacksonville Transportation Authority's trip planner, schedule information, and public alerts are public-facing government services.
JFRD and JSO public communication channels — Online forms for public records requests, fire inspection requests, and similar services.
Third-party content the city procures and controls — If the city has contracted with a vendor to provide an online permit system, that system must conform even though it's hosted by the vendor.
What Is Exempt
The rule does not apply to:
- Archived content no longer actively used or maintained, properly labeled as archived
- Content posted by third parties not under contract with the city (public comments on a city forum)
- Internal employee-only systems not accessible to the public
These exemptions are narrow. A document from 2018 that is actively linked from a current city webpage is not "archived" under the rule's definition.
What WCAG 2.1 Level AA Requires
WCAG 2.1 Level AA has 50 success criteria organized under four principles. The most common failures for government websites of Jacksonville's scale:
Perceivable failures:
- Images missing text alternatives (alt text) on pages that have changed frequently across administrations
- PDFs that are scanned images rather than tagged, accessible text — common for older zoning and meeting documents
- Insufficient color contrast on text-heavy department pages built on older templates
- Video content published without captions — public meetings, announcements, emergency alerts
Operable failures:
- Interactive web applications (permit portals, payment systems) that require mouse interaction for critical functions
- Complex multi-step forms that trap keyboard focus
- Emergency notification banners that appear and disappear without warning or keyboard control
Understandable failures:
- Error messages in online forms that say "invalid input" without explaining what is wrong or how to fix it
- Inconsistent navigation patterns across the many subdomains and third-party systems Jacksonville's government uses
Robust failures:
- Third-party widgets and embedded applications that lack accessible name, role, and state information
- Dynamic content (search results, filter systems) that does not communicate state changes to screen readers
The Compliance Timeline for a Government of Jacksonville's Scale
A government with Jacksonville's digital footprint — consolidated city-county government, multiple enterprise web applications, a document library spanning decades, numerous semi-autonomous authorities (JEA, JTA, JPA) — requires careful scoping before audit work begins.
A realistic timeline from today (May 2026):
May–June 2026: Scoping and procurement
- Define which systems and domains fall in scope
- Determine which semi-autonomous authorities (JEA, JTA, JPA) have independent compliance obligations versus joint obligations
- Issue an RFP or sole-source engage a WCAG auditor
June–August 2026: Audit
- 200-representative-page audit with manual NVDA and VoiceOver testing
- Document library sampling (PDFs, Word documents)
- Web application testing for permit portals, payment systems
August–September 2026: Remediation planning
- Findings report reviewed by IT, Legal, and department heads
- Remediation roadmap with responsible parties and target dates by severity
- Critical findings assigned first (screen reader inaccessible forms, keyboard traps)
September 2026–February 2027: Remediation
- Critical and major findings addressed by developer teams and CMS content editors
- New document publication standards put in place
- Staff training on accessible document creation
February–March 2027: Re-audit and accessibility statement
- Independent re-audit of remediated findings
- Final corrections
- DOJ-compliant accessibility statement published on coj.net
April 26, 2027: Compliance deadline
This schedule has approximately six weeks of float. An agency that starts procurement in Q3 or Q4 2026 cannot reach April 2027 compliance with a credible program.
How DOJ Enforcement Works
DOJ enforcement of Title II web accessibility is complaint-driven. A Jacksonville resident with a disability files a complaint — through the DOJ's online complaint portal, through an attorney, or directly — and DOJ investigates. The investigation process involves a request for documentation and a site assessment.
Governments that respond with a documented compliance program (audit findings, remediation plan, progress tracking, accessibility statement) are in a fundamentally different position than governments that respond with "we're working on it." The former negotiates timelines; the latter faces corrective action agreements written by DOJ.
Jacksonville's consolidated government, with its large digital footprint and multiple semi-autonomous authorities, is a complex compliance environment. A complaint about JTA's trip planner, JEA's payment portal, or the LPS permit system would each require a separate documented response.
The Parallax WCAG Audit
The Parallax WCAG audit from Morton Technology Consulting is designed for government entities operating under the April 2027 deadline — a fixed-fee ($9,500), professional assessment built for Florida government agencies.
What's included: 200 representative pages, NVDA and VoiceOver manual testing, automated scan with axe-core, full findings report with severity ratings, remediation roadmap with prioritized timeline, and a DOJ-compliant accessibility statement draft ready to publish.
The sample audit report shows the exact deliverable format (completed for a Florida government site). For a government of Jacksonville's complexity, an initial scoping call helps determine whether one audit covers the full scope or whether phased audits (main site, then enterprise applications, then document library) makes more sense.
Contact: [email protected]
---
*Morton Technology Consulting LLC, Tallahassee, FL. Government website WCAG compliance audits for the April 2027 deadline.*
Sources
- [1] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "State and local governments must make sure that their web content and mobile apps meet WCAG 2.1, Level AA"
- [2] ADA.gov — DOJ Title II Web Accessibility Final Rule Compliance Dates — "Governments serving 50,000 or more people: April 26, 2027"
- [3] U.S. Census Bureau — QuickFacts: Jacksonville city, Florida — "Jacksonville city, Florida population estimate"
Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →