Web Accessibility Rules for Lévis Contractors

Technology and Data Quebec 3 Minutes Read · published May 26, 2026 Flag of Quebec

Lévis, Quebec contractors working on city projects must ensure digital services and project deliverables meet accessibility expectations set by the municipality and applicable provincial guidelines. This article explains practical steps contractors should take when bidding, building, or operating web content for Lévis public projects, how compliance is verified, complaint and inspection pathways, and what to include in contracts and deliverables. It is aimed at bidders, project managers, web developers, and procurement officers who need clear, actionable procedures to reduce legal risk and improve service access for all residents.

Start accessibility planning before contract signature to avoid costly remediations.

Legal context and procurement requirements

Municipal projects in Lévis typically require contractors to follow accessibility standards through contract clauses and specifications. Contractors should expect requirements referencing recognized technical standards such as WCAG 2.1 AA and to provide documentation of testing and remediation. Where a specific municipal bylaw or clause applies it will normally be incorporated into tender documents or the city’s procurement terms.

Penalties & Enforcement

The City of Lévis enforces accessibility obligations for municipal projects primarily through procurement compliance, contract remedies, and administrative follow-up by municipal services. Specific monetary fines for web-accessibility failures are not typically listed in consolidated municipal bylaws; enforcement more commonly relies on contract remedies, orders to remedy, withholding of payment, or termination of contracts. Where provincial accessibility laws or standards apply, penalties and remedies are governed by those instruments as published by the applicable authority.

  • Enforcer: municipal procurement office and by-law or inspection services, acting under contract and municipal authority.
  • Monetary fines: not specified on municipal procurement pages; contract remedies and withholding of payment are common.
  • Escalation: initial cure period, then contractual penalties or termination; specific escalation timelines are not specified on general municipal pages.
  • Non-monetary sanctions: orders to remedy, corrective action plans, suspension of work, contract termination, and court action.
  • Appeals/review: contractual dispute resolution, administrative review where published, and judicial review within statutory civil time limits.
If a municipal tender references a standard, follow that standard and retain testing evidence.

Applications & Forms

No universal, city-wide web accessibility application form is published for contractors; compliance requirements and any required declarations or attestations are usually included in RFP/tender documents or contract appendices, or requested during project close-out. For details consult the tender package for each project or the city’s procurement office (current as of May 2026).

Practical compliance steps for contractors

Contractors should integrate accessibility into the project lifecycle from procurement through maintenance. The following checklist outlines typical contractual and technical actions.

  • Include explicit accessibility clauses and acceptance criteria in bids and contracts.
  • Perform an accessibility audit referencing WCAG 2.1 AA or the standard named in contract documents.
  • Provide test reports, remediation logs, and final certification or attestation at delivery.
  • Train content editors and developers on accessible authoring and testing tools.
  • Schedule periodic accessibility reviews during warranty and maintenance phases.
Retain screenshots and test artifacts tied to ticket numbers to document remediation history.

FAQ

Who enforces web accessibility on Lévis city projects?
Enforcement is carried out through procurement compliance and municipal inspection or contract administration; contractors should follow the contract terms and the standards named therein.
What technical standard should contractors use?
Contracts commonly reference WCAG 2.1 AA or equivalent technical standards; follow the specific standard named in the tender or contract.
Are there prescribed fines for noncompliance?
Specific municipal fines for web accessibility are not typically published; remedies are usually contractual such as withholding payment, orders to remedy, or contract termination.
Keep accessibility evidence with your project records for at least the duration of warranty and audits.

How-To

  1. Review the tender documents and extract any referenced accessibility standards and acceptance criteria.
  2. Plan accessibility work in the project schedule and allocate testing time and budget.
  3. Conduct an automated and manual accessibility audit against the named standard (for example WCAG 2.1 AA).
  4. Log issues, remediate, and re-test; preserve test reports and screenshots as deliverables.
  5. Submit accessibility attestations, remediation logs, and test evidence with the project close-out package.
  6. Train client editors and provide a maintenance checklist for future content updates.
Deliver accessibility attestations and test reports with final invoices to simplify acceptance.

Key Takeaways

  • Include clear accessibility clauses and acceptance criteria in contracts.
  • Document audits and remediation with test reports and screenshots.
  • Plan for ongoing reviews during maintenance, not just at delivery.

Help and Support / Resources

    Categories

    General Governance and Administration Public Safety Public Health and Welfare Land Use and Zoning Housing and Building Standards Transportation Environmental Protection Parks and Public Spaces Business and Consumer Protection Taxation and Finance Labor and Employment Education Civil Rights and Equity Elections and Campaign Finance Events and Special Uses Signs and Advertising Utilities and Infrastructure Technology and Data