Loading...
Loading...
"I'm considering removing all slide presentations and images from Canvas courses rather than jump through hoops."
Illustrative faculty concern, not a verified quotation
Faculty are overwhelmed. They won't adopt complex new accessibility tools. Here's how to automate much of the accessibility work so faculty don't need to change their workflow.
Automation figures are based on Aelira's internal estimates; actual results vary by content type and require human review.
Train 500 faculty on new accessibility tool 5% adoption rate Compliance fails
IT coordinates supported scans, human review, and follow-up on unresolved barriers
Average faculty member juggles: teaching 3-4 courses, research, committee work, student advising, grant writing. They have no bandwidth for new tools.
"There is no additional compensation for meeting the new guidelines. This is just more unpaid labor."
Illustrative faculty concern, not a verified quotation
Universities send 10-page PDFs on "How to Use YuJa Panorama." Faculty ignore them. Compliance fails.
Faculty have workflows built over 10-20 years:
Asking them to change = resistance, delay, compliance failure.
Faculty feel blindsided by "sudden" compliance requirements. Instead of embracing accessibility, they:
A large faculty rollout needs clear responsibilities, accessible support, and a way to track files that still need attention.
IT can coordinate supported file processing and human review around existing upload workflows. Test connector readiness and agree when faculty need to check content meaning.
Faculty continues using existing workflow: upload PDFs, PowerPoint, LaTeX to LMS.
IT exports all course files from Canvas/Blackboard using LMS API or manual download.
Run the supported CLI batch workflow on a pilot corpus. Processing time varies; review generated output and record unresolved issues before publication.
Review the saved output, resolve outstanding issues, and obtain the agreed approval before replacing files. Tell faculty what changed and retain the original for rollback.
Goal: reduce duplicated effort while keeping accountable human review
Time per course is not established; measure processing, review, and manual repair effort
Note: These hypothetical planning examples are not customer results or performance forecasts. Weekly course counts are assumed targets to validate in a pilot; include review and manual repair before relying on a schedule.
Test the Canvas connector and agree a review process before using it with faculty files. The maintainer reports integration testing; your institution must validate the full journey.
Faculty uploads PDF to Canvas
Aelira scans supported content; measure processing time in your environment
A person reviews partial fixes and approves the publication path
Faculty are told what was changed and what still needs review
D2L Brightspace is in beta; Blackboard and Moodle are experimental.
Coordinate supported processing, human review, and approved publication around faculty workflows.
Ask about a bounded pilot · Course scope agreed in writing
Evaluate an IT-coordinated workflow, with defined faculty and accessibility review. Use a bounded pilot to measure preparation, corrections and unresolved work.