Building the Record: Complaints, Training, and Your Students
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.
A student's accommodation clock is a semester. An intake process built on administrative time will fail them even when it technically succeeds.
The question you're actually being asked is never whether you were perfect. It's whether you knew, whether you had a plan, and what you actually did about it. A dated record answers that. Nothing else does — and in this sector, the record has to move as fast as the semester does.
Log it, solve access first, fix the defect on its own track
Whatever channel it arrives on — disability services, a faculty email, the IT help desk — log it the day it arrives. 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 fast, and structure your intake around the academic calendar, not administrative convenience — a student who can't access a reading due Thursday doesn't have six weeks. Solve their actual access first, by any workable means, while the underlying fix — an accessible-by-default template, a remediated file, a vendor ticket — gets scheduled on a separate track. Reproduce and classify: isolated, or systemic? A broken course template outranks a single broken reading, because fixing the template protects every student who touches it going forward, this semester and every one after.
Twelve columns, filled in every time
Date received, channel, person and contact (or anonymous), item affected, the barrier in the student's own words, assistive technology involved if known, access provided now and the date, systemic or isolated, corrective action and owner, target date, resolution date, and what the person was actually told. That last column is the one people skip and the one that matters most.
Training that reaches faculty, not just content authors
Short, role-specific, repeated. Content authors and course designers need headings, alt text, and the document checker built into accessible-by-default templates. Whoever buys campus software needs to demand and actually read an ACR (opens in new window). And faculty specifically need a low-friction path to request remediation help — the academic-freedom-versus-accessibility tension in this sector isn't resolved by a policy memo faculty never read; it's resolved by making the accessible path easier than the alternative, with deans carrying the expectation rather than a coordinator alone trying to enforce it department by department.
The people this is actually for
Find your local disability organization and your own disabled students — actual people who are already navigating your systems and already know where the real barriers sit. Offer a standing invitation and pay them for structured testing time. Bring them your top student-facing tasks before launch. Report back what changed because of what they found. One genuine relationship surfaces more real barriers than a semester of automated scanning.
This isn't legal advice on what your specific grievance procedure needs to contain — verify against the joint DOJ-ED guidance (opens in new window) and your counsel. When a complaint names a specific course page, ask Luke to take a first pass while you're logging the entry.
Previous: how to read a VPAT · Next: reporting up, your maturity roadmap, and the budget ask
Sources: DOJ-ED Joint Dear Colleague Letter on Online Accessibility (opens in new window) · Web Content Accessibility Guidelines (WCAG) 2.1 (opens in new window) · Accessibility Conformance Report (ACR) overview (opens in new window) · 34 CFR Part 104 — Section 504 Regulations (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.