Accessibility

Modified on Mon, 13 Jul at 2:34 PM

Overview

Accessibility helps ensure that UMKC websites can be used by everyone, including individuals who use assistive technologies such as screen readers, keyboard navigation, voice control software, or screen magnification.

DubBot automatically scans your website for common accessibility issues and identifies areas that may require attention. While many issues can be resolved by content editors, others require updates to website templates or custom functionality maintained by Web Services.

This section provides step-by-step guidance for resolving the accessibility issues most commonly reported by DubBot.

Accessibility Issues

The following articles explain how to resolve common accessibility issues reported by DubBot:

Missing Alternative Text
Empty Links
Heading Structure
Link Purpose
Missing Page Titles
Tables
Forms
Color Contrast
HTML and ARIA Issues

Before You Begin

When reviewing accessibility issues, start with those affecting the largest number of pages. Shared content, reusable components, navigation, and page templates can generate issues across an entire website.

Content-related issues, such as alternative text, headings, and descriptive link text, can typically be corrected by website editors.

Code-related issues, including HTML structure, ARIA attributes, keyboard navigation, and some color contrast problems, are generally maintained by Web Services.

Editor vs. Web Services

Website Editors

Editors can typically resolve issues involving:

Alternative text
Heading structure
Link text
Page titles
Documents
General page content

Web Services

Web Services typically resolves issues involving:

Website templates
HTML structure
ARIA attributes
Keyboard accessibility
Form functionality
Tables
Template color contrast
Interactive components

If you encounter an issue that cannot be corrected through your content editor, submit a Web Services support ticket with the affected page and a description of the issue.

Learn More

DubBot identifies many common accessibility issues automatically. However, automated testing cannot detect every accessibility concern.

For additional information about accessibility standards and best practices, visit the UMKC Accessibility resources or the Web Content Accessibility Guidelines (WCAG).