Expect Lots of Messages from CAES and UGA!
In October 2025 UGA’s EITS and EOO offices finalized a university-wide Digital Accessibility Policy and began communicating about efforts to meet the upcoming compliance deadline. With that deadline approaching, you’ll likely see a lot of messages about digital accessibility from both UGA and CAES.
For the most part, what you hear from UGA will align with what CAES OIT has already been sharing — we’ve been preparing for accessibility compliance for quite some time. However, there is one key difference in how CAES will meet the university’s accessibility requirements. This article clarifies that distinction.
Key Difference: CAES will Use DubBot, Not “Ally for Web”
If you manage a CAES website, your focus in the coming months will be to ensure your web content meets accessibility standards. While UGA’s communications will reference “Ally for Web” — a tool that generates accessibility reports — CAES will not use this product. Instead, CAES uses DubBot, a similar tool that provides reports and helps track website accessibility progress.
CAES web content owners should follow messages about DubBot and may disregard messages about Ally for Web.
Ashley Thompson is the liaison for all web accessibility questions. You’ll be hearing more from her soon — reach out if you have questions or concerns.
“Ally for eLC” and Other Accessibility Messaging Still Apply
If you are a faculty member creating digital course materials in eLC, you will use Ally for eLC, the accessibility tool built into UGA’s eLearning Commons system.
Christy Rich is the liaison for all eLC accessibility questions. You’ll be hearing more from her as well — don’t hesitate to reach out with questions.
Summary
- CAES websites → use DubBot, not Ally for Web
- eLC courses → use Ally for eLC
- Watch for more guidance from Ashley Thompson (web) and Christy Rich (eLC)
