ARIA Attributes Check

ARIA (Accessible Rich Internet Applications) is a set of HTML attributes that describe custom widgets — menus, tabs, dialogs, toggles — to screen readers. Used correctly it makes complex interfaces usable; used incorrectly it actively breaks them. VitalSite checks your ARIA with axe-core, mapped to WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

What VitalSite checks

• Valid roles and attributes. Misspelled roles, invalid attribute values, and ARIA attributes on elements that do not support them.
• Required attributes. Widgets that declare a role but are missing the attributes that role requires (for example a checkbox role without aria-checked).
• Broken references. aria-labelledby or aria-describedby pointing at IDs that do not exist.

Why it matters

The first rule of ARIA is: do not use ARIA if a native HTML element will do. Broken or misused ARIA is worse than none — it tells a screen reader something false about your interface, leaving users stuck. Getting it right is what makes custom components accessible.

How to fix it

• Prefer native elements. Use <button>, <a>, <input> and <label> before reaching for ARIA — they are accessible by default.
• Complete the pattern. If you use a role, add every attribute that role requires and keep its state updated (for example toggle aria-expanded on a menu).
• Fix references. Make sure every aria-labelledby / aria-describedby points at an element that exists on the page.

Verify the fix

Re-scan your domain. The ARIA check should report no invalid roles, missing required attributes, or broken references.

Run a free full-domain scan to see whether this affects your site — every page, with an exact fix guide. Pro and Agency plans add PDF export and monitoring.