In practice, this criterion no longer provides any benefit to people with disabilities in itself. Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different Success Criteria and should be reported under those criteria rather than as issues with 4.1.1. Understanding 4.1.1 Show Hide techniques and failures for 4.1.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 4.1.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G134: Validating Web pages G192: Fully conforming to specifications H88: Using HTML according to spec Ensuring that Web pages can be parsed by using one of the following techniques: H74: Ensuring that opening and closing tags are used according to specification AND H93: Ensuring that id attributes are unique on a Web page AND H94: Ensuring that elements do not contain duplicate attributes H75: Ensuring that Web pages are well-formed Failures for Success Criterion 4.1.1 F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID Back to top 4.1.2 Name, Role, Value Level A 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.