Law / United States / Maryland

Maryland Digital Accessibility Policy for Executive Branch departments and agencies, including the WCAG 2.1 testing and conformance report duties they impose on vendors

Maryland Digital Accessibility Policy (Md. Code Ann., State Fin. and Proc. § 3.5-303(a)(1))

In force.

An accessibility requirements rule binding government bodies.

Obligation class
Governance
Conformance standard
WCAG 2.1 AA

What it requires

  • If you are a Maryland Executive Branch department or agency, identify and maintain an Accessibility Officer as the point of contact for the Department of Information Technology Office of Accessibility and the Maryland Department of Disabilities IT Accessibility Initiative (Maryland Digital Accessibility Policy, section 4.1.1).
  • Verify that the information technology and services you develop or procure are accessible before deployment, consistent with State law, regulations and the accessibility policies set by the Department of Information Technology (Maryland Digital Accessibility Policy, section 4.1.3).
  • Ensure that vendors test their IT solutions for compliance with WCAG 2.1 A and AA success criteria through manual and automated testing, including screen reader testing in multiple environments and mobile accessibility testing on iOS and Android devices during their development cycle (Maryland Digital Accessibility Policy, section 4.1.4).
  • Ensure that vendors deliver electronic content and documents that conform to WCAG 2.1 AA success criteria, including accessibility conformance reports submitted during information technology solicitations (Maryland Digital Accessibility Policy, section 4.1.6).
  • Ensure that all new electronic content, and existing documentation uploaded to your website or made available for dissemination, conforms to WCAG 2.1 AA success criteria (Maryland Digital Accessibility Policy, section 4.1.7).

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

Section 3.5-303(a)(1) of the State Finance and Procurement Article makes the Secretary of Information Technology responsible for developing, implementing, maintaining, revising and enforcing information technology policies, procedures and standards. The policy establishes the responsibilities of Maryland’s Executive Branch agencies for implementing the State’s nonvisual access laws and regulations.

The policy applies to all departments and agencies within the Executive Branch of State government. A department or agency must verify that the information technology and services it develops or procures are accessible before deployment, consistent with State law, regulations and the accessibility policies set by the Department of Information Technology.

A department or agency must ensure that vendors test their IT solutions for compliance with WCAG 2.1 A and AA success criteria through manual and automated testing. Vendors are required to conduct screen reader testing in multiple environments during their development cycle. Vendors are required to perform mobile accessibility testing on iOS and Android devices during their development cycle.

A department or agency must ensure that vendors deliver electronic content and documents that conform to WCAG 2.1 AA success criteria, including accessibility conformance reports submitted during information technology solicitations. The policy was announced by Governor Wes Moore and the Department of Information Technology Secretary on . The policy was revised on to address the Department of Justice’s Americans with Disabilities Act Title II requirements.

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 .