Read the official website of the state of Missouri, and you’ll find a fairly standard web accessibility policy — with one curveball:
The State of Missouri is committed to making Missouri websites, documents, applications and services accessible to all [...]
We have developed our content to ensure compatibility with common adaptive technologies by utilizing the State of Missouri’s Accessibility Standard, which is based on Section 508 of the Rehabilitation Act (as amended) and Web Content Accessibility Guidelines 2.1. [emphasis added]
A growing number of states are instituting their “own" standards for web accessibility — and we put “own" in quotes because, to date, every single standard is identical with either the 2.1 or 2.0 standards of the Web Content Accessibility Guidelines (WCAG).
Missouri began developing its standards in 2014 with RSMo. 161.935, a law that requires the state to meet the digital accessibility requirements of Section 508 of the Rehabilitation Act.
Technically, government agencies in all states must meet those standards under Title II of the Americans with Disabilities Act (ADA) — but by establishing clear state-level standards, states can help to clarify the requirements for government agencies and their contractors.
State laws can also help private businesses develop their strategies for compliance with Title III of the ADA. All of those laws have similar requirements, but the penalties for non-compliance vary quite a bit (and if you’re new to digital accessibility laws, AudioEye provides an excellent introduction).
In this article, we’ll answer some questions about Missouri’s Accessibility Standard, which is also known as the Missouri Information Technology Accessibility Standard.
Does the Missouri Accessibility Standard apply to private businesses?
Not directly. The standard applies to state agencies; it may also affect the private businesses who market their services to those agencies. For example, if you’re building a web app for a Missouri agency, you’ll need to prove compliance with the Accessibility Standard.
Note that you might not ever hear the words “Missouri Accessibility Standard" when performing that work! Many state agencies will simply refer to “Section 508" or “ADA standards,” since the Missouri standard is identical to WCAG 2.1.
And while Missouri’s state standards aren’t applicable to private businesses, Title III of the ADA applies to all places of public accommodation (including websites). Per the DOJ, businesses in Missouri (and all 49 other states) should use WCAG 2.1 or later when testing for ADA compliance.
What are the penalties for non-compliance with the Missouri IT Accessibility Standard?
The standard doesn’t outline specific financial penalties. However, under Title II of the ADA — which applies to all state and local agencies — organizations can be fined, sued, or investigated by the Department of Justice (DOJ).
Once again, the Missouri Accessibility Standard is primarily intended to clarify existing requirements under federal law. It also establishes a council with the power to adopt accessibility standards, establish complaint procedures, and provide training and technical assistance.
Related: What's Next for US Web Accessibility Laws?
Why is the Missouri Web Accessibility Standard identical to WCAG 2.1?
Virtually every state, local, and federal accessibility law is aligned with some version of WCAG. That’s simply because WCAG is a well-supported international standard — it’s written by the World Wide Web Consortium (W3C), which also establishes the standards for HTML, CSS, and other web technologies.
The state of Missouri can change the standards at any time, and it’s possible that they will update the standard to WCAG 2.2 (currently, the latest version of the guidelines) at some point in the future.
Related: Understanding the Differences Between WCAG 2.1 and WCAG 2.2
What types of web accessibility issues does WCAG address?
According to the principles of WCAG, content must be Perceivable, Operable, Understandable, and Robust (the POUR principles). The guidelines are organized based on those principles.
WCAG is intended to address every accessibility issue, from low-contrast text (which may be unreadable for people with vision disabilities) to small pointer targets (which might be difficult to activate for people with motor disabilities).
Does WCAG have strict requirements about site design, colors, and so on?
That depends on your definition of “strict,” but generally, no. One of the most common myths about web accessibility is that following the rules will make content dull, boring, or ugly — but some of the most popular websites on the internet are highly accessible.
WCAG is written to apply to current and future technologies. To that end, it uses pass-or-fail statements called success criteria, which creators can use to test their content. That approach ensures that designers, developers, and other creators have some freedom to address each problem in a way that makes sense.
Related: WCAG Compliance, Explained (AudioEye)
How can I test my agency's website for compliance with Missouri's web accessibility standards?
Missouri Assistive Technology (MoAT) provides a testing guide and other resources, so if you’re operating a state agency, that’s an excellent place to start.
However, for Title II compliance, we strongly recommend working with an accessibility partner. Here’s why: WCAG testing requires a combination of manual and automated audits. Automated tools can find issues at scale, while manual checks can assess the barriers that fall outside of simple pass-or-fail rulesets.
Most web developers don’t have enough experience with screen readers and other assistive technologies (AT) to test content accurately. By involving users with disabilities and regular AT users in the testing, an accessibility partner can ensure that your website or app is actually usable with assistive technology.
Remember, web accessibility isn’t just a legal necessity; it impacts everything from brand perception to search engine optimization (SEO). Investing in accurate WCAG testing can dramatically improve your site’s performance — while also reducing your legal exposure.
To learn more, download our free guide: Essential Guide to ADA Accessibility Compliance for Websites. Or get started with a free automated web accessibility scan.
