How Faculty and University IT Can Share Accessibility Work

Accessibility work is easier to coordinate when responsibilities are explicit. Faculty, IT, learning designers, librarians, disability services and accessibility specialists bring different expertise. This article presents a proposed collaboration model, rather than quotations or a survey of IT directors.

Agree roles around tasks

Faculty can explain teaching intent and improve source material. IT can operate systems and configure access. Learning designers and accessibility specialists can assist with structure and evaluation. Library and procurement teams can request suitable publisher resources. No role is universally able or unable to repair every file.

Make the support route concrete

Provide accessible templates, short authoring guidance and a named route for difficult cases. Assign owners for structural remediation, captions, complex figures and student requests. Include staff time in the plan rather than treating review as free work.

Test what students do

Opening a file on the author's computer does not test every student's access. Review keyboard use, navigation, meaningful alternatives and media. Test important tasks with relevant assistive technologies and respond to reported barriers.

Prioritize with evidence

Start with active tasks and urgent access needs, while checking applicable scope and exceptions for older material. A systematic plan can support governance, but progress or new-content training does not guarantee all legal obligations are satisfied within two semesters.

Aelira Core is beta software. Supported workflows can apply eligible partial fixes and record outcomes, but some inputs need manual work or cannot produce a downloadable remediated file. Review the actual saved output, unresolved findings and content preservation before publication. Automated scores describe implemented checks rather than accessibility conformance. Inspect the public source and release documentation and evaluate a representative authorized sample before planning a rollout.

Measure workload and accepted outputs locally, including failures and specialist fallback. Keep unresolved cases assigned and coordinate timely interim access with disability services.