The Problem...was simple:

We don't have a website for UCF faculty to refer to when they have trouble with UDOIT.

The Universal Design Online Content Inspection Tool, or UDOIT, gets usage across the entirety of the University of Central Florida (UCF) by faculty and administrators. With the already high usage rate and the new UI overhaul, we've received an influx of Instructional Designers and professors requesting assistance with the platform.

The Context:

So, what is UDOIT?

UDOIT is a Canvas extension which was created by UCF's Center for Distributed Learning. The goal of UDOIT was to better online course learning for UCF students through providing course scans to faculty which would alert them of accessibility violations. Each scan audits a course in compliance with WCAG and ADA standards, looking out for visual, cognitive, and auditory needs, but mainly targeting course elements or styles that may inhibit users from properly interacting with the course.

My response:

In order to create a hub where Instructional Designers felt comfortable fully routing faculty to the website for solutions, I had to understand the types of information that users were relying on UDOIT for.

users wanted:

Navigation information

there has been no explicit documentation or tutorials for first-time users. usage direction has been implicit, but users had trouble adjusting after the recent overhaul.

Information egarding the error they were stuck on

course violation errors used to be listed deep into the product itself. there were no tutorials or self-written steps to solve course errors, only external documentation

The next consideration was what we wanted out of the website, as a company. Seeing as UDOIT was our open-source product, we wanted a website that could be relied on for up-to-date information.

we needed:

an equal mix of "what is udoit?" and "how to use udoit"
commonly asked questions addressed up front
installation information

And from those considerations, the UDOIT website was imagined.

I made mindful, accessible wireframes which took the needs of faculty into a responsive, helpful, curated website.

I began with interviewing faculty in round-table discussions, and analysing their pain points in the product itself. I met with the Product Owner, and coordinated the best method for responding to user concerns.

I created a space where university administrators could get useful instructions for installation and integration, but kept the website friendly enough for professors to seek answers for the issues they face while scanning their courses.

Check out my process on Figma 💻

Universal Design Online Content Inspection Tool (UDOIT) Website