Burger menu

• Par Travis, le 10 October 2023 at 17h44.

  Ce commentaire a été publié il y a plus de 2 ans. Il se peut que son contenu ne soit plus d'actualité.

  

  Thanks for creating these guidelines, they’re a great reference.

  There’s several details you don’t mention here that I’m unsure about:

  – When Esc is pressed to close the menu, should you not set the focus back to the menu button?
  – When the menu is open, shouldn’t it be treated as a modal, where keyboard navigation will be restricted to only the menu?

  Répondre

  • Par Romain Desjardins (Atalan), le 16 October 2023 at 3h19.

    Ce commentaire a été publié il y a plus de 2 ans. Il se peut que son contenu ne soit plus d'actualité.

    

    Hello Travis,

    Thank you for your message!

    Concerning the Esc shortcut, I believe that the answer to your question is in the “Keyboard interactions” of the guidelines: If the keyboard focus is positioned on one of the menu items, Esc moves the keyboard focus to the hamburger button that triggered the menu display, and then closes it.

    Concerning the modal behavior, it will depend on the visual menu opening: if it prevents user from accessing the rest of the page content (the menu opening takes all the screen for example), it could be considered as a modal. If not, a simple disclosure button can make it, without keyboard navigation restriction.

    I hope this is clearer for you.

    Have a good day,
    Romain

    Répondre

• Par Steffi, le 4 August 2023 at 11h54.

  Ce commentaire a été publié il y a plus de 2 ans. Il se peut que son contenu ne soit plus d'actualité.

  

  According to W3C Recommendations the adding of role=”navigation” is allowed, but not recommended. See: https://www.w3.org/TR/html-aria/#el-nav

  Répondre

  • Par Romain Desjardins (Atalan), le 7 August 2023 at 8h30.

    Ce commentaire a été publié il y a plus de 2 ans. Il se peut que son contenu ne soit plus d'actualité.

    

    Hello Steffi,

    Thank you for your comment.

    The information is a duplicate of the nav tag to ensure a correct restitution by the screen readers. The W3C says it is not recommended, because it follows the first ARIA rule.
    But in this case, there are only benefits to adding this role.
    The goal here is to make the information accessible to the largest number of users, especially those who do not have access to the latest versions of screen readers, which may not render the information without this attribute.

    Adding the role=”navigation” (and other landmark tags) is also to be compliant with French accessibility standards (RGAA).

    Regards,

    Romain

    Répondre

• Par Engineer Hamziey, le 16 August 2022 at 20h57.

  Ce commentaire a été publié il y a plus de 2 ans. Il se peut que son contenu ne soit plus d'actualité.

  

  Do we still need to put `role=”navigation”` in the since it’s nag tag and it’s not just a div tag

  Répondre

  • Par Romain Desjardins (Atalan), le 17 August 2022 at 10h00.

    Ce commentaire a été publié il y a plus de 2 ans. Il se peut que son contenu ne soit plus d'actualité.

    

    Hello,

    Thank you for your message.

    I confirm that the role="navigation" attribute is still needed here.

    The information is duplicated to ensure a correct restitution by the screen readers.

    The goal here is to make the information accessible to the largest number of users, especially those who do not have access to the latest versions of screen readers, which may not render the information without this attribute.

    Regards,

    Romain

    Répondre

Leave a Reply