Understanding HTML & ARIA Issues

What are HTML and ARIA issues?

HTML provides the structure of a webpage, while ARIA (Accessible Rich Internet Applications) provides additional information that helps assistive technologies understand interactive content.

DubBot may report HTML or ARIA issues when it detects code that could affect accessibility or the way assistive technologies interpret a page.

Unlike many accessibility issues, these findings are often related to website templates, components, or custom applications rather than page content.

Common issues

DubBot may report issues such as:

• Duplicate element IDs
• Missing ARIA labels
• Invalid ARIA attributes
• Missing landmarks
• Incorrect HTML structure
• Interactive elements that are not fully accessible

These issues generally require updates to website code rather than changes to page content.

Can I fix this issue?

In most cases, no.

Content editors typically do not have access to the underlying HTML or template code that generated the issue.

If the issue appears within your editable page content and you are comfortable working with HTML, you may be able to correct it. Otherwise, the issue should be referred to Web Services.

When to contact Web Services

Submit a Web Services support ticket if DubBot reports an HTML or ARIA issue that cannot be resolved through your CMS.

Include:

• The affected page URL.
• The DubBot issue description.
• A screenshot of the report, if available.

This information helps Web Services identify whether the issue originates from a shared template, reusable component, or custom functionality.

Why does DubBot report these issues?

Many HTML and ARIA issues cannot be detected through visual review alone. They primarily affect visitors who rely on screen readers, keyboard navigation, or other assistive technologies.

Identifying and correcting these issues helps improve the accessibility and usability of UMKC websites.

Verify the correction

Once Web Services has implemented a correction:

1. Verify the updated page has been published.
2. Wait for DubBot’s next scheduled crawl.
3. Confirm the reported issue no longer appears.