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. 11.2.1.33 Error identification 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 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 ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.35: Error suggestion: If an 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 With Exceptions Microsoft Office exposes the details of document structure and formatting in files per published document format specifications. Where supported, Word for iOS also exposes such information programmatically to platform accessibility APIs. Some document structure or formatting, including heading names, names of styles applied to text, inline images, auto correction actions, and movement of shapes, may not be recognized or reported by currently
selection attributes of user interface elements where the user can modify these items. 11.3.2.15 Change notification Where software provides a user interface it shall, by using the services as described in 11.3.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.3.2.5 to 11.3.2.11 and 11.3.2.13. Supported 11.3.2.16 Modifications of states and properties When permitted by security requirements, software that provides a user interface by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items. Supported 11.3.2.17 Modifications of values and text When permitted by security requirements, software that provides a user interface shall, by using the services as described in 11.3.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology. Supported 11.4.1 User control of accessibility features Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users. Not Applicable 11.4.2 No disruption of accessibility features Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software. Supported With Exceptions On/Off switches in Office apps for iOS use a custom control that does not follow the 'On/Off Labels' accessibility setting 11.5 User preferences Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms. Supported With Exceptions On/Off switches in Office apps for iOS use a custom control that does not follow the 'On/Off Labels' accessibility setting 11.6.2 Accessible content creation Supported