6.2 On each screen, interface elements must not be used only for layout purposes. Is this rule respected?

Test 1 (6.2)

This criterion only checks elements that should not be interactive (text elements, tables for example).

iOS with VoiceOver

1. Activate the screen reader and browse all the elements on the screen.
2. Check that the role rendered by the screen reader corresponds to the nature of the element (for example, when the screen reader reaches what appears to be a paragraph and renders "Button", this is an error, no role is rendered for the paragraphs).
3. If this is the case, the criterion is validated.

iOS With Accessibility Inspector

1. Connect the iOS mobile device to the computer running macOS.
2. Activate the Accessibility Inspector software.
3. Choose the mobile device as the source and stay on the "Inspection" tab (buttons at top right).
4. Use the arrows in Accessibility Inspector to access each element of the interface.
5. Check that the role available in the "Traits" parameter is relevant to the nature of the associated element (for example, simple text acting as a button would be considered non-compliant and should be identified as static text).
6. If this is the case, the criterion is validated.

Android

1. Activate the screen reader and browse all the elements on the screen.
2. Check that the role rendered by the screen reader corresponds to the nature of the element (for example, when the screen reader reaches what appears to be a paragraph and returns "Button", this is an error - no role is rendered for the paragraphs).
3. If this is the case, the criterion is validated.