University Websites

The University of Kentucky utilizes DubBot to identify accessibility issues, broken links and spelling errors across our publicly available websites. DubBot requires public URLs to crawl and cannot be used for internal or authenticated applications.

Visit the UK Digital Platform Oversight and AI DubBot page to learn more about how to use DubBot and access its features.

Learn more about DubBot at UK  

Web accessibility is a shared responsibility that involves collaboration across different roles within a web property. Both content editors and technical staff play important roles in creating an accessible online environment, though they typically address different types of issues.

This guide outlines the specific areas where content editors and technical teams can make the most impact. DubBot supports this process by identifying accessibility issues and helping distinguish which ones can be addressed by content editors and which require technical solutions.

Use DubBot Regularly

• Check your site often for issues and fix them as soon as possible.
  • UKY DubBot

Complete DubBot Video Training Courses

• Learn how to use DubBot effectively by completing courses on identifying and fixing accessibility issues.
  • DubBot Video Learning Center

Add Text for Images and Icons

• Use alt text to describe images and icons so screen readers can explain them to users.
  • WCAG 1.1.1 – Non-text Content

Make Multimedia Accessible

• Provide transcripts for audio-only content.
  • WCAG 1.2.1 – Audio-only and Video-only (Prerecorded)
• Add captions to videos. Include audio descriptions if needed.
  • WCAG 1.2.2 – Captions (Prerecorded)
  • WCAG 1.2.3 – Audio Description or Media Alternative (Prerecorded)

Use Clear Link Text

• Write link text that tells users where the link goes or what it does.
  • WCAG 2.4.4 – Link Purpose (In Context)

Use DubBot to Find Issues

• Look for technical problems and fix them based on priority.
  • UKY DubBot

Familiarize Yourself with WCAG 2.1

• The guidelines include more than criteria; they also provide detailed understanding documents, practical techniques, examples, and testing guidance.
  • WCAG 2.1
  • Understanding WCAG 2.1

Support Keyboard Navigation

• Make sure users can use the site with just a keyboard.
  • WCAG 2.1.1 – Keyboard

Keep Navigation Consistent

• Use the same layout and menu structure across pages.
  • WCAG 3.2.3 – Consistent Navigation

Use High Contrast Colors

• Choose text and background colors that are easy to read.
  • WCAG 1.4.3 – Contrast (Minimum)

Allow Text to Resize

• Make sure users can zoom in up to 200% without breaking the layout.
  • WCAG 1.4.4 – Resize Text

Avoid Flashing Content

• Don’t use flashing elements that could cause seizures.
  • WCAG 2.3.1 – Three Flashes or Below Threshold

Make Forms Accessible

• Label form fields clearly and give instructions for users with assistive tech.
  • WCAG 3.3.2 – Labels or Instructions

Use Consistent Labels

• Use the same labels for elements that do the same thing across the site.
  • WCAG 3.2.4 – Consistent Identification

General Accessibility Inquiries

DubBot Access Request

 DubBot Video Learning Center

Web Content Accessibility Guidelines (WCAG) 2.1