Is Provo's Website Ready for the ADA Title II Deadline?

Compliance deadlineApril 26, 2027about 7 months away
Population (2024 est.)115,479≥ 50,000 — first-wave tier
ClassificationMunicipal government (general purpose)Utah
Required standardWCAG 2.1 Level AADOJ-adopted standard

Did you know the deadline already changed?

If your compliance calendar still shows the original date, it's out of date: on April 20, 2026 the DOJ issued an Interim Final Rule that moved every ADA Title II web deadline back one year. For Provo, the operative date is now April 26, 2027. The public comment period closed June 22, 2026 — the deadline is set, and the clock is running.

Provo's latest accessibility scan

Overall compliance risk: High — 2 citizen services residents with disabilities may be unable to use

82/ 100
Page score

provo.gov · 60 pages scanned · July 13, 2026

📖 Reading level: grade 10.6 average — above the grade-8 plain-language target for government content.

📄 PDFs found: 0, failing basic accessibility checks: 0

⚠ Critical Service Risks

These citizen services appear to have no accessible alternative pathway — the highest-exposure findings in this scan:

  • Utility service sign-up or management — The only pathway we found for this service fails 7 serious accessibility checks — including: composite controls are missing required child elements for assistive tech. Residents using assistive technology may be unable to complete it.
  • Court services — The only pathway we found for this service fails 4 serious accessibility checks — including: composite controls are missing required child elements for assistive tech. Residents using assistive technology may be unable to complete it.

Top issues, in plain English

  • critical Composite controls are missing required child elements for assistive tech (WCAG 1.3.1 · 18 pages)
  • critical Accessibility attributes point at elements that don't exist (WCAG 4.1.2 · 11 pages)
  • critical Delayed refresh under 20 hours must not be used (WCAG 2.2.1 · 3 pages)
  • serious Text is too low-contrast against its background to read comfortably (WCAG 1.4.3 · 45 pages)
  • serious Embedded frames have no title, so screen readers announce them as unnamed (WCAG 4.1.2 · 18 pages)
Get the full page-by-page report →

Every page, every issue in plain English, weekly change monitoring, and deadline tracking. Annual plans from $1,200/yr — no sales call, no demo. Already a customer? Sign in.

What WCAG 2.1 Level AA means for city government websites

Because Provo serves 115,479 residents — above the DOJ's 50,000-person threshold — it falls in the first enforcement wave, with the earlier of the two federal deadlines.

The rule points to WCAG 2.1 Level AA — a widely used technical checklist. Stripped of jargon, it asks simple questions: can a blind resident using a screen reader pay a bill on your site? Can someone who can't use a mouse complete a form with just a keyboard? Is the text readable against its background?

For first-wave entities, the practical risk isn't only DOJ action — it's private lawsuits and demand letters that cite the federal standard the moment the deadline passes.

Provo is a major population center, and its website is the front door for utility bill payment, permit applications, and public meeting agendas. Under ADA Title II, that front door has to work for every resident.

Don't find out about problems from a demand letter

A11yCheck monitors Provo's website continuously and sends a plain-English weekly digest — no technical background needed.

Get an email if the federal deadline moves again or Provo's score changes. One-click unsubscribe.