Name, Role, Value

Understanding WCAG2.0

Elements to be operated by the user need to be interpreted by the program if they have names, roles and values. When describing elements as usual in HTML, this is rarely a problem. However, even if you are describing HTML as usual, it is important to note that if span etc. receives focus and implements such as JavaScript that causes some change in content.

Principle Robust Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guideline Compatible Maximize compatibility with current and future user agents, including assistive technologies.
Criterion Name, Role, Value
(4.1.2 A)
For all user interface components (elements that make up the form, links, script-generated components, etc.), names and roles can be interpreted programmatically. In addition, the status, properties, and values that can be set by the user can be set by the program. Then, user agents including assistive technology can use change notifications for these items.

URL of Techniques for WCAG 2.0