You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no consensus on how to deal with a bottom navigation bar, but the people I test my software with are all okay with that taking focus precedence over the rest of the page, even though visually it comes "last". They say things like "yes, but a lot of apps have such a navigation so it's okay". My advice here is not leading and there is no WCAGuideline I can link to help here. You are just going to have to make a choice and defend it or be willing to adapt based on real-user-feedback.
The bottom navigation bar currently sits at the end of the focus order. I think this should move to the front, and in fact, that's how I always implement it on the products I work on. You don't want to have to scroll through the feed to get to the navigation.
Attachments
Breakpoint
Focus Order
Desktop
Small laptop / Tablet
Mobile
What platform(s) does this occur on?
Web (Desktop), Web (Mobile)
Device Info
Not Relevant
What version of the app are you using?
Web
Additional Information
Okay so on Twitter this is partially mitigated because the Focus order isn't broken and goes from left (menu) to feed to right sidebar. However, I need to hold j to get to the bottom of the loaded posts followed by tab to get to the sidebar before the next batch loads. So it's not optimal. When browsing with a mobile user agent, there is a bottom navigation bar that comes first in the focus order, which fixes it.
LinkedIn has the same challenge as Twitter, but again the menu is in focus order so it's not that much of a problem as the right sidebar is mostly useless there. They also have skip links at the top, which is how this should work.
The text was updated successfully, but these errors were encountered:
Steps to Reproduce
There are several issues here:
jk
navigation for example).Solving the focus order solves part of it as the right sidebar on bluesky, just like on Twitter and LinkedIn is mostly useless.
This is related to #6369 and the technique for skipping is the same.
You probably want several skip links, understanding bypass blocks. Usually these links are added to skip the navigation to main content, which is probably what you want here as well, and you can add a second one to skip the feed to get to the right sidebar.
Caution
There is no consensus on how to deal with a bottom navigation bar, but the people I test my software with are all okay with that taking focus precedence over the rest of the page, even though visually it comes "last". They say things like "yes, but a lot of apps have such a navigation so it's okay". My advice here is not leading and there is no WCAGuideline I can link to help here. You are just going to have to make a choice and defend it or be willing to adapt based on real-user-feedback.
The bottom navigation bar currently sits at the end of the focus order. I think this should move to the front, and in fact, that's how I always implement it on the products I work on. You don't want to have to scroll through the feed to get to the navigation.
Attachments
What platform(s) does this occur on?
Web (Desktop), Web (Mobile)
Device Info
Not Relevant
What version of the app are you using?
Web
Additional Information
Okay so on Twitter this is partially mitigated because the Focus order isn't broken and goes from left (menu) to feed to right sidebar. However, I need to hold
j
to get to the bottom of the loaded posts followed bytab
to get to the sidebar before the next batch loads. So it's not optimal. When browsing with a mobile user agent, there is a bottom navigation bar that comes first in the focus order, which fixes it.LinkedIn has the same challenge as Twitter, but again the menu is in focus order so it's not that much of a problem as the right sidebar is mostly useless there. They also have skip links at the top, which is how this should work.
The text was updated successfully, but these errors were encountered: