2026-05-17 · 9 min read

Ohio Government Website Accessibility: What the DOJ Title II Rule Means for Your Agency

# Ohio Government Website Accessibility: What the DOJ Title II Rule Means for Your Agency

Ohio has 88 counties — one of the highest county counts in the United States. Add the state's hundreds of municipalities, township governments, independent school districts, transit authorities, and public universities, and Ohio has one of the most layered local government landscapes in the country. The DOJ Title II Final Rule applies to every one of those entities that meets the population threshold.

If you are an Ohio government IT director, this post gives you the specific compliance requirements, who is covered, what is covered, how Ohio's statewide OIT accessibility standard interacts with the federal rule, and the compliance picture across Ohio's major metro areas.

Who Is Covered

The federal rule applies to state and local government entities with a total population of 50,000 or more. The April 26, 2027 deadline applies to those jurisdictions. Entities under 50,000 have until April 26, 2028 — the standard is identical; only the timeline differs. ^[1]

In Ohio, that covers:

Ohio state government — the state of Ohio and all executive branch agencies are covered. That includes the Ohio Department of Administrative Services (DAS), the Ohio Department of Transportation (ODOT), the Ohio Department of Education and Workforce, the Ohio courts web presence, and dozens of other agencies, each with their own digital properties.

Major Ohio counties — Franklin County (~1.3 million), Cuyahoga County (~1.3 million), Hamilton County (~830,000), Summit County (~540,000), Montgomery County (~530,000), and Lucas County (~430,000) are the six most populous counties. ^{[4] [5] [6]} All are well above the 50,000 threshold and face the April 26, 2027 deadline. Delaware County (~235,000), Lorain County (~310,000), Butler County (~390,000), Stark County (~375,000), and Warren County (~260,000) are also above the threshold. Ohio's 88 counties present a wide range of sizes — many smaller rural counties fall in the April 2028 tier.

Major Ohio cities — Columbus (~905,000), Cleveland (~365,000), Cincinnati (~310,000), Toledo (~270,000), Akron (~185,000), Dayton (~135,000), Parma (~82,000), Canton (~71,000), Youngstown (~60,000), and Lorain (~66,000) are all above 50,000. Each city is an independently covered entity.

Transit authorities — the Greater Cleveland Regional Transit Authority (GCRTA), the Central Ohio Transit Authority (COTA), Southwest Ohio Regional Transit Authority (Cincinnati Metro), the Greater Dayton Regional Transit Authority (GDRTA), and the Toledo Area Regional Transit Authority (TARTA) are all independently covered entities. Transit websites, trip planners, mobile apps, and schedule PDFs are in scope. ^[12]

Public universities and community colleges — Ohio State University (~60,000 students), the University of Cincinnati (~47,000 students), Ohio University, Kent State University, University of Toledo, Wright State University, and other public institutions with populations above 50,000 are independently covered. Community colleges with smaller enrollment fall in the April 2028 tier.

School districts — Ohio has more than 600 public school districts. Districts with enrollment above 50,000 face the April 2027 deadline; smaller districts have until April 2028. Compliance obligations extend to the district's website, parent portals, student information systems, and published documents.

Libraries, park districts, port authorities, and other special districts — Ohio has numerous independent special-purpose public entities. Each must assess whether its own population or service area places it in the April 2027 or April 2028 tier.

What Is Covered

The rule covers web content and mobile apps that a public entity makes available to the public or uses to offer services, programs, or activities. ^[11] For Ohio government entities, that includes:

• The main public website and all subdomains
• Web-based applications residents use: permit portals, utility payment systems, licensing applications, benefits portals, registration forms
• Mobile apps distributed to the public
• Documents published through any of the above: PDFs, Word files, spreadsheets, presentations

Third-party content procured or controlled by the agency falls under the obligation. If you contracted a vendor to build your permit portal, that system must meet WCAG 2.1 AA. The compliance responsibility transfers to you as the contracting entity. Every technology contract signed after your compliance date should include WCAG 2.1 AA conformance as a mandatory deliverable.

---

Ohio's State Accessibility Framework: OIT and DAS

Ohio adds a state-level compliance layer that predates the federal rule. The Ohio Office of Information Technology (OIT) publishes a statewide IT accessibility standard that requires Ohio executive branch agencies to conform to WCAG 2.1 Level AA. ^[7] The Ohio Department of Administrative Services (DAS) oversees state IT procurement and policy, and DAS guidance incorporates accessibility requirements into procurement for state agency websites and applications. ^[8]

For Ohio state agencies, this means two compliance frameworks run in parallel: the OIT/DAS state standard and the DOJ Title II Final Rule. The substantive target — WCAG 2.1 Level AA — is the same under both. The enforcement mechanisms are distinct: the state framework is enforced through DAS and OIT administrative channels; the federal rule is enforced through DOJ complaint investigations and, ultimately, federal court.

Ohio's state accessibility framework also means that state agencies have had institutional exposure to WCAG 2.1 AA requirements longer than agencies in states without equivalent state law. That institutional history does not guarantee compliance — state agencies outside the DAS procurement pathway, courts, and state-affiliated entities may have uneven compliance — but it creates a baseline of policy awareness that is absent in some other states.

Local governments in Ohio — counties, cities, townships, transit authorities, school districts — are primarily subject to the federal DOJ rule rather than the OIT state standard. But the technical requirement is identical: WCAG 2.1 Level AA.

---

What WCAG 2.1 Level AA Requires

WCAG 2.1 Level AA has 50 success criteria organized under four principles. ^[9]

Perceivable — content must be presentable in ways users can perceive. Alt text for informational images. Captions for video. Transcripts for audio. Sufficient color contrast: 4.5:1 for normal text, 3:1 for large text. Content that reflows to a single column at 320px without horizontal scrolling.

