The Instructure Community will enter a read-only state on November 22, 2025 as we prepare to migrate to our new Community platform in early December. Read our blog post for more info about this change.
The UDOIT developer community has been putting a lot of work into making UDOIT 3 more capable, easier to install, more stable, and easier to debug. This is a fairly large release, but here are the highlights:
You can now filter errors/suggestions by the type of disabilities they affect. These filters are customizable by the institution in the .env file, and we welcome feedback on the default assignments.
The Issue Impact section of the Filters drawer. Options shown: Visual Issues, Auditory Issues, Cognitive Issues, and Motor Issues.
Content in iFrames that is not detected by other multimedia checks (such as YouTube) will produce a suggestion titled "External Content May Be Inaccessible". The text of the suggestion directs the user to manually evaluate and mark the item as resolved.
Screenshot of the iframe suggestion dialog box.
There are many more changes in this release. View the full notes on the UDOIT 3.2.0 Release page.
Feel free to comment on this post if you have any questions or issues with this release. You can also reach us on the UCF Open Source Slack channel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm the Team Lead of the Techrangers, which is a group of part-time students that specialize in course development and software engineering. I'm also the project manager of the UDOIT tool, which is an open source LTI that scans courses for accessibility issues. Check it out at https://github.com/ucfopen/UDOIT
Community helpTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign inTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign in