For towns, counties and special districtsNow taking towns, Colorado firstNow open, Colorado first

The Readable Record

The file you can show. Every month, dated: what was posted, what we fixed and who checked it, what was set aside and why, and how requests for help were answered.

A sample month

Readable Record

Town of Anytown · sample

RT-ANY-2026

A sample Readable Record for a fictional town, three months. The numbers are illustrative.
MonthScannedNew filesNewFixed, checkedFixedArchivedRequests
Jul 2026 Jul 1 9 9 2 0
Aug 2026 Aug 3 12 12 0 1
Sep 2026 Sep 1 14 14 1 0
Sample page for a fictional town. The numbers are illustrative.

September, file by filesample

  • agenda-sep-01.pdf Fixed: headings, list, reading order Checked by D.L., Sep 3
  • packet-sep-01.pdf Fixed: 42 pages, 6 tables, 3 maps described Checked by D.L., Sep 4
  • minutes-aug-18.pdf Fixed: scanned, text added Checked by D.L., Sep 4
  • minutes-2019-03.pdf Archived: made before the date, kept for reference, not changed, in the archive section Reason logged Sep 4
  • and 11 more files, each fixed and checked

What each month holds

  • The scan

    The date we scanned your site and how many pages and files we read.

  • Every fix

    Each file, what was fixed, who checked it and on what day.

  • Every decision

    Files set aside as archived or preexisting, each with the reason written down.

  • Every request

    Requests for help from residents, and how and when they were answered.

  • Vendor letters

    Letters asking your website and agenda vendors about the accessibility of their products, and their replies.

Why keep one

The rule puts the burden on the town. A government that falls short is treated as meeting its duty only where it can show the gap barely affects access. A record kept as you go is where that showing starts.

It is not a certificate and it guarantees nothing. It shows the work, and when it was done.

“A public entity that is not in full compliance with the requirements of § 35.200(b) will be deemed to have met the requirements of § 35.200 in the limited circumstance in which the public entity can demonstrate that the noncompliance has such a minimal impact on access ...”

In Colorado

State rules let a town publish an accessibility plan on its website and update it every year with its progress. Each month’s record gives you the lines for that update.

The plan is yours: what it says, and whether it is enough, is your town’s decision with its attorney.

Colorado law, in plain language

“To demonstrate good faith, the Accessibility Plan must be updated annually with progress the public entity has made on advancing technology accessibility.”

How readable is your town?

Send us your website. A person opens the latest agenda you posted and tells you, on one page, what a screen reader finds in it. Free.