Body
Overview
This article provides guidelines and best practices for using the UDOIT course accessibility tool in Canvas.
When should I run a scan?
Make UDOIT scans a regular part of your Canvas workflow. Run UDOIT before your Canvas site becomes available to students at the start of the semester and any time you add a new batch of content to your Canvas site. Regular scans reduce the time you spend on retroactive fixes later.
How do I read the scorecard?
UDOIT gives your course an accessibility score, shown as a percentage. This score comes from a scorecard that groups issues into three categories: high, medium, and low impact.
Click on any category to see its issues and recommended fixes. The percentage and score dial update automatically as you make changes.
Treat the scorecard as a progress tracker, not a judgment. Use it to prioritize your next fix and watch your score improve over time.
To review and fix issues, click the toggle next to the section title to view issues for the section, and click the green UFIXIT button to remediate the issue. (NOTE: not all issues will be fixable via the UFIXIT interface. If you have questions, please contact DLINQ for a conversation.)
Where do I start if I have a lot of issues?
Seeing many issues on your first scan is normal. Start with the high impact category first, since these issues most affect student access and learning.
Within high impact issues, pick whichever category feels easiest to fix. For example, broken links are usually quicker to fix than remediating whole documents.
In many cases, you can fix an issue directly inside the UDOIT interface, which speeds up your workflow.
Do I have to fix every issue UDOIT finds?
No. You do not have to make every change UDOIT suggests. Fixing even a few issues still improves access and learning for your students. Aim for progress, not perfection.
How do I get more help?
Email dlinq@middlebury.edu if you get stuck or need help fixing an issue.