All state guides » Ohio Title II accessibility
Ohio Title II accessibility: April 2026 deadline + Ohio Civil Rights Act + state IT accessibility
Ohio public-entity websites face the federal DOJ Title II rule (April 2024) with its April 24, 2026 WCAG 2.1 Level AA deadline for entities serving 50,000 or more (April 24, 2027 for smaller entities and special-purpose districts). Ohio adds two state-level layers. The Ohio Civil Rights Act (R.C. Chapter 4112) prohibits disability discrimination in places of public accommodation and is enforced by the Ohio Civil Rights Commission. InnovateOhio (the state's enterprise IT office, formerly the Office of Information Technology) maintains a state-IT accessibility policy that references WCAG conformance for state agencies. Ohio does not have a damage-multiplier statute equivalent to California's Unruh Act; the Ohio Civil Rights Act provides actual damages and attorney's fees but no statutory multiplier.
Short answer: if your entity is an Ohio state agency, county, municipality, township, school district, public university, community college, library system, or special district, you are covered by DOJ Title II and must meet WCAG 2.1 Level AA on your website by April 24, 2026 (population 50,000+) or April 24, 2027 (smaller). The Ohio Civil Rights Act adds a state-law cause of action. InnovateOhio's state-agency IT policy applies to state agencies but not directly to local entities. Site Brace audits any Ohio public entity for $149 flat. Try a free single-page check on your homepage first.
The federal Title II deadlines:
- April 24, 2026: public entities serving populations of 50,000 or more.
- April 24, 2027: public entities serving populations under 50,000, and all special-purpose districts regardless of population.
Both deadlines apply to website content and mobile apps. WCAG 2.1 Level AA is the named conformance standard. Source: 28 CFR Part 35, published in the Federal Register April 24, 2024.
The rules that apply in Ohio
1. ADA Title II (federal)
The DOJ's April 2024 final rule is the load-bearing requirement for Ohio public entities. Coverage and deadlines as above. See the DOJ Title II primer for the federal-rule overview.
2. Ohio Civil Rights Act (R.C. Chapter 4112)
The OCRA prohibits discrimination based on disability in places of public accommodation, including state and local government services. Enforcement is through the Ohio Civil Rights Commission (OCRC). The OCRA provides for actual damages and attorney's fees; there is no statutory-damages multiplier comparable to California's Unruh Act. Federal Title II complaints are typically the more impactful procedural route, but a parallel OCRA claim is available and adds a state-law venue.
3. InnovateOhio state-IT accessibility policy
InnovateOhio (within the Ohio Department of Administrative Services) maintains the state-IT accessibility policy that requires Ohio state-agency systems to meet WCAG conformance. The policy is operationalized through procurement requirements and an internal accessibility coordinator network. The policy applies to Ohio state agencies and to entities receiving meaningful state IT support; it does not directly cover counties, municipalities, townships, school districts, or library systems, which fall under the federal DOJ Title II rule for their own websites.
For most Ohio public entities, the federal Title II rule and the OCRA are the load-bearing pieces. State agencies have the InnovateOhio policy on top. Ohio does not stack a damage-multiplier layer the way California does.
Which Ohio entities are covered
Coverage is broad:
- All Ohio state agencies
- 88 counties
- Approximately 940 incorporated municipalities (cities, villages)
- 1,308 townships (Ohio has the township layer with active local government)
- 610+ school districts (K-12, including local, exempted village, city, and joint-vocational)
- 23 community colleges and technical colleges
- The University System of Ohio (14 public universities including Ohio State, Cincinnati, Toledo, Akron, Bowling Green, Kent State, Miami University, Ohio University, Wright State, Cleveland State, Youngstown State, Shawnee State, Central State, and the regional campuses)
- Public library systems (Ohio has a strong public-library structure)
- Special districts (park, sanitary, transit, port authorities, conservancy districts)
The federal population threshold determines which deadline applies. Cuyahoga County (1.25M), Franklin County (1.32M), Hamilton County (820K), and the metros of Columbus (905K), Cleveland (370K), Cincinnati (310K), Toledo (270K), Akron (190K), and Dayton (138K) fall under April 24, 2026. Smaller counties, villages, and townships have until April 24, 2027.
What we typically find on an Ohio public-entity site
The municipal CMS ecosystem in Ohio looks like the rest of the country. CivicPlus, Granicus, OpenCities, Revize, and Streamline serve a large share of Ohio counties and cities; townships often run lighter custom WordPress or older platforms.
| Finding | axe-core rule | Typical cause |
|---|---|---|
| Untagged PDFs (board agendas, RFPs, public-records requests, permit forms) | Manual finding | PDFs exported from Word without accessibility tagging |
| Color contrast on navigation, calls to action, and table cells | color-contrast |
Vendor CMS template colors that fail 4.5:1 |
| Form fields without labels on permit and public-records request forms | label |
Custom form builders and vendor form tools that style placeholder text as label |
| Township-site clutter from older CMS or legacy custom builds | Various | Ohio has 1,300+ townships, many on circa-2010 platforms with significant accessibility debt |
| Streaming-video board archives without captions | Manual finding | Live-streamed council and trustee meetings posted without post-production captioning |
| aria-label on generic elements | aria-prohibited-attr |
CMS theme customizations or overlay injection. See aria-label on a div. |
| Heading hierarchy mistakes on department and program pages | heading-order |
CMS WYSIWYG editors that allow staff to skip heading levels |
| Document libraries with non-descriptive link text | link-name |
Long lists of "Click here" or "Download" links rather than meaningful titles |
Notes on Ohio's three largest metros
Columbus, Cleveland, and Cincinnati each have dedicated city web teams that have iterated on accessibility for years. Recent city-level redesigns generally ship cleaner accessibility baselines than older county or township platforms. Individual department subsites within the cities (Parks, Public Health, Recreation, Utilities) often diverge from the citywide standard because they are owned by department staff with less web-accessibility coverage. The federal Title II rule applies to the city as a whole, including those department subsites.
Why overlays are a poor fit for Ohio public entities
Accessibility overlays are heavily marketed to Ohio municipalities and townships. We have written about why accessibility overlays do not actually make sites WCAG-compliant in detail. For Ohio specifically: the InnovateOhio state-agency IT policy is a substantiation regime, and an overlay subscription does not substantiate. Local entities face the same Title II substantiation expectation. The FTC's April 2025 settlement with accessiBe makes overlay compliance claims a documented liability.
How Site Brace audits an Ohio public-entity site
The standard page mix for an Ohio public-entity audit:
- Homepage
- Department landing pages (top 4-6, varies by entity type)
- Governing body page (City Council, Board of Trustees, County Commission, School Board, etc.)
- Most-trafficked service pages (permits, utility billing, property tax, public-records requests)
- Public meeting calendar
- Document library or board-agenda archive
- ADA accessibility statement (if one exists)
- Privacy policy, contact
That mix covers up to 25 pages depending on the entity. The audit runs axe-core 4.10, captures element-level screenshots of every contrast failure, and packages findings into a written report with copy-paste fix code and 12 re-scans included over 12 months.
Pricing is $149 flat, one-time. To see what the report looks like, view a sample report we built for a fictional municipality.
Want to check your own site first? Run a free single-page check on your homepage or your most-trafficked service page - one URL, about a minute, no signup needed to see the result.
Start an Ohio public-entity audit, $149
Related:
- Illinois Title II accessibility - the Midwest neighbor with a stronger state-IT accessibility statute (IITAA)
- Pennsylvania Title II accessibility - the comparable Mid-Atlantic state without a damage-multiplier statute
- DOJ Title II web rule primer
- Free single-page WCAG check
- Why accessibility overlays do not make sites WCAG-compliant