Houston WCAG Compliance Checklist for City Sites
Houston, Texas municipal web managers must follow clear steps to make city websites accessible under WCAG standards and applicable municipal policies. This checklist explains roles, technical and content tasks, reporting channels and compliance workflow so city departments can reduce legal and operational risk while improving access for residents with disabilities.
Overview
This guide covers practical WCAG conformance steps for Houston city sites, referencing the City of Houston accessibility resources and the municipal code where relevant. It is intended for web teams, content editors, and compliance officers who maintain official city domains. Follow the sequence: audit, prioritize fixes, adopt templates, train staff, and set monitoring and complaint routes to stay compliant with WCAG 2.1+ practices and local policy.
Checklist: implementation steps
- Conduct a WCAG audit (automated + manual) and produce a prioritized remediation plan.
- Document baseline conformance levels and maintain remediation logs and test records.
- Fix common technical issues: semantic HTML, ARIA roles, keyboard navigation, and color contrast.
- Adopt accessible templates and component libraries for CMS-powered pages.
- Provide staff training and publish an accessibility statement with contact and feedback options. City of Houston accessibility resources[1]
- Establish a complaint intake and tracking process tied to an official office or 311 intake.
Penalties & Enforcement
The municipal code and city accessibility pages do not list detailed monetary fines specific to website WCAG noncompliance; enforcement usually follows administrative or corrective routes and may reference broader non-discrimination obligations. For specific ordinance language or enforcement authority see the municipal code cited below. Municipal code and ordinances[2]
- Fines: not specified on the cited page.
- Escalation: first, repeat or continuing offence ranges not specified on the cited page.
- Non-monetary sanctions: corrective orders, injunctive court actions, or administrative compliance directives may be used; specifics not specified on the cited page.
- Enforcer: typically the department responsible for the website or a designated city compliance office; complaints often routed via City 311 or the department contact listed on the accessibility page.
- Appeals/review: appeal routes and time limits are not specified on the cited page; follow the department or municipal code appeals procedure where applicable.
- Defences/discretion: reasonable accommodation processes, good-faith remediation plans, or granted variances may apply depending on the department policy; specifics not specified on the cited page.
Applications & Forms
No single WCAG enforcement form is published on the cited pages; web teams should use department complaint forms or City 311 for reporting accessibility issues. If a formal compliance application is required, the municipal code or department web page will list it on the official site.
Operational actions
- Set quarterly re-testing schedules and include accessibility in sprint planning.
- Publish an accessibility statement with review date and remediation timelines.
- Budget for remediation, testing and procurement of accessible components.
- Designate a contact for intake and provide clear reporting instructions on each site.
FAQ
- How do I report an inaccessible city webpage?
- Use the City of Houston accessibility contact or submit a 311 request; include the page URL, browser, device and a description of the issue.
- What WCAG level should city sites meet?
- City guidance commonly targets WCAG 2.1 AA as a practical baseline unless a higher standard is required by policy.
- Who enforces web accessibility for Houston sites?
- Enforcement is handled by the owning department and city compliance channels; legal action may involve municipal or state remedies depending on the claim.
How-To
- Run an automated accessibility scan to identify high-level issues.
- Perform manual testing for keyboard navigation, screen reader behavior and form labels.
- Remediate critical failures first: headings, labels, alt text, and color contrast.
- Publish an accessibility statement and provide a simple reporting form or 311 instructions.
- Schedule regular audits and document fixes and outstanding issues.
Key Takeaways
- Start with an audit, then fix critical user-impact issues first.
- Maintain an accessibility statement and clear reporting path.
- Keep remediation logs and schedule recurrent testing.
Help and Support / Resources
- City of Houston Accessibility
- Houston Municipal Code (Municode)
- City 311 - Service Requests
- Planning & Development Department