Digital Accessibility Training for Faculty: Designing a Programme That Actually Completes

Every institution facing an accessibility deadline reaches the same realisation, usually about four months in: remediation alone is a treadmill. A team fixes last year’s course materials while this year’s are produced with exactly the same defects, by the same people, for the same reasons. The only intervention that changes the inflow is training the people who make the content. And yet accessibility training for faculty has a reputation for going nowhere — announced with enthusiasm, completed by the converted, ignored by everyone else, and impossible to report on. This guide is about designing the version that works: what to teach, how much, how to make it mandatory without provoking a revolt, and how to produce the completion evidence that the whole exercise ultimately has to stand on.

Why most faculty accessibility training stalls

The failure modes are consistent across institutions, and none of them are about faculty being unwilling.

• It is taught as law. An hour on WCAG conformance levels and the Rehabilitation Act produces compliance fatigue and no behaviour change. Academics respond to evidence about students; they do not respond to statutes.
• It is too long. A six-hour certification is a reasonable ask of an instructional designer and an unreasonable one of a professor in week three of term. Completion rates collapse past about two hours.
• It is generic. Training built around a generic web page teaches nothing about the actual artefacts — a lecture recording, a problem set PDF, a slide deck with a chart, a spreadsheet of data.
• It is voluntary. Optional training reaches the people who were already going to fix their captions.
• Nobody can report on it. If the record is an attendance sheet from a workshop and a mailing list, the institution cannot answer “what proportion of teaching staff in this school has completed it?” — which is the only question that matters when someone asks.

Fix those five and the programme works. Ignore them and no amount of content quality rescues it.

What to teach in the first ninety minutes

Scope ruthlessly. The goal is not to produce accessibility specialists; it is to stop the five defects that account for most of the barriers students actually hit. In rough order of volume:

1. Captions on video. How to generate them, why the automatic output must be reviewed, and what “accurate” means in practice — names, terminology, equations. This alone addresses the largest share of complaints.
2. Document structure. Using real headings rather than large bold text, in Word, Google Docs, slides and the LMS editor. Two minutes of instruction that changes every document a person produces thereafter.
3. Images and alt text. When an image needs a description, when it is decorative, and how to describe a chart — by stating what it shows, not what it looks like.
4. Colour and contrast. Not relying on colour alone to convey meaning, and checking that text meets contrast minimums. See our colour contrast guide.
5. Accessible PDFs and slides. Mostly: export properly from the source rather than printing to PDF, and keep the source file.

Open with a screen-reader demonstration of a real course page from your own institution — with permission, and anonymised. Ninety seconds of hearing an unlabelled button announced as “button” does more than an hour of guidelines. Our WCAG checklist for course creators works well as the take-away reference, and how to make online courses accessible covers the wider practice.

Making it mandatory without a revolt

Mandatory training is a governance decision, not a communications one, and it needs three things in place before the first email goes out.

A sponsor with standing. A dean, a provost’s office or a department chair — someone whose name on the message means the deadline is real. Accessibility offices rarely have the authority to compel and should not be asked to pretend otherwise.

A defensible reason. Lead with students, then the obligation. “Roughly one in five of our students reports a disability, and a third of them tell us they have been unable to complete a required activity this year” lands very differently from “the Department of Justice requires this.” Use your own institutional data if you have it; if you do not, that gap is itself worth naming.

A proportionate ask. Ninety minutes, self-paced, with a due date roughly six weeks out and a genuine exemption path for staff who have completed equivalent training elsewhere. Then annual recertification of perhaps thirty minutes, covering what changed — not the whole course again. Recertification is where most programmes quietly die, and keeping the renewal short is what prevents it.

Pair the mandate with office hours. The training creates questions about real course material — “how do I caption a recorded lab?”, “is this chart described well enough?” — and a standing slot with the accessibility office converts a compliance exercise into a support relationship. It is also where you learn what to fix in the platform.

Measuring it in a way that survives scrutiny

The completion report is not bureaucracy; it is the artefact the entire programme has to produce. Four measures are enough:

• Completion by department, against the due date. The headline. Aggregate figures hide the school that has done nothing, and the school that has done nothing is the one that generates the complaint.
• Content change. The proportion of new course material published with captions and alt text, before and after. This is the measure that shows the training worked rather than merely happened.
• Barriers reported by students, and time to resolution. Reports going up initially is a good sign — it means people now know where to report.
• A short satisfaction survey, anonymous, five questions, with free-text answers read in full. Faculty will tell you exactly which module wasted their time.

