• Resolved toad78

    (@toad78)


    I’m receiving a report that the mega menu code does not allow for keyboard control with the use of the arrow keys, Enter/Space for selection of menu/submenu items, and the use of the ESC key to leave the submenu items.

    I didn’t see any settings regarding this possible functionality. I did not see anything in regards to WCAG or settings in the plugin’s documentation either.

    I really like the plugin, but I need this to work for WCAG.

    Putting it out there:
    General Settings > Click Event Behavior = First click will open a sub menu, second click will follow the link. However, this doesn’t seem to be working either. I can hover over a parent menu item and the submenu appears instead of “onclick”.

    So is it possible to make this WCAG compliant with the use of keyboard control?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author megamenu

    (@megamenu)

    Hi toad78,

    Whist we make no official claims to be WCAG compliant (that’s too risky, as there are conflicting opinions on how menu accessibility should be implemented), you should find that if you “tab” to the menu then you can navigate through it:

    TAB activates keyboard navigation and navigates through the menu
    ENTER on a parent item opens a sub menu (pressing ENTER a second time will respect the “Second Click Behaviour” setting)
    ENTER on a standard item will follow the link
    SPACE toggles the sub menu visibility
    ESC closes all open sub menus
    LEFT/RIGHT ARROW selects the previous/next top level item

    Please note that at this point I do not plan on changing the current keyboard behaviour (this behaviour has been ‘signed off’ by a couple of accessibility audits in the past).

    Regards,
    Tom

    Thread Starter toad78

    (@toad78)

    Thank you for the clarification, Tom.

    I’ll run another test.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WCAG Issue: Keyboard Function’ is closed to new replies.