Skip to main content

Training

State Accessibility Laws, A to Z

Last checked: November 1, 2026. Reference, not legal advice. Laws change; each entry shows the date it was checked. Federal laws apply in every state and are listed once, on the Federal Accessibility Laws page.

Jump to a state: Alabama · Alaska · Arizona · Arkansas · California · Colorado · Connecticut · Delaware · District of Columbia · Florida · Georgia · Hawaii · Idaho · Illinois · Indiana · Iowa · Kansas · Kentucky · Louisiana · Maine · Maryland · Massachusetts · Michigan · Minnesota · Mississippi · Missouri · Montana · Nebraska · Nevada · New Hampshire · New Jersey · New Mexico · New York · North Carolina · North Dakota · Ohio · Oklahoma · Oregon · Pennsylvania · Rhode Island · South Carolina · South Dakota · Tennessee · Texas · Utah · Vermont · Virginia · Washington · West Virginia · Wisconsin · Wyoming

Alabama

In short: Alabama has no state law; an older state information technology (IT) standard (2011) points agencies to Section 508.

  • State law: No state-specific digital accessibility law found.
  • State rules or standards: State IT Standard 530S2-00, "Universal Accessibility" (released 2011), https://oit.alabama.gov/oit-blob-wps-01/wp-content/uploads/2022/07/Standard_530S2_Universal_Accessibility-1.pdf; Web Content Accessibility Guidelines (WCAG) version named: Section 508 (no WCAG version required)
  • Who it covers: Executive branch agencies, boards and commissions (alabama.gov and state.al.us sites)
  • State accessibility office or contact: Office of Information Technology (OIT), https://oit.alabama.gov
  • Checked: 2026-11-01
  • Notes: The standard is old and refers to the pre-2017 Section 508 rules. OIT points agencies to the federal Americans with Disabilities Act (ADA) Title II rule (WCAG 2.1 AA).

Alaska

In short: Alaska has no specific law; a 2022 state policy requires Section 508 and current WCAG A and AA for executive agencies.

  • State law: No state-specific digital accessibility law found. The policy relies on general statutes Alaska Statutes (AS) 18.80.255 and AS 39.28.055.
  • State rules or standards: Dept. of Administration, "Accessibility of Information and Communication Technology" policy (Aug 4, 2022), https://doa.alaska.gov/ada/policy/AccessibilityofInfoandCommTechPolicy.pdf; WCAG version named: Section 508, plus the "latest version" of WCAG at Level A and AA
  • Who it covers: Executive branch agencies; state-hosted, state-procured or state-funded information and communication technology (ICT) (which reaches vendors)
  • State accessibility office or contact: Department of Administration (DOA) ADA Compliance Program, https://doa.alaska.gov/ada/contact.html
  • Checked: 2026-11-01
  • Notes: WCAG 2.2 is mentioned only as an optional higher target.

Arizona

