Getting Started with Accessibility in UDOIT

Whether you’re new to UDOIT or a seasoned pro, you’re likely juggling limited time, different student accommodation needs, varying levels of familiarity with accessibility, and competing course priorities.

The Ways to Get Started panel on the right side of the UDOIT Scorecard is especially helpful for users who are new to accessibility or may feel overwhelmed by a full list of issues. It guides you toward manageable starting points and groups similar issue types together, making remediation more efficient and consistent.

Choosing a Way to Get Started

UDOIT’s Ways to Get Started panel is designed to reduce overwhelm by organizing accessibility work into clear, focused workflows. Each option below supports a different remediation strategy, helping you prioritize issues, build confidence, and make consistent progress.

Easiest to Fix

If your main goal is to make progress quickly, this is often the most approachable and expedient way to get started. The Easiest to Fix issues are ones you can typically resolve right from within the UDOIT interface, without needing to dig into your course for additional context.

Start with the Easiest to Fix option if you are limited on time, you want visible progress right away, or you’re new to UDOIT and/or accessibility

High Impact Issues

In addition to selecting individual issue types sorted by their accessibility score from the High Impact category of the Scorecard Home screen, you can also choose to work through ALL high-impact issues.

This approach is helpful if you want to focus your time where it matters most. High Impact Issues are those that significantly affect learner access and contribute heavily to your course’s overall accessibility score.

Start with the High Impact Issues option if you want to improve your accessibility score efficiently, you’re preparing for a review or audit, or you need to prioritize changes that most affect students.

By Issue Type

This is an extremely helpful workflow to focus on one particular group of issues, for example, providing alternative text for images or links that aren’t descriptive

By focusing on one issue type repeeatedly the cognitive load is reduced, allowing you to increase your familiarity with the task at hand.

Start with the By Issue Type option if you are new to using UDOIT, you have limited time and want to see progress quickly, or your course content follows similiar patterns.

By Impact Type

This approach shifts the focus from the technical issue itself to the learner experience. Instead of asking “What’s wrong with this content?” you’re asking “Who might struggle with this, and why?”

There are four possible impact types: visual, auditory, cognitive, and motor.

Start with the By Impact Type option if you’re supporting a specific student or group of students with specific DASS accommodations, or you’re reviewing accessibility more intentionally with student needs in mind.

By Content Type

This option allows you to work through all errors found within a typical type of content in Canvas. If you tend to think about your course in terms of Canvas content areas rather than accessibility concepts, this view may feel the most intuitive. Sorting by content type lets you focus on where the issues live, making it easier to tackle accessibility as part of your normal course maintenance or term prep.

Content types you can review include announcements, assignments, classic quiz directions, discussion board directions, pages, and the syllabus area.

Start with the By Content Type option if you are getting ready for a new term (before it’s published for students), you want to focus on what students will see most, you prefer to move through the discrete content areas one-by-one, or you have a preferred content type that you work with more than others.

Updated on February 6, 2026
Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Submit a Help Request

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

css.php