Accessibility: 1.3.1 Info and Relationships, 4.1.2 Name, Role, Value
# 1.3.1 Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
Link to documentation: https://www.ibm.com/able/guidelines/ci162/name_role_value.html
# 4.1.2 Name, Role, Value
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Note: This success criterion is primarily for authors who develop or script their own user interface components. Standard HTML controls already meet this success criterion when used according to specification.
Link to documentation: https://www.w3.org/TR/WCAG20/#text-equiv-all
Link to how to meet these standards: https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#qr-text-equiv-all
epic