Building the Record: Complaints, Training, and Your Patrons
Trust note
This article was written by a person and reviewed against accessibility.chat editorial standards. Treat it as research and education rather than legal advice. We prioritize primary sources and correct material errors.
In a small community, the real complaint path is a patron telling you at the desk. Log it anyway.
The question you're actually being asked is never whether you were perfect. It's whether you knew, and what you did about it. A dated record is the only thing that answers that — and at one-librarian scale, building it has to be simple enough that it actually happens.
Log it the day you hear it, whatever channel it arrived by
Email, phone, a form on your site, or — most commonly in this sector — a patron mentioning it at the desk. That last one is the channel most likely to go unrecorded if you don't build the habit deliberately, because it feels like a conversation, not a complaint. Log it anyway. An unlogged complaint is the worst fact any file can contain, because it means the record shows you didn't know when the truth is you did.
Acknowledge quickly, solve the person's actual access first by whatever means available — staff-mediated search, a different format, a phone walkthrough — while any underlying fix gets scheduled separately. Reproduce and classify: isolated, or systemic? If it's a licensed platform, the fix likely isn't yours to make directly; log it as a vendor issue and let it feed your renewal-time leverage rather than a remediation queue you can't actually execute.
A shorter intake log than most sectors, and that's fine
Date received, channel, person and contact (or anonymous), item affected, the barrier in their own words, access provided now, whether it's your content or a licensed platform's, and what the person was told. Fewer columns than a larger institution might run, sized to actually get filled in by one person working in stolen hours. A log that's simple enough to maintain beats a comprehensive one that quietly stops being updated after the second week.
Training, sized to fit
Whoever posts content for the library needs the basics: headings, alt text, link text. Whoever staffs the desk needs to know the one instruction that matters most — log it the day you hear it. If your library board or a state library association offers free accessibility training, use it rather than building your own; your hours are better spent on the intake habit than on curriculum development.
The people this is actually for
Find your local disability organization, or ask your state library association or regional cooperative for contacts if your community doesn't have one directly. One conversation with an actual patron who uses assistive technology tells you more than a lot of scanning ever will. Report back what changed because of what they told you — even a small change, communicated honestly, is what turns a one-person program into a real relationship.
This isn't legal advice on what your specific process needs to contain — verify against DOJ's own guidance (opens in new window) and your counsel. When a complaint names a specific licensed platform, ask Luke to take a first pass at it while you're logging the entry.
Previous: how to read a VPAT · Next: reporting up, your maturity roadmap, and the budget ask
Sources: DOJ guidance on web accessibility and the ADA (opens in new window) · Web Content Accessibility Guidelines (WCAG) 2.1 (opens in new window) · Accessibility Conformance Report (ACR) overview (opens in new window) · 28 CFR Part 35, Subpart H — Web and Mobile Accessibility (opens in new window)
About Jeff Fryer
Jeff Fryer spent years working kitchens before moving into ADA compliance work for local government. He writes from that experience -- direct, plainspoken, allergic to compliance theater. Contributing writer at accessibility.chat.
Jeff Fryer is a person, not one of the AI analyst lenses this site also publishes under. A named human is accountable for this article.
Specialization: Local government ADA compliance, contributed from direct field experience
Authorship and Editorial Process
Jeff Fryer wrote this article. AI was not used to draft it. It went through the same editorial checks as everything else published here.