Success Criterion 3.2.3 - Consistent Navigation - Level AA

[JJdeGroot]

WCAG2ICT guidance: https://www.w3.org/TR/wcag2ict-22/#consistent-navigation

Share your thoughts for applying to mobile apps as a comment below.

[JJdeGroot]

Discussed in yesterday's meeting. Will be on agenda again next week.

9 October 2024

Source

JJ: WCAG2ICT added a note that while not required SC should be considered best practice
… relates to the problematc definition to "set of software programs" (rather than "set of views")

JJ: In the EN 301 549 it is also considered to change to sets within software

Jamie: If we have a note, the way it is written does not clearly stating the purpose
… seems confusing right now - we should not use the same wording

JJ: if we can view or screen it will be clearer

JJ: We might need an exception because there may be valid reasons to deviate in terms of order
… need ti figure out if exception is needed - may not be needed since note is not normative

JJ: we may also discuss consistent help - applies more to web sites

JJ: will send out minutes after the meeting

[JJdeGroot]

• Reconsidering WCAG-based software requirements omitted from EN 301 549 v.3.2.1
• EN 301 549 discussion for 3.2.3 Consistent Navigation

Most recent proposal:

Navigational mechanisms that are repeated within a software program occur in the same relative order each time they are repeated, unless a change is initiated by the user or where not doing so is essential to the function of the software.

This replaces "set of web pages" with "a software program"
I proposed to add: "except where not doing so is essential to the function of the software." to add the same exception that was accepted for 3.2.4 Consistent Identification

I think we should phrase our guidance similarly, ideally with "views" or "screens". Or we could phrase it as "a mobile application" to apply it to all content contained in the application.

[JJdeGroot]

Discussed in today’s meeting.

16 October 2024

Source

JJ - WCAG2ICT replaces "set of web pages" with "a software program"

JJ - correction - EN 301 549 replaces "set of web pages" with "a software program"

JJ - This mostly related to how we replace "set of web pages".

<JJ> Mick: in our group we would look at a relatively small set of components for consistent navigations, such as search buttons?

JJ - I would consider a back button, close button, buttons in a list, a change of tab in a tab bar.

Aash - should we introduce certain things - the bottom sheets without the close button. Very hard to dismiss those overlays.

JJ - I think it would be interesting to add such things in a Note. That might be more related to Keyboard Operation rather than this success criterion

JJ - I wonder would a back button or close button placed differently would fail this criteria in app or is it too strict. Is it more about large lists of links rather than a single link/button.

JJ - Does 'navigational mechanisms' related to one button or link

Jamie - this criteria isn't about where the back button is on every app

ACTION: Define "navigational mechanisms"

Jamie - what are we considering navigational mechanisms? It would be helpful outlining examples.

JJ - this is specific to a single app.

ACTION: Define "navigational mechanisms" = #71