11.2.1.22 Focus order Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.22: Focus order: If software can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. Supported With Exceptions In the Edge browser, the visual focus indicator is not visible in "Choose Environment" combo box. 11.2.1.23 Link purpose (in context) Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.23: Link purpose (in context): The purpose of each link can be determined from the link text or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. Supported 11.2.1.25 Headings and labels Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.25: Headings and labels: Headings and labels describe topic or purpose. Supported 11.2.1.26 Focus visible Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in 11.26: Focus visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. Supported With Exceptions The comments section in the Blog comments does not show 11.2.1.27 Language of software Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.27: Language of software: The default human language of software can be programmatically determined. Supported 11.2.1.29 On focus Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.29: On focus: Supported
When any component receives focus, it does not initiate a change of context. 11.2.1.30 On input Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.30: On input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. Supported 11.2.1.33 Error identification Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.33: Error identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. Supported With Exceptions There are issues that causes two error messages - invalid input for a Recurrence action, and with Windows Narrator - to not to be read immediately. 11.2.1.34 Labels or instructions Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.34: Labels or instructions: Labels or instructions are provided when content requires user input. Supported 11.2.1.35 Error suggestion Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.35: Error suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. Supported 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 Supported