Jacksonville Vendor WCAG Requirements for City Contracts
Introduction
Jacksonville, Florida requires vendors working on city contracts to address accessibility for people with disabilities as part of procurement and digital services. This guide summarizes how WCAG expectations are applied to vendor deliverables, where the city directs vendors for policy and technical guidance, and practical steps for compliance and dispute resolution under Jacksonville procurement procedures.
Scope and Applicable Standards
City contracts commonly require compliance with web and digital accessibility standards such as the Web Content Accessibility Guidelines (WCAG). The specific contract language, solicitation documents, and technical requirements determine whether WCAG 2.0, 2.1, or a particular conformance level (A, AA, AAA) applies. Vendors must review solicitation attachments and the City of Jacksonville procurement requirements before bidding.[1]
Vendor Responsibilities
- Review contract documents, scope of work, and technical appendices for explicit WCAG version and level.
- Provide an accessibility conformance report or VPAT where requested by the solicitation.
- Implement remediation plans for any nonconforming content found during testing or acceptance.
- Allow city inspections, testing, or third-party audits as required by contract terms.
- Include estimates for accessibility testing and remediation in bids and invoices where required.
Penalties & Enforcement
Enforcement of accessibility obligations for vendors under city contracts is primarily administered through the City of Jacksonville Procurement Division and contract administration teams. Remedies and penalties depend on the contract terms, procurement rules, and any applicable ordinances or administrative procedures referenced in the solicitation.[1]
- Monetary fines: not specified on the cited page.
- Escalation for repeat or continuing breaches: not specified on the cited page.
- Non-monetary sanctions: contract termination, withholding payment, required remediation at vendor expense, and debarment are possible remedies referenced in procurement practice; specific procedures are set out in solicitation terms or procurement rules.[1]
- Enforcer: City of Jacksonville Procurement Division and the contract manager named in the solicitation.
- Inspection and complaint pathway: vendors and members of the public may report accessibility issues to procurement or the city department that issued the contract; contact details are on the procurement pages and departmental accessibility pages.[1]
- Appeals and protests: bid protest and contract dispute procedures are governed by procurement rules; specific time limits for filing protests are not specified on the cited procurement page.
- Defences and discretion: reasonable excuse, cure periods, corrective action plans, or approved variances may be available if expressly allowed by the contract; consult procurement for exceptions.
Applications & Forms
The City uses vendor registration, solicitation forms, and procurement documents to record accessibility commitments. Where a solicitation requires a VPAT or accessibility plan, those documents will be named in the solicitation attachments. If no specific form is requested in a solicitation, no separate city form is required for WCAG compliance according to the procurement page.[1]
Testing and Verification
Vendors should combine automated scans, manual testing, and user testing with people who have disabilities. The city may require proof of testing or independent verification depending on the contract. For technical guidance and testing tools referenced by city IT policies, consult the City of Jacksonville information technology accessibility guidance.[2]
Action Steps for Vendors
- Review the solicitation and attachments for WCAG version and level before preparing a bid.
- Prepare a VPAT or accessibility conformance report if requested in the solicitation.
- Plan for testing, remediation, and post-deployment monitoring in the project timeline.
- Contact the Procurement Division or the issuing department with questions during the solicitation period.
FAQ
- Do Jacksonville contracts always require WCAG 2.1 AA?
- Not always; the required WCAG version and level are set by the individual solicitation and contract attachments. The procurement pages do not list a uniform mandatory level for all city contracts.[1]
- Who enforces accessibility clauses in city contracts?
- The City of Jacksonville Procurement Division and the contract manager enforce contract terms; technical departments and the city IT office may verify compliance.[1]
- What happens if a vendor fails accessibility checks after deployment?
- Remedies are determined by the contract and procurement rules and may include remediation at vendor expense, withholding payment, or contract termination; specific fines and timelines are not specified on the cited procurement page.[1]
How-To
- Review the solicitation documents and identify any accessibility requirements.
- Prepare a VPAT or accessibility conformance report if requested.
- Perform automated and manual accessibility testing, and document results.
- Deliver remediation for any failures before acceptance or as contracted.
- Retain records of testing and remediation to support inspections or audits.
- If disputed, follow the procurement protest process and contact procurement for guidance.
Key Takeaways
- Check each solicitation for explicit WCAG requirements.
- Provide documented testing and remediation plans when bidding.
- Contact Procurement early to clarify requirements and avoid disputes.
Help and Support / Resources
- City of Jacksonville Procurement Division
- City of Jacksonville Information Technology Department
- City of Jacksonville Planning and Development