Usability issues backend/frontend

  • georg03

    (@georgdem)


    6 months ago

    Hello,

    thanks for creating a block based mega menu! I use this plugin in a couple of projects together with WP default themes Twenty Twenty-Five and Twenty Twenty-For and want to address some usability issues in front and backend.

    1. When creating a menu in FSE editor in a Header template part the dropdown/submenu is usually not visible when you click on a Menu Item. You have to scroll to view all items. The desired behaviour would be to see the whole submenu as shown in the WP plugin “Sreenshots” section.
    2. When you click on a Plain Menu item placed in a submenu it actually links within the Header Template to the linked page. I then see the frontend of the website within the Header Template which is apparently a bug. When I want to go back I get an error message and need to exit and re-enter the FSE editor.
    3. It would be nice to add also a menu-is-open class to body in order to make it non-scrollable when opening the menu.
    4. Currently the menu is not WCAG compatible, there are no aria attributes and you can not navigate through keyboard with TAB, Enter/Space, ESC.

    Thanks,
    Georg

Viewing 1 replies (of 1 total)
  • Plugin Support Eugene White

    (@eugenewhite)

    5 months, 3 weeks ago

    Hello, Georg, 

    Thank you for your feedback. We appreciate it. 

    I’ve already escalated it to our developers, but would also like to comment on the usability issues you mentioned: 

    1. I understand that working with a mega menu in the header template part can be challenging due to its limited height. However, the content area (height) of the header template part adjusts in height automatically depending on the size of the block you add. I realize you would like the height to match both the mega menu plus the dropdown menu, but I’m uncertain if that’s achievable or if the issue originates from our plugin. Nevertheless, we’ll explore potential solutions. In the meantime, as a workaround, I suggest adding a Section block first (provided by the Getwid plugin). You can set your preferred height for this section and then add your Mega Menu block within it. Once you have created or edited your mega menu, you can copy it, remove the section with your mega menu, and then paste it into the header.

    2. You’re correct that the link added to the Plain Menu block is clickable. However, the menu item itself is not clickable, and when you click the page link, it opens in a new browser tab instead of the same tab. Therefore, you don’t need to open FSE to edit your template part since it remains open. It’s possible that your browser settings are configured to open such links in the same tab. Regardless, I have escalated this issue to our developers, and they will look into what can be done about the link.

    3. Thank you. We’ll keep this in mind for future plugin releases. 

    4. We don’t position our Mega Menu plugin/block as WCAG-compatible. But will also keep this in mind for future plugin releases if we receive more similar questions or feedback from other customers. Thanks! 

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.