Most accessibility writing about Colorado's digital accessibility law focuses on the website. The website matters — but for a clerk, the document that puts your jurisdiction at the most legal risk every two weeks is the meeting agenda packet. It's the artifact you post most often, the one residents are most likely to download, and the one most likely to be assembled from a stack of sources that were never written to be accessible in the first place.
The grace period that gave good-faith local governments cover under HB24-1454 ended on July 1, 2025. The statutory damages provision in HB 21-1110 — $3,500 per violation, per affected individual, on top of any actual damages — has now been live for about ten months. This post is a clerk-level walkthrough of what that law actually demands of an agenda workflow, where the gaps usually are, and what "compliant" looks like in practice.
What HB 21-1110 Says — In Plain Terms
House Bill 21-1110, passed in 2021 and amended in 2023 by Senate Bill 23-244, requires every state and local government entity in Colorado — counties, municipalities, special districts, school districts, and the agencies attached to them — to make their public-facing digital content conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.
Two pieces of that sentence do most of the work:
- "Public-facing digital content" includes your website, your meeting portal, your agenda PDFs, your minutes documents, your packet attachments, your videos, your email templates, and your social media. The law does not draw a line at "the website" and stop.
- "WCAG 2.1, Level AA" is a technical specification with about 50 success criteria. For a clerk's purposes, the practical translation is: every document you publish must be readable by a screen reader, navigable by keyboard, contrast-compliant for low-vision users, and structurally tagged so assistive technology can understand it.
The law is enforced through a private right of action. An individual with a disability who encounters an inaccessible document can file suit in Colorado state court. If the court finds discrimination, it can order remediation, award actual damages, and assess statutory damages of $3,500 per violation. "Per violation" is the phrase to read carefully — it is not capped at one violation per agency.
HB 21-1110 is not the federal ADA. It's stricter.
Federal Title II requires non-discrimination but historically left "what counts as accessible" to interpretation. HB 21-1110 names the standard (WCAG 2.1 AA), names the dollar amount ($3,500), and gives any individual standing to sue. That combination is unusual at the state level, and Colorado is one of the first states to write all three into one law.
Where the Agenda Workflow Usually Fails
An agenda packet is rarely one document. It's a cover sheet, a list of items, a set of staff memos, ordinances or resolutions, exhibits, financial statements, contracts, and supporting correspondence. Each piece comes from a different system, drafted by a different person, and stitched together — often by a clerk on a deadline. Every step in that pipeline is a chance to introduce an accessibility failure.
In practice, almost every gap traces back to one of these:
1. Scanned PDFs
If a department head scans a signed contract and emails it to the clerk for inclusion, what arrives is an image. To a screen reader, an image of text is a blank page. WCAG 2.1 AA Success Criterion 1.4.5 (Images of Text) and 1.1.1 (Non-text Content) both apply. The fix is OCR plus tagging — running the scan through optical character recognition, then verifying that the resulting text is in the correct reading order.
2. Untagged PDFs from Word
"Save as PDF" from Word produces a PDF. It does not, by default, produce a tagged, structured PDF. Headings look like headings to a sighted reader because the font is bigger and bolder; to a screen reader they're just paragraph text in a larger size. The agenda's structure — sections, subsections, lists, tables — is invisible to assistive technology unless tags are explicitly written into the file.
3. Tables used for layout
A common pattern in older agenda templates: a two-column table where column one is "Agenda Item" and column two is "Action Requested." If that table was built for visual layout rather than as a true data table with headers, a screen reader reads it cell-by-cell with no context. Success Criterion 1.3.1 (Info and Relationships) requires that the relationship between header and cell be programmatically determinable.
4. Color-coded vote indicators
Minutes that show votes as red/green dots without text labels fail Success Criterion 1.4.1 (Use of Color). The user with red-green color blindness cannot tell who voted yes. The fix is text — "Yes," "No," "Abstain" — accompanying any color cue, or replacing the color cue entirely.
5. Embedded video without captions
If your meeting is livestreamed and archived, the video itself is public-facing digital content. WCAG 2.1 Success Criterion 1.2.2 requires captions for prerecorded video. Auto-captions are a starting point, not a finish line — they are not accurate enough to satisfy the standard for proper names, motion language, or technical terms (the kind of vocabulary that fills a council meeting).
6. The packet is one giant PDF
A 200-page combined PDF with no bookmarks, no table of contents, and no internal navigation may technically be "tagged" but is not navigable. WCAG 2.4 (Navigable) requires that users can locate content within a page. For a long packet, that means functional bookmarks, a linked table of contents, and meaningful page titles.
Where Most Colorado Clerks Are Right Now
Anecdotally — and based on the volume of questions hitting the Colorado Municipal League's digital accessibility resource pages — small and mid-sized Colorado jurisdictions cluster into roughly four states of readiness:
- Aware but not started. The clerk has heard of HB 21-1110, possibly attended a CML webinar, and has flagged the issue to administration. No structural changes have been made to the agenda workflow. This is the most common state.
- Website remediated, agendas not. A vendor was hired to retrofit the public-facing website. Agendas continue to be produced through the legacy Word + scan + combine pipeline. The clerk is doing the same job they did in 2023.
- Agenda template fixed, packet contents not. The cover sheet and agenda outline are now produced from a template that generates a tagged PDF. Attachments — staff memos, ordinances, contracts — still arrive in whatever form their authors send them, and are inserted as-is.
- End-to-end remediation. Every document in the packet is either generated by an accessible system or remediated before posting. The workflow has been redesigned around the standard rather than retrofitted around it.
The legal exposure is concentrated in the first three categories. A complaint filed against an agency in category one or two would be very difficult to defend on the merits. A complaint against an agency in category three would turn on the specific document the complainant downloaded and whether it was internally produced or attached.
The Five Things to Audit This Quarter
If you're a clerk who has read this far and is now wondering where to start, the answer is not "hire a consultant." Start with a specific, narrow audit of the documents you control most directly.
- Pull last month's agenda PDF and run it through the Adobe Acrobat accessibility checker. The free version is good enough. Note every error and warning. Most clerks who do this for the first time discover 30–80 issues in a typical packet.
- Identify which of those issues come from the cover sheet, and which come from attachments. The cover sheet is yours. The attachments belong to whoever submitted them. Both need to be fixed, but the remediation paths are different.
- Write a one-page submission standard. Department heads need to know that staff memos must be submitted as Word documents using a styled template — not as scans, not as flattened PDFs, not as photos of printouts. Without this rule, your remediation work will never end.
- Audit your minutes template for color-only voting indicators. If "yes" and "no" are distinguished only by red/green text or icons, change the template. Add explicit text labels and use shapes or position alongside color.
- Check whether your archived meeting videos have captions, and whether those captions were human-edited. Auto-generated captions on a Granicus or YouTube stream are a starting point, but legal exposure on long-form video is real if the captions are full of obvious errors.
Each of these is a few hours of work, not weeks. None of them require a vendor. All of them measurably reduce risk.
Remediation vs. Replacement
The dominant question across small-government accessibility conversations in 2026 is whether to keep remediating the existing workflow or replace it. The honest answer depends on volume.
If your agency posts twelve agenda packets per year and they're each 40 pages, remediation works. The cost of having someone tag and verify each document is bounded. The workflow change is small.
If your agency posts 50+ agendas per year (city councils with weekly committees, school districts with multiple boards, counties with active planning commissions), the math shifts. Remediation becomes a permanent staffing line item. At that volume, generating accessible documents at the source — through a system that produces tagged, structured output as a default — is usually cheaper than retrofitting forever.
This is the structural argument for moving off Word-and-email-and-scan as an agenda pipeline. Not modernization for its own sake, but because the labor cost of compliance grows linearly with packet count under remediation, and is roughly flat under generation.
What Compliance Actually Looks Like
For a clerk, "we are HB 21-1110 compliant" is a meaningful statement when these things are simultaneously true:
- Every public-facing PDF on your website passes the Adobe Acrobat accessibility check with no errors and only justified warnings.
- Every agenda is produced from a structured source — a template, an agenda management system, or a tagged Word file — not by combining scans.
- Every staff memo, ordinance, and resolution included as an attachment was authored in a tagged format or remediated before posting.
- Every archived video has accurate captions (human-reviewed, not auto-only) and a transcript.
- Every form on the website (contact us, public comment sign-up, FOIA request) has properly labeled fields and visible focus states for keyboard navigation.
- You have a documented accessibility complaint process, named on your website, with a real human to whom complaints route.
- You have an accessibility plan, written and adopted, identifying who is responsible for what.
That last item — the plan — was a quiet expectation of the OIT rules issued under HB 21-1110, and it remains the single most under-implemented requirement at the local level. It is also the easiest defense to a complaint: a written plan, reviewed annually, demonstrates the kind of good-faith program effort that courts have historically considered when evaluating discrimination claims.
The single most useful free resource is the OIT's standards page.
The Colorado Office of Information Technology maintains the rules, FAQs, and exemption process at oit.colorado.gov/accessibility-law. Read it before you read anything a vendor sends you.
The Quiet Cost of Doing Nothing
The headline risk under HB 21-1110 is the lawsuit. The actual experienced cost, ten months into post-grace-period enforcement, is more often something else: complaints filed with the Colorado Civil Rights Division, demand letters from disability rights advocacy organizations, and the staff time required to respond to them. A single demand letter that asks for a remediation plan, sample documents, and proof of training can absorb a clerk's office for a week.
The scale of this is hard to measure precisely because most resolutions happen privately, before litigation. But the conversation among Colorado clerks shifted noticeably after July 2025. Compliance is no longer "something we'll get to." For most agencies, it is now an active line item in the work plan — or it is becoming one in response to outside pressure.
The clerks who are quietly getting ahead of this are the ones who started before the deadline, made the workflow change once, and now run an accessible packet pipeline as a matter of course. The cost they paid was a few months of process redesign. The cost the agencies in category one are facing — remediating a backlog of public records under threat of complaint — is meaningfully larger.
If You Take Only One Thing From This
It is this: HB 21-1110 enforcement does not turn on whether your website looks accessible. It turns on whether the specific document a person with a disability tries to read is readable by the assistive technology they use. The clerk's job, in compliance terms, is to make sure that for every document the agency publishes, the answer to that question is yes.
The fastest way to get there is to stop adding inaccessible documents to the pipeline starting today. Remediating last year's archive is a separate, slower project. But the bleeding stops at the source.
Sources: Colorado General Assembly — HB21-1110 bill text and history · Colorado General Assembly — SB23-244 Technology Accessibility Cleanup · Colorado General Assembly — HB24-1454 Grace Period Extension · Colorado OIT — Digital Accessibility Law · Colorado OIT — HB21-1110 FAQ · Colorado Municipal League — Digital Accessibility resources · W3C — WCAG 2.1 Quick Reference