Winnipeg WCAG Contract Clauses for City Projects
This guide explains how contract clauses that require WCAG accessibility are applied to municipal work in Winnipeg, Manitoba. It summarizes where accessibility requirements typically appear in procurement and project contracts, who enforces them, and practical steps consultants, vendors, and city staff should follow to meet WCAG standards on city-funded or city-managed projects. The article focuses on contractual obligations, enforcement pathways, and how to document compliance for bidding, delivery, and post-completion support.
Where WCAG Clauses Appear in Winnipeg Contracts
WCAG requirements are usually included in procurement documents, tender specifications, and professional services agreements for digital deliverables, public websites, kiosks, and embedded digital systems. Clauses can require WCAG 2.0 or 2.1 conformance at a specific level (commonly AA), require accessible documentation and testing, and assign responsibilities for remediation and maintenance. Contract language often references the Citys accessibility guidance and procurement standards; see the City of Winnipeg Accessibility Office for municipal guidance City of Winnipeg Accessibility Office[1].
- Typical clause elements: statement of required WCAG level, acceptance testing, and maintenance obligations.
- Deliverables often include accessibility statements, test reports, and defect remediation plans.
- Construction and systems contracts may require accessible user interfaces for public-facing controls and displays.
Penalties & Enforcement
Municipal enforcement of WCAG contract clauses is primarily contractual: remedies for breach are those specified in the procurement contract, such as withholding payment, repair/replace obligations, or termination. Monetary fines for accessibility breaches are not generally listed on the municipal accessibility guidance and are not specified on the cited page.[1]
- Fine amounts: not specified on the cited page.
- Escalation: first notice, remediation period, and potential contract remedies; specific ranges not specified on the cited page.
- Non-monetary sanctions: repair orders, corrective work, withholding of payments, contract termination, and claims for damages may apply.
- Enforcer: Materials Management/Procurement and the City Accessibility Office handle contract compliance and related complaints.
- Inspection & complaints: vendors and the public can raise accessibility issues through procurement contacts or the City Accessibility Office.
- Appeals & reviews: contractual dispute resolution provisions apply; statutory appeal routes depend on the instrument and are not specified on the cited page.
- Defences/discretion: reasonable excuse or approved variances may be possible if explicitly written into the contract or approved by the City.
Applications & Forms
No single public form is published for declaring WCAG compliance in municipal contracts; compliance is generally demonstrated through deliverables, test reports, and certificates included with bids or final submissions, or as required by the specific tender documents. The City guidance does not publish a universal form for WCAG certification on contracts.
Contract Drafting & Procurement Best Practices
Include clear, testable acceptance criteria and assign remediation obligations and timelines. Require third-party or independent accessibility testing where appropriate, and spell out maintenance responsibilities for hosted services and updates. Make accessibility a scored criterion in evaluations to incentivize compliance.
- Set remediation timelines and acceptance testing windows in the contract.
- Require submission of accessibility test reports and remediation plans as deliverables.
- Use templates or clauses that specify WCAG version and conformance level (for example, WCAG 2.1 AA).
- Consider staged acceptance for large projects: milestones tested for accessibility before final acceptance.
Action Steps for Vendors and Project Teams
- At bid stage: include accessibility statements, evidence of prior work, and a remediation plan.
- During delivery: run automated and manual accessibility tests against the contracts required WCAG level.
- If non-compliant: notify the contracting officer, submit a remediation plan, and cooperate with acceptance testing.
- If disputed: follow the contracts dispute resolution process and preserve records of testing and remediation efforts.
FAQ
- Which WCAG level does Winnipeg require for city projects?
- Winnipeg procurement documents commonly require WCAG 2.x at Level AA; check the specific tender or contract for the stated version and level.
- Who enforces accessibility clauses in contracts?
- Enforcement is handled through the contract holder and City procurement processes, with input from the City Accessibility Office and Materials Management.
- What if a third-party platform cannot meet WCAG?
- Contractors should document limitations, propose mitigation or alternative accessible solutions, and seek written approval or an agreed remediation plan from the City contracting authority.
How-To
- Review the tender documents for the exact WCAG version and level required.
- Prepare accessibility deliverables: statements, test reports, and remediation plans.
- Perform automated and manual accessibility testing and fix defects before submission.
- Submit required documentation with invoices or final deliverables and respond promptly to City remediation requests.
- If disputes arise, follow contractual dispute resolution and keep detailed records of testing and correspondence.
Key Takeaways
- Make WCAG requirements explicit, testable, and tied to acceptance.
- Document compliance with test reports and require remediation plans in contracts.
Help and Support / Resources
- City of Winnipeg Accessibility Office
- City of Winnipeg Materials Management (Procurement)
- Manitoba Accessibility - Government of Manitoba