provided to the user, unless it would jeopardize the security or purpose of the content. 11.2.1.36 Error prevention (legal, financial, data) Supported Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.36: Error prevention (legal, financial, data): For software that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. 11.2.1.37 Parsing Supported Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.37: Parsing: For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, 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. 11.2.1.38 Name, role, value Supported With The following items are Exceptions not supported via screen Where ICT is non-web software that provides a user reader: creating interface and that supports access to any assistive relationships, adding technologies, it shall satisfy the Success Criterion in Table images, changing slicer 11.38: Name, role, value: state, switching page For all user interface components (including but not view, switching number limited to: form elements, links and components generated formatting and creating by scripts), the name and role can be programmatically measures determined; states, properties, and values that can be set by the user can be programmatically set; and notification
provided to the user, unless it would jeopardize the security or purpose of the content. 11.2.1.36 Error prevention (legal, financial, data) Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.36: Error prevention (legal, financial, data): For software that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. Supported 11.2.1.37 Parsing Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.37: Parsing: For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, 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 11.2.1.38 Name, role, value Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.38: 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 determined; states, properties, and values that can be set by the user can be programmatically set; and notification Supported With Exceptions The following items are not supported via screen reader: creating relationships, adding images, changing slicer state, switching page view, switching number formatting and creating measures
Power%20BI%20Desktop.Win32.EN_102417.DOCX