We designed a four-phase campus rollout of Ally, beginning with a small group of 11 faculty and gradually scaling to a full-campus release after a period of 18 months. We took a very hands-on approach in the early phases of the pilot, using the institutional report to assess the accessibility levels of each course, and then communicating a personalized remediation plan to instructors. The plan included a list of “low hanging fruit” items instructors could fix on their own using Ally, such as adding alternative descriptions to images, and a list of items that our team would fix for them. To effectively scale our support, we developed a two-tier ticketing system that allows us to better manage how we handle remediation requests. When an instructor requests support for an accessibility issue that can be fixed within Ally, a tier-1 ticket is assigned to the instructor’s point of contact, who guides them through the issue. When a file requires more complex work, a tier-2 ticket is assigned to our remediation team. Each tier-2 content item is added to a Box folder, where we can track the amount of time it takes for us to produce an accessible version. This allows us to better approximate our turnaround time when assessing future courses.
“Instead of taking a reactive position, we used the institutional report to help inform our pilot strategy: start small and scale up.”