12.3 The application does not interfere with the accessibility features of the platform. Is this rule respected?

Test 1 (12.3)

iOS

1. Identify the accessibility features made available to users in the platform documentation (see the documentation concerning the accessibility features provided by iOS.
2. Check that the application does not prevent their use, for example
   • if the application implements interactions that trigger features, these interactions do not prevent the platform's accessibility features such as the screen reader or other touch-based features from working properly;
   • if the application includes voice recognition, then the use of the voice command integrated into the platform is not disrupted;
   • if the application implements keyboard shortcuts, these do not use key combinations already employed by the platform for accessibility features (VoiceOver can be used with a keyboard for example, the proposed shortcuts must not interfere);
   • or any other application functionality.
3. If this is the case, the criterion is validated.

Android

1. Identify the accessibility features made available to users in the platform documentation (see the documentation concerning accessibility features provided by Android).
2. Check that the application does not prevent their use, for example
   • if the application implements interactions that trigger features, these interactions do not prevent the platform's accessibility features, such as the screen reader or other touch-based features, from working properly;
   • if the application includes voice recognition, then the use of the voice command integrated into the platform is not disrupted;
   • if the application implements keyboard shortcuts, these do not use key combinations already employed by the platform for accessibility features (TalkBack can be used with a keyboard for example, the proposed shortcuts must not interfere);
   • or any other application functionality.
3. If this is the case, the criterion is validated.