[Accessibility] AXE Devtools Issue

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

    (@megamenu)

    1 year, 4 months ago

    Hi Karan,

    Thanks. I’ll need to look into this, maybe the anchors need a role of button applied (it’s tricky, because they don’t strictly act as a button, the first click opens the sub menu (like a button) but the second click follows the link (like an anchor)).

    You can enable the “Disable Link” option for your parent items, and they will automatically change to a button.

    Interestingly, in this case, the w3 example of a flyout menu is incorrect, as they use aria-expanded on the top level anchors:

    https://www.w3.org/WAI/tutorials/menus/flyout/

    I’ll take a closer look when I have some time. Thanks for the heads up.

    Regards,
    Tom

    Thread Starter Karan Thakur

    (@karanperformedia)

    1 year, 4 months ago

    Hi Tom,

    Thank you very much! The “disable link” option worked effectively, and AXE no longer reports it as an issue. You’re right about the W3 example as well. I’ll notify them so they can update it.

    Thanks again!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘[Accessibility] AXE Devtools Issue’ is closed to new replies.