Consequently, these problems either no longer exist or are addressed by other criteria. This criterion no longer has utility and is removed. Success Criterion 4.1.2 Name, Role, Value Understanding Name, Role, Value | How to Meet 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 . Note This success criterion is primarily for Web authors who develop or script their own
      user interface components. For example, standard HTML controls already meet this success
      criterion when used according to specification.