Las Vegas Vendor Website Accessibility Requirements
Las Vegas, Nevada requires vendors who contract with the city to ensure digital services and public-facing web content are accessible to people with disabilities. This guide summarizes what vendors should expect in procurement documents, what technical standards are commonly referenced, how to report accessibility problems, and practical steps vendors can take to meet obligations when doing business with the City of Las Vegas. It highlights enforcement pathways, typical corrective actions, and where to find official contact points for complaints and assistance.
Scope & Applicable Standards
Vendors supplying web design, hosting, online portals, or digital content to the City of Las Vegas should expect contract language requiring compliance with federal accessibility law (Americans with Disabilities Act) and city accessibility policies. The city website provides an accessibility statement with contact and complaint information for online services [1].
- Commonly referenced technical standards: WCAG 2.0 or 2.1 at AA level (as specified in procurement documents or guidance).
- Federal requirements such as the ADA and Section 508 for federal funds may inform city expectations.
- Vendors should review the City of Las Vegas accessibility contacts and procurement terms before bidding.
Penalties & Enforcement
The City of Las Vegas addresses accessibility primarily through contract requirements, compliance notices, and its published accessibility statement. Specific monetary fines or formulaic penalties for vendor website noncompliance are not specified on the cited page [1]. Where civil or statutory enforcement applies, federal or state remedies under the ADA may also be relevant.
- Fine amounts: not specified on the cited page.
- Escalation: first, repeat, and continuing-offence treatment is not specified on the cited page.
- Non-monetary sanctions: likely remedies include contract corrective actions, orders to remediate, or suspension/termination of contracts; specific lists are not specified on the cited page.
- Enforcer and complaint pathway: the City of Las Vegas accessibility contact is the official starting point for complaints and reports; procurement-related enforcement may involve the Purchasing/Procurement division and legal counsel (see Help and Support / Resources below for official contacts).
- Appeals and review: specific administrative appeal time limits are not specified on the cited page; vendors should preserve contract correspondence and follow any appeal steps set out in the contract or procurement documents.
- Defences and discretion: common defences include demonstrating a good-faith remediation plan, reliance on official guidance, or the existence of an approved variance or accommodation; specific permissive variances are not specified on the cited page.
Applications & Forms
The city does not publish a standard "accessibility violation" vendor fine form on the cited page; procurement disputes and contract default procedures are typically handled through contract notices or purchasing division processes and any applicable claim forms in contract documents [1]. Vendors should check procurement RFQs/RFPs for required submittals and vendor registration requirements.
Practical Compliance Steps for Vendors
- Conduct an initial accessibility audit against WCAG 2.1 AA (automated plus manual testing).
- Document known issues, remediation plans, and target dates.
- Include accessibility clauses in subcontractor agreements and require deliverable checklists.
- Budget for remediation and ongoing accessibility testing in proposals.
- Use the city accessibility contact to clarify expectations before bid submission [1].
FAQ
- Do I need to make third-party platforms accessible when contracting with Las Vegas?
- Yes. Vendors must ensure any platform or third-party service used to deliver public-facing content meets the accessibility requirements set out in the contract or procurement documents.
- Which technical standard does the city require?
- The city references federal accessibility law and its website accessibility statement; specific technical standard references in procurement documents are typically WCAG 2.0 or 2.1 AA unless the contract states otherwise.
- How do I report an accessibility problem with a city website?
- Use the City of Las Vegas accessibility contact listed on the city accessibility statement to report issues and request accommodations [1].
- What if my company needs more time to remediate?
- Propose a written remediation schedule to the contracting officer and retain evidence of progress; time extensions are decided case by case and may be reflected in contract amendments.
How-To
- Review the procurement documents and city accessibility statement to identify explicit accessibility requirements.
- Run an accessibility audit (automated tools plus manual checks with assistive technologies).
- Create a remediation plan with prioritized fixes and timelines; include estimated costs.
- Submit documentation and, if needed, a remediation schedule to the city contracting officer or accessibility contact.
- After remediation, perform verification testing and provide a compliance report to the city.
Key Takeaways
- Vendors must plan for accessibility early and document remediation.
- Use the City of Las Vegas accessibility contact for reports and clarifications [1].
Help and Support / Resources
- City of Las Vegas - Accessibility Statement and Contact
- City of Las Vegas - Procurement / Purchasing
- City of Las Vegas - City Clerk and Municipal Code
- U.S. Department of Justice - ADA Web Accessibility Guidance