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
On our sites that use mobile navigation, the tabbing gets screwy. The ideal behavior is
a user can tab through relevant elements based on focus styles visually guiding them
there are no redundant repeats of source code in the markup that require blind users to hear things twice
Our mobile nav component clones elements from the primary and utility nav. This is fine. We just need to ensure that all buttons and anchors in our .mobile and .subMenuClass elements have a tabindex="-1".
The text was updated successfully, but these errors were encountered:
On our sites that use mobile navigation, the tabbing gets screwy. The ideal behavior is
Our mobile nav component clones elements from the primary and utility nav. This is fine. We just need to ensure that all buttons and anchors in our .mobile and .subMenuClass elements have a tabindex="-1".
The text was updated successfully, but these errors were encountered: