Your first UDOIT pass
Open UDOIT from the Canvas course menu.
Open the course you want to check and select UDOIT in the course navigation. The first time UDOIT is opened in a course, it performs an initial scan of the course's Canvas content and files.
Course Accessibility
Select UDOIT from the Canvas course navigation to open the course accessibility dashboard.
If you do not see UDOIT in the course menu, contact the CTL instead of spending time searching for a hidden setting.
Let the scan finish. Use “Scan Now” only when you need a fresh check.
UDOIT can scan automatically when you open it after the configured interval. Scan Now checks content and files added since the most recent scan. Use the three-dot menu and Full Rescan when you intentionally want UDOIT to start over and scan the entire course.
Initial scans can take from seconds to several minutes depending on the course.
Use the Scorecard as triage—not as a grade.
If Moraine Valley has course scoring enabled, UDOIT may show a Scorecard with High, Medium and Low impact categories and an overall course accessibility score. Start with repeated high-impact issues or a problem that appears many times.
Best first move: fix one repeated issue type. Twenty missing alt texts are often easier than twenty unrelated fixes.
For Canvas content, open the issue and use UFIXIT.
UDOIT's UFIXIT interface lets you repair many Canvas-content problems without leaving UDOIT. Depending on the issue, you can add alt text, improve link text, correct contrast, or make another targeted change. Save the change and move to the next occurrence.
For uploaded documents, use Review Course Files.
UDOIT scans common course files including PDF, Word, PowerPoint and Excel files. Open Review Course Files to see file-level issues. Some files need to be fixed in the original application and replaced; UDOIT can also offer alternate-format options for some files.
Review accessibility findings · replace corrected file
Review accessibility findings
Rescan, then do a short human check.
After a batch of repairs, run the appropriate scan again. Then manually check the parts automated tools cannot reliably judge: whether alt text actually makes sense, whether headings describe the page, whether link text is meaningful, whether a complex image has an equivalent explanation, and whether required third-party tools are usable.
Remember: UDOIT checks common accessibility issues; it is not a complete WCAG certification tool.
Before you call the course done, check what UDOIT cannot fully judge.
UDOIT catches many common barriers, but a few areas still need a person to look at them in context:
- Third-party tools and embedded content — Publisher platforms, LTIs, embedded websites, iframes and other external tools may sit outside UDOIT’s view. Check the real student task and make sure an accessible alternative exists when needed.
- Complex images, charts, and diagrams — A checker can tell you that text is present; it cannot tell you whether the description communicates the instructional meaning.
- Human review: alt text quality — Make sure descriptions are useful in the context of the page, and mark decorative images appropriately.
- Human review: headings and page structure — Make sure headings describe the content and create a logical outline rather than simply looking large or bold.
- Human review: link purpose — Make sure link text tells students where the link goes or what it does without relying on surrounding text.