Aurora Website Accessibility - WCAG Checklist
Aurora, Colorado public websites and municipal contractors should follow WCAG best practices to ensure access for all residents, including people with disabilities. This guide explains applicable WCAG standards, audit steps, procurement considerations, and how to report accessibility problems to city offices. It summarizes likely enforcement paths and practical remediation steps tailored for Aurora sites operated by city departments, contractors, and local agencies.
What WCAG means for Aurora sites
Follow WCAG 2.1 AA as a working standard: perceivable, operable, understandable, and robust content. Practical priorities are alt text for images, keyboard navigation, clear headings and labels, color contrast, and accessible forms and documents (PDFs, Word). Integrate accessibility into content workflows and procurement so new pages and third-party tools meet standards.
Common accessibility tasks
- Perform a combined automated and manual audit using WCAG 2.1 AA checklists and real-device keyboard testing.
- Inventory site documents and convert or tag PDFs for accessibility.
- Remediate templates, themes, and content management system components for semantic HTML and ARIA where needed.
- Schedule regular re-audits after major releases or content migrations.
- Provide an accessible feedback and complaint mechanism on each site and publish contact info for the city ADA/Accessibility coordinator.
Design, procurement, and contracts
Include specific WCAG conformance requirements in RFPs and contracts and require deliverables such as an accessibility conformance report (ACR) and remediation timelines. Require vendors to provide test artifacts, browser/device compatibility statements, and ongoing support for accessibility updates.
Penalties & Enforcement
Aurora does not publish a separate municipal web-accessibility fine schedule on the city pages commonly used for policy and guidance; monetary penalties for website accessibility issues are not specified on the cited city pages. Federal enforcement under the ADA or complaints to the U.S. Department of Justice or the U.S. Department of Education Office for Civil Rights may apply to public entities in practice.
- Monetary fines: not specified on the cited page.
- Escalation: first, corrective notice or demand for remediation; repeating or continuing failures may prompt additional administrative or legal action - not specified on the cited page.
- Non-monetary sanctions: injunctive relief, required remediation, or court orders may be sought through federal or state processes; city-specific administrative suspensions or penalties for contractor noncompliance should be enforced via contract terms.
- Enforcer and contact: the City of Aurora's ADA/Accessibility contact or the department responsible for the specific website typically handles complaints; see Help and Support / Resources below for official contacts.
- Appeals and review: appeals and judicial review generally follow standard administrative or civil procedures; time limits are not specified on the cited city pages and will depend on the enforcement route taken.
Applications & Forms
No standardized municipal form for website accessibility complaints is published on the general city guidance pages reviewed; file a complaint using the department contact or the city ADA/accessibility contact listed in Help and Support / Resources. For contractor compliance, require accessibility deliverables and ACRs as part of contract closeout documentation.
Practical action steps
- Run an initial automated scan and a manual keyboard/visual test within 30 days for high-traffic pages.
- Create a prioritized remediation plan: critical (navigation, forms), major (documents, media), minor (cosmetic ARIA).
- Budget for remediation and ongoing testing in annual IT or communications budgets.
- Publish an accessibility statement and feedback contact on each site with expected response times.
FAQ
- Does Aurora require WCAG 2.1 AA for municipal websites?
- Aurora sites follow accessibility best practices and the city recommends WCAG standards; specific municipal code mandates or exact levels are not published on the general guidance pages cited below.
- How do I report an inaccessible city web page?
- Use the department contact or the city ADA/accessibility contact listed in Help and Support / Resources to report accessibility issues and request remediation.
- Are there fines for inaccessible web content?
- Monetary fines specific to Aurora web accessibility are not specified on the cited city pages; federal ADA enforcement or contract remedies may apply.
How-To
- Inventory public-facing pages and documents to identify high-priority content.
- Run automated WCAG scans and supplement with manual keyboard and screen reader tests.
- Prioritize fixes: navigation and form accessibility first, then documents and media.
- Implement fixes in templates and CMS components to prevent regressions.
- Publish an accessibility statement, remediation timeline, and a feedback channel on the site.
- Schedule periodic audits and include accessibility requirements in all future contracts and RFPs.
Key Takeaways
- Design for accessibility from procurement through deployment to reduce long-term costs.
- Use combined automated and manual testing for reliable results.
- Provide a clear, public feedback route and respond promptly to reported issues.
Help and Support / Resources
- City of Aurora - Accessibility and ADA information
- Aurora Municipal Code (Municode)
- City of Aurora - Human Resources / Equal Opportunity
- City of Aurora - Community Development / Building Services