Accessibility requirements for Nevada government procurement
Nevada maintains its own IT accessibility standard in addition to the federal requirements that bind every jurisdiction.
What binds a Nevada purchase
ADA Title II — WCAG 2.1 Level AA
Applies to the web content and mobile apps of every state and local government entity in Nevada, whoever built the software. Compliance dates:
- 26 April 2027 — entities serving 50,000 or more
- 26 April 2028 — entities serving under 50,000, and special district governments
Software bought today will still be in service on those dates, which is what makes this a procurement question rather than an IT one.
Section 508 — where federal funds are involved
Governs federal procurement and reaches a great deal of Nevada spending through federal funding, including most public universities. It incorporates WCAG 2.0 Level AA, and adds chapter requirements that WCAG does not cover — functional performance, software, and support documentation.
If your solicitation cites Section 508, a WCAG-edition conformance report does not answer it. The editions explained.
Nevada digital accessibility (NRS 242.131)
Nev. Rev. Stat. § 242.131
Nevada commits to access to electronic and information technology, including web pages and PDFs, against WCAG 2.2 Levels A and AA and WAI-ARIA — a version ahead of the WCAG 2.1 Level AA that ADA Title II requires, which matters when a vendor's report is written to 2.1.
Read Nevada’s own pageWhat Nevada names, and what the ADA now requires
Nevada’s own standard
WCAG 2.2 Levels A and AA, with WAI-ARIA
ADA Title II, from 26 April 2027
WCAG 2.1 Level AA
The state standard is the higher bar
Nevada names a later version of WCAG than ADA Title II does. Most vendor conformance reports are written to WCAG 2.1 or to Section 508 — so a report that fully satisfies the federal requirement can still leave the Nevada requirement unanswered, and the criteria added in the later version are exactly the ones no one will have tested.
What this means when a vendor sends you a report
- Name the standard in the solicitation. The edition a vendor sends back is chosen to match what you asked for. Ask for nothing specific and you will get the edition that flatters the product.
- Ask during evaluation, not after award. Before the contract your leverage is the award itself; after it, your leverage is a change order.
- Keep the record. What you required, what the vendor disclosed, what you challenged and when. If conformance is ever questioned, that record is the useful artifact — not the software.
Section508.gov — State-level Accessibility Law and Policy does not list Nevada. The entry above was researched from Nevada’s own statute, regulation or policy page in August 2026 and links to it directly. General guidance for procurement planning, not legal advice — verify against the statute or policy that applies to your entity, and check the current status of any pending legislation named above.