Aurora Website Accessibility: WCAG & Bylaw Checklist
This guide explains website accessibility obligations and WCAG technical rules as they apply to Aurora, Illinois public websites and municipal contractors. It summarizes applicable standards, enforcement pathways, practical steps to audit and remediate sites, and how to accept and respond to accessibility complaints for city-run or city-funded sites. The goal is to help Aurora departments, vendors, and local nonprofits meet recognized standards and reduce legal risk while improving access for people with disabilities.
Legal framework and standards
Web accessibility obligations for public entities in the United States rely on federal disability law (Title II of the Americans with Disabilities Act) and recognized technical standards such as WCAG 2.1; municipal codes sometimes reference or require compliance but do not always set technical criteria themselves. For Aurora, the consolidated municipal code does not specify a web-specific accessibility standard on its code pages [1]. The technical rules widely used by public agencies are the Web Content Accessibility Guidelines (WCAG) maintained by W3C, commonly applied at level AA for government sites [2]. Federal enforcement and technical guidance for websites is available from the U.S. Department of Justice and related federal guidance on web content; municipalities should align policies with those federal resources when a local ordinance is absent [3].
Penalties & Enforcement
Where a local ordinance or municipal code explicitly creates penalties for inaccessibility, that provision controls; for Aurora there is no municipal code section on web-accessibility penalties found on the city code pages, so specific local fines or schedules are not specified on the cited page [1]. Federal enforcement under the ADA can result in court actions, injunctive relief, and settlement terms; monetary amounts and civil penalties depend on the enforcement action and are not stated as fixed sums on the DOJ technical guidance page [3]. State agencies may also investigate discrimination claims under state law when disability access is at issue; specific Illinois administrative penalties for web inaccessibility are not listed on the municipal code page cited for Aurora [1].
- Fine amounts: not specified on the cited Aurora municipal code page; federal remedies vary by case and are described in DOJ guidance [3].
- Escalation: first, remedial requests and notices; repeat or continuing noncompliance can lead to litigation or court-ordered remedies, amounts or daily penalties are not fixed on the cited municipal page.
- Non-monetary sanctions: injunctive relief, mandatory remediation plans, monitoring and reporting, and court orders are typical under federal enforcement.
- Enforcer and complaint pathway: for federal claims, U.S. Department of Justice; locally, complaints about Aurora services or sites should be directed to the City of Aurora administrative contact or the department responsible for the affected service (see Help and Support / Resources below).
- Appeals and review: appeals depend on the enforcing agency and forum; time limits for bringing an administrative claim or lawsuit are not set on the Aurora code page and vary by statute of limitations for state or federal claims (not specified on the cited page).
Applications & Forms
There is no specific Aurora municipal web-accessibility permit or form found on the cited municipal code pages; when filing a complaint or request for accommodation, use the City's published contact or ADA accommodation process if available, or submit written documentation to the department that operates the service [1].
Practical compliance checklist
Adopt a measurable project plan that maps site content, tests for WCAG 2.1 AA conformance, and assigns remediation tasks. Include procurement language requiring vendors to meet accessibility standards and require deliverable testing evidence.
- Conduct an accessibility audit against WCAG 2.1 AA success criteria and generate a prioritized issue list [2].
- Set deadlines for remediation phases and public timelines for fixes.
- Update procurement and contractor agreements to require accessibility testing results and an accessibility conformance report.
- Remediate critical interactive features first (forms, navigation, PDF documents) and retest after fixes.
- Provide an accessibility statement and a clear contact for reporting accessibility barriers.
FAQ
- Do Aurora municipal websites have to follow WCAG?
- While WCAG is the accepted technical standard, Aurora's municipal code pages do not set a specific web standard; agencies typically adopt WCAG 2.1 AA as best practice and follow federal ADA guidance [2].
- Who enforces web accessibility claims for Aurora sites?
- Federal enforcement actions under the ADA are handled by the U.S. Department of Justice; local complaints should be submitted to the City department responsible for the service or to the City's official contact channels [3].
- How long will remediation take after a complaint?
- Timeframes vary by issue complexity and resource allocation; specific municipal deadlines are not specified on the Aurora code pages and should be agreed in remediation plans with the enforcing body or claimant.
How-To
- Inventory site pages, applications, and document formats that provide public services.
- Run automated and manual WCAG 2.1 AA tests, document failures, and estimate effort to fix each item.
- Create a remediation plan with prioritized fixes, responsible owners, and target dates.
- Update procurement templates to require accessibility acceptance testing from vendors.
- Publish an accessibility statement and a clear complaint/contact process for users.
Key Takeaways
- Adopt WCAG 2.1 AA for technical conformance and document compliance efforts.
- Include accessibility requirements in contracts and procurement for city vendors.
- Provide a clear reporting channel and respond promptly to accommodation requests.