Austin WCAG Checklist for City Contractors

Technology and Data Texas 3 Minutes Read · published February 06, 2026 Flag of Texas

Austin contractors who build or maintain websites for the City of Austin must design for accessibility so people with disabilities can access information and services. This checklist explains expected WCAG practices, procurement considerations, enforcement pathways, and practical steps contractors should follow when working on Austin municipal websites.

Checklist Overview

  • Perform an initial accessibility audit against WCAG 2.1 AA standards and document findings.
  • Provide an accessibility conformance report (ACR) or VPAT showing current conformance and remediation plan.
  • Remediate issues by priority: critical barriers, then major functional gaps, then polishing and documentation.
  • Include accessibility testing in QA cycles and schedule periodic re-testing after deployments.
  • Offer training for client content editors on producing accessible content and maintaining templates.
  • Include contractual language requiring ongoing conformance, reporting intervals, and remediation deadlines.
Document an accessibility owner and a remediation timeline before work begins.

Penalties & Enforcement

The City of Austin enforces municipal requirements through its code and procurement terms; specific monetary fines or statutory penalties for web accessibility are not detailed on the cited city pages. City of Austin Code of Ordinances[1] and departmental procurement pages discuss contract compliance and remedies but do not list explicit per-violation fine tables for website inaccessibility.

  • Fine amounts: not specified on the cited page.
  • Escalation: first, repeat, and continuing offence ranges are not specified on the cited page.
  • Non-monetary sanctions: contract remedies, withholding payments, termination for default, and required remediation are referenced in procurement rules or contract terms; exact remedies vary by contract and are not itemized on the cited page.
  • Enforcer: the City department that awarded the contract and the City Purchasing/Finance office oversee compliance and may process complaints; see the City procurement pages for contact points.Communications & Public Information[2]
  • Appeal/review: appeal routes depend on contract terms and procurement protest procedures; time limits for protests or appeals are set in procurement rules or the specific contract and are not uniformly specified on the cited pages.
  • Defences/discretion: requests for variances or corrective timelines may be considered per contract terms or departmental discretion; exact criteria are not specified on the cited pages.
If a contract names remediation milestones, adhere to them to avoid contractual remedies.

Applications & Forms

  • The City does not publish a single universal web-accessibility “penalty” form; contractors should follow contract-specific reporting forms and procurement instructions, or contact the awarding department for required submissions.

Implementation Steps for Contractors

  • Run automated scans (e.g., axe, WAVE) and manual tests (keyboard navigation, screen reader walkthroughs) and compile a prioritized issue list.
  • Fix structural issues first (semantic HTML, ARIA roles, headings), then media alternatives (captions, transcripts) and color/contrast.
  • Deliver an Accessibility Conformance Report (ACR) or VPAT with remediation milestones and acceptance criteria.
  • Schedule post-deployment audits at regular intervals and after major updates.
Include acceptance tests for accessibility in statements of work to make conformance verifiable.

Common Violations

  • Poor keyboard focus order and inaccessible custom controls.
  • Missing or inadequate alt text for images and non-text content.
  • Insufficient color contrast and reliance on color alone to convey information.
  • Uncaptioned video or inaccessible multimedia players.

FAQ

Do city contracts require WCAG conformance?
The City expects contractors to follow recognized accessibility standards; contract language defines the required level and verification process, and may reference WCAG conformance or equivalent criteria.
How do I report an inaccessible city website?
Report accessibility barriers to the department that hosts the service or to the City communications/accessibility contact listed on the department page; contractors should also notify the contract manager immediately.
What documentation should contractors submit?
Submit an accessibility conformance report (ACR or VPAT), remediation plans with dates, and evidence of testing; specific submission details are in the contract or procurement instructions.

How-To

  1. Inventory all public-facing pages and interactive components to scope the engagement.
  2. Run an accessibility audit (automated and manual) and produce a prioritized issue list.
  3. Create a remediation plan with milestones, owners, and acceptance tests.
  4. Remediate issues, document code changes, and update CMS templates to prevent regressions.
  5. Deliver an ACR/VPAT and schedule a post-deployment audit to confirm fixes.

Key Takeaways

  • Build accessibility into contracts and statements of work to avoid disputes.
  • Provide clear evidence: audits, VPAT/ACR, and remediation timelines.

Help and Support / Resources

  1. [1] City of Austin Code of Ordinances
  2. [2] Communications & Public Information — City of Austin

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