1. Feedback
  2. Blazor
  3. 46517

Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Dropdown Menu accessibility - Popup inserted at bottom of page, affecting reading order

Hello,

When using the Dropdown Menu component, I noticed that the HTML code for the popup menu that opens after clicking the DropdownButton is inserted at the end of the web page before the end of the </body> element. I am referring to the popup container that has the class of "e-dropdown-popup".

Visually, the menu appears near the DropdownButton that triggers it, but since the popup HTML is inserted at the bottom of the page, the reading order which screen readers use does not match. This can be tested by using a screen reader in browse/read mode. It can also be tested by disabling CSS stylesheets on a page and opening the Dropdown Menu, where the menu will instead appear after all other page content.


A menu that does not appear next to it's trigger affects its meaning when read, and therefore would be an issue under WCAG 1.3.2:

https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence

If possible, I would recommend placing the popup HTML immediately after it's trigger (DropdownButton). That way, a screen reader user can read the button and menu in the same order that sighted users have via the CSS positioning.

Let me know if you need more information. Thank you.

-Ken Watson