In short: Arizona has no specific law; a 2008 statewide policy points state agencies to Section 508.

  • State law: No state-specific digital accessibility law found. The policy relies on Arizona Revised Statutes (A.R.S.) § 41-3504 (the state IT agency's power to set standards).
  • State rules or standards: Statewide Policy P130, "Web Site Accessibility" (effective Sept 12, 2008), https://aset.az.gov/sites/default/files/P130%20Web%20Site%20Accessibility%20Policy_1.pdf; WCAG version named: Section 508 (no WCAG)
  • Who it covers: State budget units. Excludes the state universities, community colleges, the Legislature and the courts.
  • State accessibility office or contact: Arizona Department of Administration, Arizona Strategic Enterprise Technology (ADOA-ASET), https://aset.az.gov
  • Checked: 2026-11-01
  • Notes: No newer statewide standard confirmed.

Arkansas

In short: Arkansas law requires state technology to be accessible to people who are blind or visually impaired.

  • State law: Information technology access for people who are blind or visually impaired: Act 1227 of 1999, amended by Act 750 (2011), Act 308 (2013) and Act 218 (2019); Arkansas Code Title 25, Ch. 26 (§ 25-26-204 confirmed). https://sas.arkansas.gov/state-technology/policies-standards/technology-legislation/
  • State rules or standards: Nonvisual access standards set by the state IT office (citation and URL Not verified); WCAG version named: Not verified
  • Who it covers: State agencies and entities that use public funds; IT purchases (vendors, through a contract clause)
  • State accessibility office or contact: Division of Information Systems / State Technology, https://sas.arkansas.gov
  • Checked: 2026-11-01
  • Notes: Full section range Not verified. Act 1301 (2003) exempts technology that is visual by nature.

California

In short: California law requires state entities to follow Section 508, and agency websites to certify WCAG 2.1 AA every two years.

Colorado

In short: Colorado law requires state agencies and local governments to meet WCAG 2.1 AA, with fines for violations.

  • State law: HB21-1110 (Colorado Revised Statutes (C.R.S.) § 24-34-802 and the OIT statutes); SB23-244; HB24-1454, https://leg.colorado.gov/bills/hb21-1110
  • State rules or standards: 8 Colorado Code of Regulations (CCR) 1501-11, Technology Accessibility Rules, https://oit.colorado.gov/accessibility-law; WCAG version named: WCAG 2.1 AA (and Section 508)
  • Who it covers: State agencies, local governments, and platform providers (including vendors)
  • State accessibility office or contact: Governor's Office of Information Technology (OIT), https://oit.colorado.gov/accessibility-law
  • Checked: 2026-11-01
  • Notes: Full compliance was due July 1, 2024. A good-faith liability shield ended July 1, 2025. Courts can fine $3,500 per violation. Rules amended May 2025.

Connecticut

In short: Connecticut has no specific law; a 2025 state policy requires WCAG 2.1 AA for executive agencies.

  • State law: No state-specific digital accessibility law found. The policy relies on Connecticut General Statutes (C.G.S.) §§ 4-5, 4-8, 4-65a, 4-66, 4d-1(3) and 4d-8a.
  • State rules or standards: "Accessibility & Inclusivity Policy for Websites and Digital Assets" v5.0 (effective July 14, 2025), https://portal.ct.gov/accessibility/-/media/sitecore-center/accessibility/it-accessibility-policy-final-for-release-07142025.pdf; WCAG version named: WCAG 2.1 AA
  • Who it covers: Executive branch state agencies: websites, documents, apps, forms, media and software. The Legislature and courts are encouraged to adopt it.
  • State accessibility office or contact: Accessibility in CT (Office of Policy and Management (OPM) policy; the Department of Administrative Services, Bureau of Information Technology Solutions (DAS-BITS) runs the feedback form), https://portal.ct.gov/accessibility
  • Checked: 2026-11-01
  • Notes: Replaces the 2019 policy v4.1. New content must comply now; existing content is fixed by priority.

Delaware

In short: Delaware has no digital-specific law; a 2026 state policy requires WCAG 2.1 AA for state digital services.

District of Columbia

In short: DC has no verified digital accessibility law; its government website policy points to Section 508.

Florida

In short: Florida law requires state agencies to buy technology that meets Section 508.

  • State law: Florida Statutes (Fla. Stat.) §§ 282.601–282.606, "Accessibility of Information and Technology," https://www.flsenate.gov/Laws/Statutes/2013/Chapter282/PART_II
  • State rules or standards: Florida Administrative Code Ch. 60-8 (e.g. Rule 60-8.003, effective Jan 23, 2007), https://flrules.org/Gateway/View_notice.asp?id=4837892; WCAG version named: Section 508 (through § 282.603 and 36 CFR 1194); no WCAG stated
  • Who it covers: State agencies, for technology bought on or after July 1, 2006
  • State accessibility office or contact: Department of Management Services, https://www.dms.myflorida.com (office URL Not verified)
  • Checked: 2026-11-01
  • Notes: Undue-burden exception requires another way to get the information. Full rule text not confirmed.

Georgia

In short: Georgia has no specific law; a state standard requires WCAG 2.1 AA for state digital properties.

  • State law: No state-specific law found
  • State rules or standards: Georgia Technology Authority (GTA) Digital Accessibility Standard SM-19-002, https://gta-psg.georgia.gov/node/776 and the Digital Services Georgia version, https://digital.georgia.gov/node/38; WCAG version named: WCAG 2.1 AA
  • Who it covers: All digital properties run by state entities: websites, web apps, mobile apps and online documents
  • State accessibility office or contact: Digital Services Georgia (GTA), https://digital.georgia.gov/digital-accessibility-poc
  • Checked: 2026-11-01
  • Notes: The standard took effect 8/28/2019. It names no state statute as its authority, only other GTA policies.

Hawaii

In short: Hawaii law (2022) requires state entities, public schools and the university to meet WCAG 2.1 AA.

Idaho

In short: Idaho has no specific law; a state web standard requires WCAG 2.1 AA for public state websites.

  • State law: No state-specific law found
  • State rules or standards: Idaho Technology Authority (ITA) Standard S5120 Web Publishing (issued under Idaho Code 67-833), https://ita.idaho.gov/wp-content/uploads/2025/07/S5120-ADA.pdf; WCAG version named: WCAG 2.1 AA, plus AAA criterion 3.2.5
  • Who it covers: Public-facing state websites and web apps on idaho.gov
  • State accessibility office or contact: Office of Information Technology Services (ITS), digitalada@its.idaho.gov, https://its.idaho.gov/progress-toward-ada-title-ii-compliance/
  • Checked: 2026-11-01
  • Notes: The standard was revised 7/24/2025 for ADA compliance. ITS is working to the federal 4/26/2027 deadline.

Illinois

In short: Illinois law (IITAA) requires state entities and public universities to meet WCAG 2.1 AA.

Indiana

In short: Indiana law covers state agency technology accessibility; the state standard names WCAG 2.1 and Section 508.

  • State law: Indiana Code 4-13.1-3 (IT accessibility for state agencies), cited at https://www.in.gov/core/accessibility/
  • State rules or standards: IN.gov accessibility standard, https://www.in.gov/core/accessibility/; WCAG version named: WCAG 2.1 and Revised Section 508
  • Who it covers: State agency IT used by the public or by state employees
  • State accessibility office or contact: Indiana Office of Technology, IN.gov team, INgovManagement@iot.IN.gov, https://www.in.gov/core/accessibility/
  • Checked: 2026-11-01
  • Notes: Statute section numbers and effective date: Not verified (official text could not be opened). The in.gov page does not name a WCAG level.

Iowa

In short: Iowa has no specific law; a state policy requires WCAG 2.1 AA and encourages WCAG 2.2.

  • State law: No state-specific law found
  • State rules or standards: Digital Accessibility Policy ADMN.303.02.E (cites Iowa Code 8.77 and 8.85), https://policies.iowa.gov/dom/policy/digital-accessibility-policy/; WCAG version named: WCAG 2.1 AA, with WCAG 2.2 AA encouraged
  • Who it covers: The Department of Management and the entities it supports, including employees, contractors and vendors. Vendors must provide an Accessibility Conformance Report.
  • State accessibility office or contact: Iowa Department of Management (formerly the Office of the Chief Information Officer, OCIO), 515-281-3322, https://policies.iowa.gov/dom/policy/digital-accessibility-policy/
  • Checked: 2026-11-01
  • Notes: The policy took effect 9/1/2026 and expires 8/31/2027. Its compliance deadline is 4/26/2027.

Kansas

In short: Kansas has no specific law; a state policy requires WCAG 2.1 AA for state entities and contractors.

Kentucky

In short: Kentucky law requires accessible technology in state agencies and state-funded bodies.

  • State law: Accessible Information Technology (AIT) law, Kentucky Revised Statutes (KRS) 61.980 to 61.988, https://apps.legislature.ky.gov/record/00rs/HB1032.htm (2000 bill record)
  • State rules or standards: Technology access clause and standards set by the Finance and Administration Cabinet (KRS 61.984), with Commonwealth Office of Technology (COT) guidance at https://technology.ky.gov/help/Tutorials/KY%20ADA%20Guidance%20Document.pdf; WCAG version named: Section 508 in the law, WCAG 2.1 in the COT guidance
  • Who it covers: State agencies and state-funded bodies such as universities, school systems and political subdivisions, plus IT vendors through contract clauses
  • State accessibility office or contact: Commonwealth Office of Technology, https://technology.ky.gov/
  • Checked: 2026-11-01
  • Notes: The law took effect 7/14/2000; people can sue in circuit court for injunctive relief. Current statute text: Not verified (could not be opened on the official site).

Louisiana

In short: Louisiana has no specific law; a state rule requires WCAG 2.1 AA for executive branch agencies.

  • State law: No state-specific law found. The rule's authority is Louisiana Revised Statutes (La. R.S.) 39:8.
  • State rules or standards: PPM 74, Web Accessibility Compliance (Louisiana Administrative Code (LAC) 4:V, Chapter 61), https://www.doa.la.gov/media/gs0hee2m/ppm-74-web-accessibility-compliance-r6-25-a11y.pdf; WCAG version named: WCAG 2.1 AA
  • Who it covers: Executive branch boards, commissions, departments and agencies
  • State accessibility office or contact: Office of State ADA Coordinator, with Office of Technology Services support, https://accessibility.ots.la.gov
  • Checked: 2026-11-01
  • Notes: The June 2025 revision lowered the minimum from WCAG 2.2 to 2.1. The content compliance date in the rule is 4/24/2026.

Maine

In short: Maine has no specific law; a state policy requires WCAG 2.1 A and AA for state agencies.

  • State law: No state-specific law found. The policy's authority is 5 Maine Revised Statutes (M.R.S.) §1973 (CIO powers).
  • State rules or standards: Digital Accessibility and Usability Policy v3.1, https://www.maine.gov/oit/policies/DigitalAccessibilityPolicy.pdf; WCAG version named: WCAG 2.1 A/AA
  • Who it covers: State agencies under the CIO, for public and some internal content and software, plus vendors
  • State accessibility office or contact: Office of Information Technology Accessibility Team, https://www.maine.gov/oit/accessibility/index.html
  • Checked: 2026-11-01
  • Notes: First issued 12/20/2019; last revised 5/29/2026. Archived and unchanged legacy services are exempt.

Maryland

In short: Maryland law requires nonvisual access in state IT buying; a state policy requires WCAG 2.1 AA.

Massachusetts

In short: Massachusetts has no specific law; a 2025 state policy requires WCAG 2.1 AA or later for executive agencies.

  • State law: No state-specific digital accessibility law found. The Executive Office of Technology Services and Security (EOTSS) issues the policy under its general IT power, Massachusetts General Laws (M.G.L.) c. 7D § 3 (official URL: Not verified).
  • State rules or standards: EOTSS Enterprise Digital Accessibility Policy, https://www.mass.gov/policy-advisory/enterprise-digital-accessibility-policy; WCAG version named: WCAG 2.1 AA or later
  • Who it covers: Executive Department agencies, other entities that use EOTSS services such as mass.gov, and contractors who build digital assets for them.
  • State accessibility office or contact: EOTSS ACCESS (Accessibility Center for Consulting, Education and Support Services), EOTSS-ACCESS@mass.gov, https://www.mass.gov/digital-accessibility-policy-requirements
  • Checked: 2026-11-01
  • Notes: Policy published 2025-08-01. A Digital Accessibility and Equity Governance Board advises EOTSS.

Michigan

In short: Michigan has no specific law; a state standard requires WCAG 2.1 AA for executive branch agencies.

  • State law: No state-specific law found.
  • State rules or standards: Department of Technology, Management and Budget (DTMB) IT Technical Standard 1360.00.11, State of Michigan (SOM) Digital Standards for Websites and Applications, plus Admin Guide policies 1650.00–1650.02, https://www.michigan.gov/som/footer/policies/som-applications-and-site-standards; WCAG version named: WCAG 2.1 AA
  • Who it covers: Executive branch departments and agencies: websites, apps, documents, and content from contractors and third parties.
  • State accessibility office or contact: DTMB and eMichigan, https://www.michigan.gov/digitalstandards
  • Checked: 2026-11-01
  • Notes: Standard effective 2025-05-27. Michigan adopted WCAG 2.1 AA in May 2024.

Minnesota

In short: Minnesota law requires state agencies to follow a state standard that now uses WCAG 2.1 AA.

Mississippi

In short: Mississippi has no state law or statewide standard that could be found.

  • State law: No state-specific law found.
  • State rules or standards: No state standard found. The ms.gov accessibility policy names no standard: https://www.ms.gov/accessibility-policy; WCAG version named: none stated
  • Who it covers: Not verified
  • State accessibility office or contact: Not verified. The state IT agency is Mississippi ITS, https://www.its.ms.gov
  • Checked: 2026-11-01
  • Notes: ITS procurement manual only partly checked.

Missouri

In short: Missouri law requires accessible state technology; the state standard now uses WCAG 2.2 AA.

  • State law: Revised Statutes of Missouri (RSMo) 161.935 (part of §§ 161.900–161.945). Requires accessible ICT when the state develops, buys, maintains, or uses it, including through contracts and grants. https://at.mo.gov/?p=6709
  • State rules or standards: Missouri State ICT Standard 3.0 (2024), https://moat.mo.gov/info-tech-standards/; WCAG version named: WCAG 2.2 A/AA (was 2.1), plus Section 508
  • Who it covers: State agencies in all three branches, plus public colleges and universities.
  • State accessibility office or contact: Missouri Assistive Technology (MoAT) with the Office of Administration, Information Technology Services Division (OA-ITSD), https://moat.mo.gov/info-tech-standards/
  • Checked: 2026-11-01
  • Notes: v3.0 approved 2024-09-13. WCAG 2.2 took effect 2025-10-05; agencies had to comply by 2026-04-06.

Montana

In short: Montana law requires nonvisual access in state technology buying; the state names WCAG 2.1 AA.

  • State law: Montana Code Annotated (MCA) 18-5-601 to 18-5-605 (Nonvisual Access Technology Procurement, House Bill (HB) 239 of 2001). https://sitsd.mt.gov/Accessibility/Policy-Legislation
  • State rules or standards: State of Montana Accessibility Policy, https://mt.gov/discover/disclaimer; WCAG version named: WCAG 2.1 AA (per the State Information Technology Services Division (SITSD)); the policy page references Section 508.
  • Who it covers: State agencies. An agency can be excused if it finds in good faith that compliance would be an undue burden.
  • State accessibility office or contact: Dept. of Administration, SITSD, https://doa.mt.gov/sitsd/accessibility
  • Checked: 2026-11-01
  • Notes: SITSD lists the ADA Title II deadline as 2026-04-24 (federal date has since moved). The policy has no number.

Nebraska

In short: Nebraska's state standard requires Section 508 and the federal Title II rule for state agencies.

  • State law: Not verified. Nebraska Revised Statutes (Neb. Rev. Stat.) 73-205 is the likely source; its official text could not be opened.
  • State rules or standards: Nebraska Information Technology Commission (NITC) Standard 2-101 (Accessibility), https://nitc.nebraska.gov/docs/chapter-2-accessibilty.pdf; WCAG version named: Revised Section 508 (36 CFR 1194) plus 28 CFR 35 Subpart H
  • Who it covers: State agencies, for ICT they buy, build, maintain, or use. Vendors are bound through the technology access clause.
  • State accessibility office or contact: NITC, https://nitc.nebraska.gov/standards-and-guidelines/
  • Checked: 2026-11-01
  • Notes: 2-101 amended 2025-07-11. The vendor clause is now kept by DAS; its page returned an error.

Nevada

In short: Nevada state guidelines require WCAG AA for state agencies; official pages disagree on 2.0 or 2.1.

New Hampshire

In short: New Hampshire has no specific law; a state policy requires WCAG 2.1 AA for state agencies.

New Jersey

In short: New Jersey law covers school websites only; state IT contract language points to Section 508.

  • State law: New Jersey Statutes Annotated (N.J.S.A.) 18A:36-35.1 (school websites only), https://nj.gov/education/atoz/digital_accessibility.shtml. No enacted law for state agency websites found.
  • State rules or standards: NJ Office of Information Technology web accessibility contract language, https://www.nj.gov/it/ps/07-12-NJOIT_web_accessibility_policy.pdf; WCAG version named: WCAG 2.0 AA through Section 508 (OIT). The school law requires Level AA of the current WCAG, which NJ Education lists as WCAG 2.2.
  • Who it covers: School districts, charter schools, renaissance schools and the Katzenbach School for the Deaf. The OIT language covers vendors that build web systems.
  • State accessibility office or contact: NJ Office of Information Technology, https://www.nj.gov/it/. For schools, NJ Department of Education (link above).
  • Checked: 2026-11-01
  • Notes: Schools file a statement of assurance every 2 years. Bill S1016/A3636 (state agencies) not shown as enacted; status Not verified. A state-agency statute (N.J.S.A. 52:18A-237) listed by one secondary site: Not verified.

New Mexico

In short: New Mexico has no state law in force that could be confirmed; a 2026 bill was pending.

New York

In short: New York law requires state agencies to meet current WCAG AA; the state policy names WCAG 2.2 AA.

North Carolina

In short: North Carolina has no specific law; a state standard requires WCAG 2.1 AA for public state services.

  • State law: No digital-accessibility-specific statute found. The N.C. Department of Information Technology (NCDIT) standard cites North Carolina General Statutes (N.C.G.S.) 143B-1320(a)(17), 143B-1376 and 75-61(10) (official URL Not verified).
  • State rules or standards: NCDIT Digital Accessibility and Usability Standard v1.1 (January 16, 2025), https://it.nc.gov/documents/digital-accessibility-usability-standard/open; WCAG version named: WCAG 2.1 AA
  • Who it covers: Public-facing websites and digital services of state agencies, including those run by contractors
  • State accessibility office or contact: N.C. Department of Information Technology, https://it.nc.gov/accessibility
  • Checked: 2026-11-01
  • Notes: v1.0 issued April 5, 2024. Statewide accessibility support service began August 2025.

North Dakota

In short: North Dakota has no specific law; a state policy requires WCAG 2.1 AA for executive agencies.

  • State law: No state-specific law found. The policy cites North Dakota Century Code (NDCC) 54-59-09 and NDCC 14-02.4-14 and 14-02.4-15.
  • State rules or standards: North Dakota Information Technology (NDIT) Policy POL0030001, Revision 1, https://ndit.nd.gov/node/165752; WCAG version named: WCAG 2.1 AA
  • Who it covers: Executive branch state agencies, including the University System Office (web content and mobile apps)
  • State accessibility office or contact: NDIT, https://www.ndit.nd.gov/support/digital-accessibility-hub
  • Checked: 2026-11-01
  • Notes: Effective January 1, 2025. NDIT target date April 26, 2027.

Ohio

In short: Ohio has no specific law; a state policy requires WCAG 2.1 AA for state agencies.

  • State law: No digital-accessibility-specific statute found. Policy IT-09 cites Ohio Revised Code (ORC) 125.18 (official URL Not verified).
  • State rules or standards: Ohio Administrative Policy IT-09, Digital Accessibility, https://das.ohio.gov/technology-and-strategy/policies/it-09; WCAG version named: WCAG 2.1 AA
  • Who it covers: State agencies, boards and commissions under the Governor
  • State accessibility office or contact: Ohio Department of Administrative Services (DAS), https://das.ohio.gov/technology-and-strategy/policies/it-09
  • Checked: 2026-11-01
  • Notes: Effective January 10, 2025. Outsourced work and accessibility statement requirement: Not verified (official Portable Document Format (PDF) could not be opened).

Oklahoma

In short: Oklahoma law (2004) requires accessible state technology; the state standard requires WCAG 2.1 AA.

Oregon

In short: Oregon has no confirmed law; state guidance requires WCAG 2.1 AA for Oregon.gov websites.

Pennsylvania

In short: Pennsylvania has no specific law; a 2026 state policy requires WCAG 2.1 AA for agencies and vendors.

  • State law: No state-specific law found. The policy rests on Executive Order 2016-06 (IT governance).
  • State rules or standards: OA/IT Digital Accessibility Policy (October 5, 2026), https://pa.gov/content/dam/copapwp-pagov/en/oa/documents/policies/it-policies/digital%20accessibility%20policy.pdf; WCAG version named: WCAG 2.1 AA minimum (current WCAG at AAA encouraged), plus Revised Section 508
  • Who it covers: Agencies under the Governor, any entity on the Commonwealth network, and vendors, licensors and contractors
  • State accessibility office or contact: Office of Administration, Office for Information Technology (contact URL Not verified)
  • Checked: 2026-11-01
  • Notes: Replaces the November 12, 2025 version and older ITP-ACC001. Next review October 2028.

Rhode Island

In short: Rhode Island has no specific law; its state web policy names no standard.

  • State law: No state-specific law found. Bill H 7159 (2024) was held for further study, https://webserver.rilegislature.gov/BillText24/HouseText24/H7159.htm
  • State rules or standards: RI.gov accessibility policy (no number or date), https://www.ri.gov/policies/access/; WCAG version named: none stated
  • Who it covers: Official State of Rhode Island web portals and agency web developers
  • State accessibility office or contact: Not verified (RI.gov general contact only)
  • Checked: 2026-11-01
  • Notes: Similar bills in 2022 and 2023 not shown as enacted.

South Carolina

In short: South Carolina has no state law or statewide agency standard; each agency sets its own.

South Dakota

In short: South Dakota has no specific law; state web standards point to WCAG 2.0 and Section 508.

  • State law: No state-specific law found
  • State rules or standards: Bureau of Information and Telecommunications (BIT) web development standards, https://public.sd.gov/accpolicy.aspx ; https://gfp.sd.gov/accessibility-ada; WCAG version named: WCAG 2.0 and Section 508 (no level stated)
  • Who it covers: State government websites
  • State accessibility office or contact: BIT Web Services, https://accessibility.sd.gov/
  • Checked: 2026-11-01
  • Notes: The statewide policy moved to an sd.gov knowledge-base article (KB0010219) that would not load; current text Not verified.

Tennessee

In short: Tennessee has no specific law; the state accessibility statement names WCAG 2.1 AA.

Texas

In short: Texas law requires accessible state technology; state rules point to Section 508 and the federal WCAG 2.1 AA rule.

Utah

In short: Utah state rules require WCAG 2.1 and Section 508 for executive agencies and vendors.

Vermont

In short: Vermont has no specific law; a state standard names WCAG 2.0 and Section 508, and state templates target WCAG 2.1 AA.

Virginia

In short: Virginia law requires accessible technology for state and local government and ties to the federal Title II rule.

  • State law: Information Technology Access Act, Virginia Code (Va. Code) § 2.2-3500 to -3505, https://law.lis.virginia.gov/vacodefull/title2.2/chapter35/
  • State rules or standards: Virginia Information Technologies Agency (VITA) Information Technology Resource Management (ITRM) Standard GOV103-00 (2005) and VITA IT accessibility page, https://www.vita.virginia.gov/policy--governance/policies-standards--guidelines/it-accessibility-and-website-standards; WCAG version named: the law ties to the federal Title II rule (28 CFR 35.200) and Section 508; GOV103 names WCAG 1.0 Level A (outdated)
  • Who it covers: State agencies, public school divisions, public higher education, local governments, and vendors (through an access clause)
  • State accessibility office or contact: VITA, https://www.vita.virginia.gov/ ; each covered entity must publish its own digital accessibility coordinator
  • Checked: 2026-11-01
  • Notes: HB2541 (2025, c. 571) rewrote the Act and added § 2.2-3505 (coordinator and a way to report barriers). Effective date Not verified.

Washington

In short: Washington state policy requires WCAG 2.2 AA for state agencies from July 1, 2026.

West Virginia

In short: West Virginia law requires state technology to be accessible to people who are blind or visually impaired.

  • State law: West Virginia Code (W. Va. Code) § 18-10N, "Information Technology Access for the Blind and Visually Impaired," https://code.wvlegislature.gov/18-10N/
  • State rules or standards: Access standards set by the Purchasing Division under § 18-10N-3, https://code.wvlegislature.gov/18-10N-3/ ; WV.gov accessibility statement, https://www.wv.gov/policies/accessibility; WCAG version named: Section 508 (WV.gov); none in the law
  • Who it covers: State agencies' IT and state procurement contracts
  • State accessibility office or contact: Department of Administration, Purchasing Division; Digital Accessibility Request Form via https://www.wv.gov/policies/accessibility
  • Checked: 2026-11-01
  • Notes: The law covers blind and visually impaired users only. Current Purchasing Division standards text: Not verified.

Wisconsin

In short: Wisconsin has no specific law; state web templates are checked against Section 508 and WCAG AA.

  • State law: No state-specific law found
  • State rules or standards: State agency web templates scanned for Section 508 and WCAG AA, https://webmasters.wi.gov/Pages/AgencyTemplates/Overview.aspx; WCAG version named: WCAG AA (version not stated) and Section 508. Statewide policy page: Not verified.
  • Who it covers: State agency websites built on the state templates
  • State accessibility office or contact: Not verified
  • Checked: 2026-11-01
  • Notes: Agencies must check content they add. Universities of Wisconsin have their own policy: https://www.wisconsin.edu/digital-accessibility/

Wyoming

In short: Wyoming has no specific law; a state web standard names no WCAG version.