Operable — all functionality must work without a mouse. Keyboard navigation must reach every interactive element. No time limits that trap users. No content that flashes more than three times per second. Skip navigation links that allow users to jump past repeated header elements.

Understandable — the language of the page must be declared in HTML so screen readers pronounce content correctly. Forms must include visible labels, error messages that identify what is wrong, and suggestions for how to fix it. Navigation must be consistent across pages.

Robust — HTML must be valid, with proper ARIA roles and attributes so assistive technology can parse and interact with the interface.

The WebAIM Million 2024 report found that 95.9% of home pages had detectable WCAG 2 failures. ^[10] The five most common: low contrast text (81%), missing alt text (54.5%), missing form labels (48.6%), empty links (44.6%), and missing document language (17.1%). Ohio government sites follow the same failure patterns seen nationally.

---

The Three Most Common Failure Categories for Ohio Government Sites

1. PDF accessibility. Ohio government entities publish extensive volumes of PDFs — budget documents, ordinances, meeting minutes, permit applications, public records requests, transportation plans, court forms. Most of these are inaccessible. Scanned-image PDFs — common for older records — are unreadable by screen readers. Even digitally created PDFs typically lack the tag structure, reading order, and accessible form fields WCAG requires. The rule covers PDFs when they provide access to government services, programs, and activities.

2. Accessible forms for government services. Ohio government permit portals, tax payment systems, licensing applications, benefits portals, and registration systems commonly fail WCAG 1.3.1 (form fields lack programmatically associated labels), 3.3.1 (errors not identified in text), and 3.3.3 (no suggestions provided for correcting errors). When a resident cannot complete a permit application or pay a utility bill because the form is inaccessible, it is a service failure, not just a technical gap.

3. Keyboard inaccessibility in complex interactions. Custom navigation menus, interactive maps, date pickers, modal dialogs, and GIS-based interfaces — common in Ohio permit portals, property search tools, and transit applications — frequently trap keyboard users or become unreachable without a mouse. WCAG 2.1.1 (Keyboard), 2.1.2 (No Keyboard Trap), and 2.4.7 (Focus Visible) are among the most common failures that automated scanners cannot detect.

---

Compliance Timeline for Ohio Entities

Ohio covered entities have until April 26, 2027. A realistic WCAG compliance program for a mid-size Ohio government entity:

• Weeks 1–4: Scope the digital footprint — inventory all web properties, subdomains, mobile apps, and document repositories.
• Weeks 5–12: Commission an audit covering automated scanning, manual testing with assistive technology (NVDA, JAWS, VoiceOver), and document review.
• Weeks 13–24: Remediation planning — prioritize findings by severity and service impact, assign ownership, set milestones.
• Weeks 25–40: Remediation — developers fix code, document teams reformat PDFs, procurement adds WCAG requirements to new vendor contracts.
• Weeks 41–48: Validation testing — re-test against WCAG 2.1 AA to confirm remediation is complete.
• Weeks 49–52: Publish an accessibility statement, establish ongoing monitoring, train staff.

Entities that begin now have a realistic path to April 2027 compliance. Entities that delay past fall 2026 will not.

---

Ohio's Major Metro Compliance Profiles

Franklin County / Columbus. Ohio's largest county and state capital. Franklin County government, the City of Columbus (~905,000), COTA transit, Columbus Metropolitan Library, and Ohio State University (~60,000 students) all face the April 26, 2027 deadline. Columbus City Schools (~47,000 students) and Columbus State Community College (~25,000 students) have until April 26, 2028. As the state capital, Columbus government entities operate under the highest enforcement scrutiny — OIT, DAS, and DOJ Civil Rights Division are all present. See the detailed Franklin County compliance guide.

Cuyahoga County / Cleveland. Ohio's second largest county (~1.3 million). Cuyahoga County government, the City of Cleveland (~365,000), the Greater Cleveland Regional Transit Authority (GCRTA), Cleveland Metropolitan School District (~35,000 students — April 2028), Cuyahoga Community College, and Cleveland State University all have independent compliance obligations. ^[5]

Hamilton County / Cincinnati. Hamilton County (~830,000), the City of Cincinnati (~310,000), Southwest Ohio Regional Transit Authority (Cincinnati Metro), Cincinnati Public Schools, and the University of Cincinnati (~47,000 students) all face the April 2027 deadline. ^[6]

Summit County / Akron. Summit County (~540,000), the City of Akron (~185,000), Metro RTA, Akron Public Schools, and the University of Akron are independently covered.

Montgomery County / Dayton. Montgomery County (~530,000), the City of Dayton (~135,000), Greater Dayton RTA, and Dayton Public Schools all face the April 2027 deadline.

Lucas County / Toledo. Lucas County (~430,000), the City of Toledo (~270,000), TARTA transit, and the University of Toledo are independently covered.

---

Ohio County-Level Compliance Guides

Detailed compliance guidance for Ohio's major counties:

• Franklin County Ohio government website accessibility — Franklin County Board of Commissioners, City of Columbus, COTA, Columbus Metropolitan Library, Ohio State University, Columbus City Schools, and Columbus State Community College
• Cuyahoga County Ohio government website accessibility — Cuyahoga County government, City of Cleveland, GCRTA, Cleveland Metropolitan School District, Cuyahoga Community College, and Cleveland State University

For comparison with Ohio's compliance picture, see:

• Texas government website accessibility — 254 counties, METRO, DART, VIA, and the largest state compliance landscape in the US
• Florida government website accessibility — 67 counties, 411 municipalities, and the full Title II compliance picture for another large state
• Government website ADA compliance 2027 — the complete guide to the federal rule and April 2027 deadline

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