Law / United States / Ohio

State agency web content and mobile application accessibility

Ohio Admin. Policy IT-09, Digital Accessibility, under Ohio Rev. Code Sec. 125.18(B)(3)

In force since .

An accessibility requirements rule binding government bodies.

What it requires

  • This binds every state agency, board or commission under the authority of the Governor, which section 125.18(B)(3) of the Revised Code directs to comply with the office of information technology's policies and standards; a state-supported institution of higher education falls outside section 125.18's definition of state agency (IT-09, Scope; R.C. 125.18(B)(3) and (I)(2)).
  • If you are a state agency, board or commission under the authority of the Governor, establish a digital accessibility strategy for the design, development, implementation and maintenance of the web content and mobile applications you make available to the public (IT-09, section III).
  • Make your public web content and mobile applications comply with WCAG 2.1 Level AA, in accordance with Title II of the Americans with Disabilities Act and 28 CFR Part 35, Subpart H, by (IT-09, sections III.A and III.H).
  • Adopt the design and content management standards for public-facing web pages that the InnovateOhio Platform team defines, as Ohio Administrative Policy IT-08 requires (IT-09, section III.A).
  • Place an accessibility statement on your home page and primary entry points, or link to one, and in each mobile application, stating WCAG 2.1 Level AA compliance and the steps taken to keep it where compliance is attained, giving a feedback mechanism for reporting accessibility issues, and linking to the state's ADA Coordinators Directory (IT-09, Accessibility Statements).
  • The exceptions and the conforming alternate versions that sections 35.201 and 35.202 of 28 CFR Part 35 set out apply to this standard (IT-09, Exceptions and Conforming Alternate Versions).

These lines are LexLint's reading of the law's text.

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Ohio Administrative Policy IT-09, Digital Accessibility, issued by the Department of Administrative Services, applies to all state agencies, boards and commissions under the authority of the Governor. Section 125.18(B)(3) of the Revised Code requires state agencies to comply with the policies and standards the office of information technology establishes for the use of common information technology. IT-09 names section 125.18 as its authority.

Each agency must establish a digital accessibility strategy for the design, development, implementation and maintenance of the web content and mobile applications it makes available to the public.

That web content and those mobile applications must comply with WCAG 2.1 Level AA, in accordance with Title II of the Americans with Disabilities Act and 28 CFR Part 35, Subpart H. Agencies must also adopt the design and content management standards for public-facing web pages that the InnovateOhio Platform team defines, as Ohio Administrative Policy IT-08 requires.

The exceptions in section 35.201 of 28 CFR Part 35 cover archived web content, preexisting conventional electronic documents, certain content posted by third parties, individualized, password-protected or otherwise secured conventional electronic documents, and preexisting social media posts.

An agency must place an accessibility statement on its home page and primary entry points, or link to one, and include one in each mobile application, with a statement of WCAG 2.1 Level AA compliance where attained and a feedback mechanism for reporting accessibility issues. Agency web content and mobile applications must be compliant by . The policy updated that compliance date on , based on the extension from the U.S. Department of Justice.

The current version took effect , when the policy was revised to align with Subpart H of 28 CFR Part 35; the policy was first issued .

When LexLint raises it

When your app profile says your app ships a consumer interface or ships a mobile app.

Back to the example  ·  Lint your app

Page updated .