Definition of "navigational mechanisms" in mobile context

w3c / matf

Guidance from the Mobile Accessibility Task Force (MATF)

https://w3c.github.io/matf/

Other

8 stars 3 forks source link

Definition of "navigational mechanisms" in mobile context #71

Open JJdeGroot opened 1 month ago

JJdeGroot commented 1 month ago

In our meeting on October 16, 2024, the definition of navigational mechanisms came up.

We need to consider what would be considered navigation mechanisms in the context of mobile applications.

Success Criterion 2.3.2:

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

detlevhfischer commented 1 month ago

I think a positive list would include:

Icon and icon/label tab bars at the bottom of the display
Navigation elements in the header (back button, more menu, home icon etc()
Lists of targets poiting to other views brought into view in side sheets or bottom sheets after activating a control (most frequently icons: more icon, hamburger icon, cog icon
dedicated step navigation like next and previous in processes (e.g., onboarding sequences)
links in a footer that is repeated on most / many views in the same way, with links often pointing to stuff outside the app context (terms and conditions, technical documentation in web sites, etc.)

Individual inline links of varying function buttons in the content area I would generally not see as navigational mechanism.

julianmka commented 1 month ago

Would we consider the global system-level back gesture/button in Android a navigational mechanism? Devs do have the ability to change what it does, and I've encountered many apps ignore it altogether in favor of whatever custom controls they have instead.

detlevhfischer commented 1 month ago

@julianmka Since WCAG (and by implication, the guidance we develop here) is focused on the content authored, i.e., the stuff for which designers / developers are directly responsible, I wouldn't think global gestures or keystrokes without representation in the app's interface would generally be included. But it gets tricky when they are hijacked and mapped to something else, of course... at that point the mechanism is owned by the author, and 2.3.2 would then apply, I guess.