2026-05-17 · 6 min read

Orange County and Orlando Government Website Accessibility: What the DOJ Title II Rule Requires

# Orange County and Orlando Government Website Accessibility: What the DOJ Title II Rule Requires

The Orlando metropolitan area is one of Florida's fastest-growing regions — and its government entities are among the state's most digitally active, serving residents, businesses, and a massive tourism-adjacent workforce. Both Orange County and the City of Orlando operate extensive digital service platforms and are subject to the DOJ Title II Final Rule requiring WCAG 2.1 Level AA compliance by April 26, 2027.

Who Is Covered in the Orlando Metro

Orange County serves approximately 1.4 million residents. Its primary digital infrastructure includes orangecountyfl.net and web applications spanning property tax, permitting, animal services, elections, and court information.

City of Orlando serves roughly 320,000 residents within the county. Its digital presence includes orlando.gov, online permit applications, utility services, event permitting, and citizen service request systems.

Orlando Utilities Commission (OUC) — the public utility serving Orlando and parts of Orange County — operates public-facing digital services including account management and outage reporting. As a public authority established by Florida statute, OUC's public-facing digital services are covered by the Title II rule.

LYNX (Central Florida Regional Transportation Authority) — the regional transit authority serving Orange, Osceola, and Seminole counties — operates a public-facing trip planner, schedule information portal, and rider communications. As a government authority, LYNX's public web presence is covered.

Orange County Supervisor of Elections — The public-facing voter registration, polling location, and election results systems are government services subject to WCAG compliance requirements.

Each of these entities exceeds the 50,000-population threshold for the April 2027 deadline. Each must independently maintain a defensible compliance record.

What the Rule Requires

Every entity covered by Title II must bring its public-facing web content and mobile apps into conformance with WCAG 2.1 Level AA. The standard has 50 success criteria across four principles:

Perceivable: Content must be perceivable to users with sensory disabilities. Key requirements: text alternatives for all images (1.1.1), captions for all video (1.2.2), text that meets 4.5:1 contrast ratio (1.4.3), content that reflows to single-column at 320px width (1.4.10).

Operable: All functionality must be operable without a mouse. Key requirements: full keyboard access to all functions (2.1.1), no keyboard focus traps (2.1.2), skip navigation links (2.4.1), visible focus indicator at all times (2.4.7).

Understandable: Content must be understandable. Key requirements: descriptive error messages for form errors (3.3.1), labeled instructions for all form inputs (3.3.2), page language declared in HTML (3.1.1).

Robust: Content must work with current and future assistive technology. Key requirements: programmatic name, role, and state for all UI components (4.1.2), status messages communicated without requiring focus (4.1.3).

High-Risk Areas for Orlando-Area Governments

Online permitting applications — Both Orange County and Orlando operate complex online permitting systems. These multi-step, multi-field web applications are the highest-risk WCAG failure surface for most large county governments. Date pickers, file upload controls, multi-step navigation, and conditional logic frequently introduce keyboard and screen reader barriers.

Tourism and event-related content — Orlando's government websites have higher-than-average content volume related to tourism, events, and venues. This content is often visually rich (image-heavy) with inadequate text alternatives. Video content — event recaps, official announcements, meeting recordings — is common and frequently uncaptioned.

Commission and board meeting content — Orange County Commission meetings, City Council meetings, and the meetings of numerous advisory boards and authorities produce large volumes of documents (agendas, minutes, attachments) and recordings that must meet WCAG standards.

Elections and civic participation — Voter registration portals, candidate filing systems, and election results pages are high-stakes civic infrastructure. Screen reader inaccessibility in these systems directly disenfranchises voters with disabilities, which is the clearest possible case for DOJ complaint.

Document libraries — Both Orange County and the City of Orlando have decades of published PDFs. Older documents — particularly those scanned from paper — are completely inaccessible to screen readers. The document remediation scope for a large county government is typically 50–70% of total remediation effort.

Multilingual content — Both Orange County and Orlando maintain Spanish-language content. Each language version of a page must independently meet WCAG criteria. A document published in English and Spanish requires accessible structure in both versions.

The Enforcement Picture

DOJ enforcement of Title II web accessibility operates through the Disability Rights Section. A resident who encounters an inaccessible government service files a complaint; DOJ investigates; governments that cannot demonstrate compliance face corrective action.

Orange County and the City of Orlando each have large resident disability communities and active disability rights advocacy organizations. The metro area's population of 2.7 million means many residents are potential complainants. Unlike smaller counties where a single complaint is an unusual event, Orlando-area governments should plan for the possibility of complaints as a matter of normal course.

Private ADA litigation targeting government websites has been active in Florida's Middle District courts (which cover the Orlando area). Litigation typically targets clear, documentable failures — missing alt text on image-heavy pages, inaccessible forms — rather than subjective claims about quality. Documented WCAG audit findings are precisely the kind of evidence plaintiffs' attorneys use.

Compliance Timeline from May 2026

From today to April 26, 2027 is approximately 11 months. A workable timeline for Orange County or City of Orlando scale:

May–June 2026: Procurement Define scope — main portal, highest-traffic applications, document library sampling strategy, semi-autonomous authorities (OUC, LYNX, Elections). Issue or award audit engagement.

July–August 2026: Audit (4–6 weeks) 200 representative pages, NVDA and VoiceOver manual testing, automated axe-core scan. PDF sampling from document library. Web application testing for permitting, payment, and citizen service systems.

September 2026: Remediation planning Findings report delivered. Responsible parties assigned for each finding. Priority remediation roadmap built — critical findings (complete by December 2026), major findings (complete by February 2027), minor findings (complete by April 2027).

September–February 2027: Remediation Developer teams address programmatic failures (ARIA, keyboard navigation). Content teams remediate image alt text and document accessibility. Web applications upgraded or replaced where accessibility deficits are architectural.

February–March 2027: Re-audit and accessibility statement Independent verification of remediated findings. DOJ-compliant accessibility statement published on the government website identifying the auditor, the standard, known residual limitations, and a feedback mechanism for residents.

April 26, 2027: Compliance deadline

Getting Started

Before engaging a WCAG auditor, two resources help establish a self-assessment baseline:

• The free WCAG 2.1 AA Compliance Checklist — 47 success criteria with clear pass/fail criteria. Available on the website, no email required.
• The $149 WCAG Pre-Audit Readiness Kit — detailed testing protocols for keyboard navigation, screen reader testing, and PDF assessment.

The Parallax WCAG Audit

Parallax is Morton Technology Consulting's fixed-fee WCAG audit for Florida government agencies operating under the April 2027 deadline. $9,500, 200 representative pages, 4–6 week delivery.

Deliverables: professional WCAG 2.1 AA findings report with severity classifications (critical/major/minor), NVDA and VoiceOver manual test results, axe-core automated scan coverage, remediation roadmap with recommended prioritization, and a DOJ-compliant accessibility statement draft.

The sample audit report shows the exact deliverable format — a completed assessment of a Florida government site.

For Orange County, the City of Orlando, or any of the semi-autonomous authorities (OUC, LYNX, Elections Supervisor), an initial scoping conversation determines whether one 200-page engagement covers the highest-risk compliance scope, or whether a phased approach makes better use of the timeline.

Contact: [email protected]

---

*Morton Technology Consulting LLC, Tallahassee, FL. Government website WCAG compliance audits for the April 2027 deadline.*

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →