provided to the user, unless it would jeopardize the security or purpose of the content. 3.3.4 Error Prevention (Legal, Supported Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete data in data storage systems, or that submit user test responses, at least one of the following is true: 1. Reversible: Submissions are reversible. 2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. 3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. Principle 4: Robust Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. Guideline 4.1 Compatible Maximize compatibility with current and future user agents, including assistive technologies. Criteria Supporting Feature Remarks and Explanations 4.1.1 Parsing: In content Supported 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. 4.1.2 Name, Role, Value: For all Supported user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically
provided to the user, unless it would jeopardize the security or purpose of the content. 3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete data in data storage systems, or that submit user test responses, at least one of the following is true: 1. Reversible: Submissions are reversible. 2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. 3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. Supported Principle 4: Robust Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. Guideline 4.1 Compatible Maximize compatibility with current and future user agents, including assistive technologies. Criteria Supporting Feature Remarks and Explanations 4.1.1 Parsing: 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. Supported 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 Supported
Intune%20Android%20Company%20Portal.Android.WCAG_082417.DOCX