Las Vegas City WCAG Requirements for Contractors
Las Vegas, Nevada contractors working on city projects must follow digital accessibility expectations included in contracts and standards adopted or referenced by the city. This guide summarizes how WCAG requirements are applied to contractor deliverables, who enforces them, and the practical steps to document and deliver compliant digital assets for public projects in Las Vegas.
Overview
Contract language for Las Vegas projects frequently requires deliverables that meet recognized accessibility standards such as WCAG 2.1 AA or equivalent testing results. Where the city adopts technical standards for buildings and public services, contractors must follow those adoption instruments and any contract-specific scope and deliverables. For web and digital content, contract specifications and technical exhibits define the test level and acceptance criteria.
Penalties & Enforcement
Enforcement for accessibility deficiencies on city projects is handled through contract compliance, purchasing, and applicable permitting or code enforcement processes. Specific monetary fines or per-day penalties for digital accessibility noncompliance are not specified on the cited municipal code page; enforcement typically proceeds through contract remedies, corrective orders, withholding of payments, and, if necessary, legal action by the city"[1].
- Monetary fines: not specified on the cited page; contract remedies and withholding are typical.
- Escalation: corrective notice, cure period, withheld payments, then potential contract termination or legal claims.
- Non-monetary sanctions: corrective orders, required remediation, suspension of acceptance, and court actions.
- Enforcer and complaints: Purchasing/contract compliance typically oversees contractor obligations for accessibility; building or IT departments may inspect technical deliverables.
Applications & Forms
The city does not publish a single, universal "WCAG compliance" form for contractors; submission requirements are set in the contract documents and vendor instructions found through Purchasing. For specific contract solicitations, follow the vendor submission and acceptance instructions posted by City Purchasing"[2].
- Required documents: accessibility test reports, remediation plans, and signed declarations if specified in contract exhibits.
- Deadlines: per contract milestones and acceptance testing schedules.
How-To
- Review the contract accessibility exhibit and acceptance criteria.
- Perform an initial WCAG audit to the required level (for example, WCAG 2.1 AA) using automated and manual testing.
- Deliver a remediation plan for any failures and schedule corrective work before final acceptance.
- Provide test reports, screenshots, and a signer statement of compliance as required by the contract.
- Maintain records of testing and remediation for the project retention period stated in the contract.
FAQ
- Are contractors required to meet WCAG for Las Vegas city projects?
- Yes when the contract or technical exhibits require WCAG standards; the contract documents determine the required success criteria and acceptance testing.
- Who enforces accessibility rules on city contracts?
- Contract compliance is managed primarily by City Purchasing and the relevant project department; building or IT departments may perform technical reviews.
- What happens if my deliverable fails accessibility testing?
- The city may require remediation, withhold payments, or pursue contract remedies until the issues are corrected.
Key Takeaways
- Always review contract exhibits for the specific WCAG level and acceptance tests.
- Document automated and manual test results and keep remediation records.
Help and Support / Resources
- City of Las Vegas Purchasing Division
- Las Vegas Municipal Code on Municode
- Building and Safety Division
- City Information Technology Department