Report these honestly, including when a target is missed. A programme that reports 61% completion in one school and explains why is more credible — internally and externally — than one that reports a rounded institutional average.

A rollout that fits one term

Run the first cycle in a single school rather than across the institution. One school gives you a real completion rate, a manageable support load, and a sponsor who can actually chase people — and if the design is wrong, you find out at a scale where fixing it costs a fortnight rather than a year.

A twelve-week shape that works:

• Weeks 1–2 — agree the mandate. Sponsor confirmed, cohort defined by name, due date fixed, exemption path written down. Decide now what the completion target is and what happens if a unit misses it, because deciding afterwards looks arbitrary.
• Weeks 3–4 — build the institution-specific core. Take the generic material and replace every example with your own: your LMS, your slide template, a real lecture recording, a real problem set. This is the step most programmes skip and the one that determines whether anything transfers.
• Weeks 5–6 — pilot with a friendly department. Ten to fifteen people, watched closely. Time how long it actually takes; the answer is usually longer than the estimate, and the fix is cutting content rather than extending the deadline.
• Weeks 7–10 — launch to the cohort. Assign it with a due date, send two reminders rather than five, and hold weekly office hours where people bring their own course material. Publish a running completion figure by department — visible progress does more than any reminder email.
• Weeks 11–12 — report and decide. Completion by department, the satisfaction survey read in full, what changed in published content, and a go or no-go for the next school.

Expect the first cycle to land somewhere between 70% and 90% rather than at 100%, and plan the follow-up for the remainder as part of the design rather than as a failure. The units that do not complete are information: usually they are the ones with the heaviest teaching load, which is also where the most course content is being produced.

Build it, buy it, or both

Building your own has one decisive advantage: the examples are your own courses, in your own LMS, with your own templates, which is exactly what makes training stick. The cost is production time and the maintenance burden when the tooling changes.

Buying an off-the-shelf course — Deque University and similar programmes are the established options — gets you depth and immediacy, and suits specialists well. The trade-off is that generic examples generalise poorly to a specific institution’s workflow, and per-seat pricing across all teaching staff adds up quickly.

The pragmatic answer for most institutions is a hybrid: a ninety-minute institution-specific core that everyone takes, using your own materials, plus deeper specialist modules for instructional designers, web publishers and the accessibility office. Run the core on a platform that can assign it, chase it, record completion by department and reissue it annually — because the reporting requirement is what distinguishes a programme from a workshop.

Whichever route you take, budget for the second year at the outset. Programmes fail at recertification far more often than at launch.

Eduspera is an accessibility-first learning platform built to sit alongside a campus LMS rather than replace it: WCAG 2.2 AA as a product requirement, a published Accessibility Conformance Report, public HECVAT answers, SAML single sign-on with InCommon metadata, SCIM provisioning and LTI 1.3 with grade passback. Institutions can start from the 12-week pilot kit, which sets out the plan, the metrics and the technical checklist your identity and data teams will work through.

Frequently asked questions

How long should faculty accessibility training be?

Around ninety minutes for the core programme, self-paced, with roughly thirty minutes of annual recertification covering what has changed. Completion rates fall sharply beyond about two hours. Depth belongs in optional specialist modules for instructional designers and web publishers, not in the course everyone has to take.

Can we make accessibility training mandatory for academic staff?

Institutions do, and increasingly must, but it needs a sponsor with actual authority — a dean or the provost’s office rather than the accessibility office alone — a proportionate time commitment, a realistic deadline and an exemption path for equivalent prior training. The mandate is a governance decision before it is a communications one.

What should the training actually cover?

The five defects that produce most real barriers: captions on video, real heading structure in documents, alt text for images and charts, colour and contrast, and exporting accessible PDFs and slides. Teach them using your own institution’s course materials rather than generic web examples.

How do we prove faculty completed it?

Run it on a platform that assigns the course to named staff with a due date and reports completion by department. An attendance sheet from a workshop cannot answer the question an auditor or a regulator asks, which is what proportion of teaching staff in a given unit completed the training by the deadline.

Should we build our own course or buy one?

Most institutions do both. A short institution-specific core using your own courses and templates is what makes the training transfer to daily practice; bought specialist modules add depth for the small group who need it. Whichever you choose, plan the annual recertification at the start — that is where programmes usually fail.