ARIA role inside widget element

Compliance Data & User Impact

User Impact: Major

60% Complete

Disabilities Affected:

  • blindness
  • deafblindness
  • vision impairments

WCAG Version:
2

WCAG Levels:

  • A

WCAG Guidelines:

Solution Techniques:

Automated Test Accuracy:
Medium

uTester Severity:
2

DRRSAG Designations:

  • role

How to Fix the Problem

The characteristics of user interface components should be described by the role attribute. Interactive elements cannot contain elements with another role.

The Algorithm, in Simple Terms

The engine looks for elements which have a role attribute different from “presentation“ and “none“ and checks if they are a child of either of these: <a href>, <button>,<role=link>,<role=button>,<role=checkbox>,<role=menuitem>,<role=menuitemcheckbox>,<role=menuitemradio>,<role=option>,<role=radio>,<role=searchbox>,<role=slider>,<role=spinbutton>,<role=switch>,<role=tab>,<role=textbox>,<role=treeitem>

Why Is it Important?

Exposing the roles correctly enables users to understand widgets and how to interact with it.

Address: 401 9th St NW, 6th Floor
Washington, DC 20004
Phone number: (888) 995-WCAG
International number: 1(888) 995-9224
Email: accessibility@user1st.com