Langley BC Website Accessibility Bylaw: WCAG Steps
Langley, British Columbia public staff are responsible for ensuring municipal websites meet WCAG accessibility standards and provide equitable access to information and services. This guide summarizes practical, office-level steps for communications, web development, and records staff to plan, test, remediate, and monitor web content against WCAG criteria, and explains reporting, enforcement channels, and appeal paths relevant to Langley municipal operations.
Getting started: scope and roles
Define the scope (site pages, PDF documents, transactional services) and assign roles: communications for content, IT for technical remediation, legal for policy alignment, and a designated accessibility coordinator. Prioritize high-traffic and transactional pages first and keep an inventory of third-party tools and vendor obligations.
Core WCAG compliance steps
- Create an accessibility policy and published statement that references WCAG level and target timelines.
- Conduct an automated audit (axe, WAVE, or equivalent) and a prioritized manual review for keyboard and screen-reader support.
- Remediate templates and components first (navigation, forms, headings) before page-level fixes.
- Adopt a remediation schedule with regular sprints and release gating to prevent regressions.
- Include accessibility acceptance criteria in vendor contracts and new procurements.
- Set up ongoing monitoring and a public feedback/reporting channel for accessibility issues.
Penalties & Enforcement
Municipal-level fines or specific bylaw penalties for website accessibility are not specified on the official Langley municipal pages linked in Resources; enforcement commonly involves provincial bodies or adjudication through human rights processes rather than a municipal ticketing fine for web content. For Langley staff, enforcement responsibility and internal corrective measures normally rest with the communications and IT departments and with provincial oversight where applicable (see Resources).
Escalation and sanctions: the cited official resources do not list municipal monetary ranges or first/repeat offence schedules for website accessibility; escalation typically follows complaint investigation, remedial orders, and possible referral to provincial authorities or tribunals where statutory routes exist.
Non-monetary sanctions and orders that may apply include formal compliance orders, requirements to publish accessibility plans, or administrative directions to remediate content. Enforcement channels for accessibility concerns affecting residents may include provincial accessibility offices or the BC Human Rights Tribunal depending on the claim type and instrument cited.
Enforcer and complaint pathways: internal enforcement is handled by the City of Langley departments responsible for web publishing and bylaw or corporate administration for policy. Residents should report accessibility problems using the city contact or general complaint channels detailed in Resources; staff should route complaints to the accessibility coordinator and IT service desk for tracking and remediation.
Appeals and review: appeal or review routes and statutory time limits for decisions are not specified on the municipal pages cited here; provincial complaint or tribunal processes set their own deadlines and appeal procedures, so staff should document timelines and preserve evidence when responding to complaints.
Applications & Forms
There is no published, dedicated municipal "accessibility compliance application" or standardized form for demonstrating WCAG compliance on the City of Langley site; complaints and accessibility feedback are handled via the general contact or complaint submission processes listed in Resources.
Action steps for Langley staff
- Publish a short accessibility statement and remediation timeline on the municipal website.
- Run an initial automated scan and log top 20 issues for immediate fixes.
- Update templates and CMS components to include semantic headings and ARIA where needed.
- Budget for vendor audits and manual testing by assistive-technology users.
- Set a published point of contact for accessibility feedback and weekly triage for incoming reports.
FAQ
- What WCAG level should Langley municipal websites target?
- Most public sector guidance recommends WCAG 2.1 AA as a practical standard; confirm any specific municipal policy with the accessibility coordinator or the provincial guidance linked in Resources.
- How do residents report inaccessible content?
- Residents should use the City of Langley contact or complaints channel listed in Resources to report inaccessible pages or documents; staff must log the report and begin triage.
- Are there exemptions for legacy content?
- Exemptions or staged timelines may be documented in policy but are not set out on the municipal pages cited here; use the remediation schedule to prioritize high-impact content.
- Who enforces accessibility complaints?
- Enforcement may involve municipal administration for internal compliance and provincial bodies or tribunals for statutory complaints; see Resources for provincial contacts.
How-To
- Assemble a cross-department team and appoint an accessibility coordinator.
- Create an inventory of pages, documents, and third-party tools; tag by priority.
- Run automated scans, then schedule manual keyboard and screen-reader tests on prioritized items.
- Remediate templates/components first, then pages, and validate fixes with manual testing.
- Publish an accessibility statement, reporting channel, and remediation timeline.
Key Takeaways
- Make accessibility part of procurement and release gates.
- Prioritize templates and transactional pages for fastest public benefit.
Help and Support / Resources
- City of Langley - Accessibility and contact pages
- Township of Langley - accessibility and service pages
- Accessible British Columbia Act and provincial statutes
- BC Human Rights Tribunal - complaint processes
