Success Criterion 1.3.2 - Meaningful Sequence - Level A

[JJdeGroot]

Discussion:

MATF meeting on June 26, 2024

[Source](https://www.w3.org/2024/06/26-matf-minutes.html#t04) JJ: Focus should follow a specific order to understand the screen properly. Mobile platforms allow us to modify focus order. julianmka: We have worked with teams where we modify the focus order, but try not to and achieve it by grouping etc. julianmka: MATF could provide supplementary documentation about mobile-specific techniques like grouping Joe_Humbert: Similar experience as Julian. Reading/focus order on mobile blend together a bit. Using Accessibility elements on iOS can be problematic with dynamically loading content. JJ: Same experience with accessibility element in iOS. Android lets you set traversal order. Aashutosh: Success story: Worked on app where home screen focus order was modified. Aashutosh: Designers should indicate the intended sequence so that developers don't have to infer it. +1 to that, Aashutosh yes +1 +1 to Aashutosh JJ: Android floating action button (FAB) could be a good use case for manipulating focus order Illai: MCAG project recommends grouping to help ensure meaningful sequence.

Summary:

1. Importance of Focus Order:

   • JJ: Emphasized that focus should follow a specific order to ensure users can properly understand the screen. Mentioned that mobile platforms allow modifications of focus order.

2. Experiences with Focus Order:

   • Julian: Shared that their team tries not to modify focus order directly, instead achieving the desired sequence by grouping elements.
   • Joe Humbert: Echoed Julian's experience, noting that reading and focus order tend to blend together on mobile. Highlighted issues with using Accessibility elements on iOS with dynamically loading content.
   • JJ: Confirmed similar issues with iOS and noted that Android sets traversal order differently.
   • Aashutosh: Shared a success story where their team modified the focus order on a home screen.

3. Recommendations:

   • Aashutosh: Stressed that designers should indicate the intended focus sequence to avoid developers having to infer it.
   • Joe Humbert and Jamie: Agreed with Aashutosh's recommendation.

4. Use Cases and Techniques:

   • JJ: Suggested that the Android floating action button (FAB) could serve as a good use case for manipulating focus order.
   • Illai: Mentioned that the MCAG project recommends grouping to ensure a meaningful sequence.

[gert-janvercauteren]

We probably want to keep 'reading order' (1.3.2) and 'focus order' (2.4.3) separate for mobile, even though we feel they are somewhat similar there is a difference once you start navigating by keyboard on iOS and elements receive focus.

As mentioned, the MCAG guidelines from Evinced make this distinction and reference two different WCAG criterion

• https://getevinced.github.io/mcag/#logical-reading-sequence (WCAG 1.3.2)
• https://getevinced.github.io/mcag/#logical-focus-sequence (WCAG 2.4.3)

Regardless of which platform our designers create designs for, we ask them to mark up both reading and focus order on components with different markup styles.

[illai]

@gert-janvercauteren I also think we should keep them separate since these are different mechanisms and browsing modes that responsible to each of them, and each of them impact different users on different ways.