Albuquerque WCAG Compliance Guide for City Websites

Technology and Data New Mexico 4 Minutes Read ยท published February 08, 2026 Flag of New Mexico

This guide explains practical steps for achieving WCAG accessibility on municipal websites in Albuquerque, New Mexico. It summarizes who enforces accessibility, how to audit and remediate city web content, complaint and appeal routes, and where to find official forms and contacts so city teams and contractors can act confidently.

Getting started: audit, policy, and scope

Begin with a formal WCAG conformance goal (WCAG 2.1 AA or higher), an accessibility statement on the site, and a written remediation plan that assigns tasks and deadlines to departments. Include procurement clauses that require contractors and vendors to deliver accessible code and content. For local legal context, consult the City of Albuquerque municipal code and website accessibility resources [1][2].

Start audits on public-facing pages and high-traffic services first.

Technical steps

  • Run automated scans to find common failures (contrast, alt text, labels).
  • Perform manual testing with keyboard-only navigation and screen reader tools.
  • Publish an accessibility statement with conformance level, known exceptions, and contact details.
  • Set remediation deadlines and track fixes in a public roadmap.
  • Budget for ongoing monitoring, training, and vendor compliance checks.

Procurement and governance

Embed WCAG requirements into RFPs and contracts for vendors and require deliverable acceptance testing. Assign a city accessibility coordinator or team to approve vendor test reports and to sign off on content before publication. Use the city IT accessibility page for local policy references [2].

Penalties & Enforcement

Enforcement for accessibility issues affecting city websites in Albuquerque typically proceeds through administrative complaint channels, corrective orders, and escalation to litigation where federal ADA claims apply. Specific monetary fines for web inaccessibility are not commonly listed on city pages; where amounts or civil penalties are stated they must be confirmed on the cited municipal or department page. For complaint filing and departmental contact, see the Human Rights/ADA office link [3].

  • Fine amounts: not specified on the cited page.
  • Escalation: first response, remediation order, repeat or continuing noncompliance may lead to stronger administrative or judicial remedies; specific ranges are not specified on the cited page.
  • Non-monetary sanctions: corrective orders, mandated remediation timelines, injunctive court orders, and possible court-ordered oversight.
  • Enforcer: City Human Rights/ADA office and the City Attorney for enforcement or legal action; complaints and inspection pathways are published by the city [3].
  • Appeals/review: administrative review or judicial appeal; time limits for appeals are not specified on the cited page and should be confirmed with the enforcing department.
  • Defences/discretion: reasonable accommodation, documented good-faith remediation efforts, or approved variances may be considered; specific statutory defenses are not specified on the cited page.
If a specific penalty amount is needed for legal planning, request the enforcing department's guidance in writing.

Applications & Forms

The city does not publish a universal "web accessibility fine" form; complaints are typically filed through the Human Rights/ADA complaint process and IT acceptance testing uses vendor reports and accessibility statements for documentation. Check the Human Rights/ADA complaint submission and IT guidance pages for any published forms or templates [2][3].

Action steps for city teams

  • Publish or update the website accessibility statement and remediation roadmap.
  • Commission a WCAG 2.1 AA audit and prioritize fixes for core public services.
  • Integrate accessibility checks into the CMS workflow and procurement documents.
  • Designate an accessibility coordinator and publish contact information for complaints and questions.

FAQ

Who enforces website accessibility for city sites in Albuquerque?
The City Human Rights/ADA office handles local administrative complaints and the City Attorney enforces legal remedies; federal ADA enforcement may also apply. See the city complaint and IT pages for contacts [2][3].
Does Albuquerque require WCAG 2.1 AA specifically?
The city encourages WCAG conformance as a best practice; specific adoption of WCAG 2.1 AA should be confirmed in procurement guidance or policy documents on the city IT pages [2].
How do I file an accessibility complaint about a city webpage?
Submit a complaint through the Human Rights/ADA complaint process on the city website; the complaint page lists submission methods and contact details [3].

How-To

  1. Define your conformance target (for example, WCAG 2.1 AA) and publish it in an accessibility statement.
  2. Run automated scans across public-facing pages and export a prioritized defect list.
  3. Perform manual testing for keyboard navigation and screen reader compatibility on critical flows.
  4. Create a remediation roadmap with assigned owners, deadlines, and verification steps.
  5. Update procurement documents to require accessibility deliverables and acceptance tests from vendors.
  6. Publish completed fixes, update the accessibility statement, and invite feedback via the published complaint contact.

Key Takeaways

  • Start with an audited baseline and a public remediation roadmap.
  • Integrate WCAG requirements into contracts and CMS workflows.
  • Publish a clear contact for complaints and designate an accessibility coordinator.

Help and Support / Resources


  1. [1] City of Albuquerque municipal code and ordinances
  2. [2] City of Albuquerque IT - Web accessibility guidance
  3. [3] City of Albuquerque Human Rights - ADA and accessibility complaints