PRINCIPLE 4: ROBUST Flashcards
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
GUIDELINE 4.1
COMPATIBLE
Maximise compatibility with current and future user agents, including assistive technologies
SUCCESS CRITERION 4.1.1
PARSING (A)
In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
SUCCESS CRITERION 4.1.2
NAME, ROLE, VALUE (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.
SUCCESS CRITERION 4.1.3
STATUS MESSAGES (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.