WCAG 2.2 Robust

Question 1

4.

Answer 1

4. Robust
   Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
   - 4.1 Compatible
   – 4.1.1 removed in 2.2 version
   - (1A, 1AA)

Question 2

4.1 Compatible

Answer 2

4.1 Compatible
Maximize compatibility with current and future user agents, including assistive technologies.

Question 3

4.1.1 Parsing (Obsolete and removed)

Answer 3

4.1.1 Parsing (Obsolete and removed)

This criterion was originally adopted to address problems that assistive technology had directly parsing HTML. Assistive technology no longer has any need to directly parse HTML. Consequently, these problems either no longer exist or are addressed by other criteria. This criterion no longer has utility and is removed.

Question 4

4.1.2

Answer 4

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.

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.

Question 5

4.1.3

Answer 5

4.1.3 Status Messages (Level AA)
In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.