Title: [Accessibility] AXE Devtools Issue
Last modified: January 15, 2025

---

# [Accessibility] AXE Devtools Issue

 *  Resolved [Karan Thakur](https://wordpress.org/support/users/karanperformedia/)
 * (@karanperformedia)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/accessibility-axe-devtools-issue/)
 * Hi,
 * We love your plugin and admire how accessible it is than any other menu plugin
   on WordPress, when doing an audit we found an issue that we hope with help with
   the plugin being more accessible.
 * The issue is that aria-expanded is not allowed on <a> tags without an explicit
   role. We think using <button> should remove this issue. Attaching a screenshot
   of the AXE Devtools report and MDN reference for aria-expanded.
 * MDN:- [https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-expanded](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-expanded)
 * [https://www.imghost.net/zj9sdaxbubrWD4x](https://www.imghost.net/zj9sdaxbubrWD4x)

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

 *  Plugin Author [megamenu](https://wordpress.org/support/users/megamenu/)
 * (@megamenu)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/accessibility-axe-devtools-issue/#post-18249364)
 * 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/](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](https://wordpress.org/support/users/karanperformedia/)
 * (@karanperformedia)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/accessibility-axe-devtools-issue/#post-18249679)
 * 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.

 * ![](https://ps.w.org/megamenu/assets/icon-128x128.png?rev=1489843)
 * [Max Mega Menu](https://wordpress.org/plugins/megamenu/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/megamenu/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/megamenu/)
 * [Active Topics](https://wordpress.org/support/plugin/megamenu/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/megamenu/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/megamenu/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Karan Thakur](https://wordpress.org/support/users/karanperformedia/)
 * Last activity: [1 year, 4 months ago](https://wordpress.org/support/topic/accessibility-axe-devtools-issue/#post-18249679)
 * Status: resolved