You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reading the Popover documentation, it’s clear that the component is primarily intended for providing additional information. However, I’m wondering if it would be appropriate to use Popover for allowing users to perform actions in scenarios where other components, such as Modal, Menu, or Dropdown, don’t quite fit the use case.
As an example, see the screenshots below of rough prototypes for an interface that allows users quick access to available Wi-Fi networks and keyboard layout from a top toolbar.
Avilable Wi-Fi networks
Localization options
One concern I have is that the Popover component internally uses the aria-describedby attribute, which I believe makes the interactive content inaccessible. From my limited understanding of accessibility, and after reviewing MDN's documentation, it seems that using aria-details might help.
The aria-describedby property is appropriate when the associated content contains plain text. If the content is extensive, contains useful semantics, or has a complex structure requiring user navigation, use aria-details instead. aria-details allows assistive technology users to visit the associated structured content and provides additional navigation commands, making it easier to understand the structure, or experience the information in smaller pieces.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
While reading the Popover documentation, it’s clear that the component is primarily intended for providing additional information. However, I’m wondering if it would be appropriate to use Popover for allowing users to perform actions in scenarios where other components, such as Modal, Menu, or Dropdown, don’t quite fit the use case.
As an example, see the screenshots below of rough prototypes for an interface that allows users quick access to available Wi-Fi networks and keyboard layout from a top toolbar.
One concern I have is that the Popover component internally uses the
aria-describedby
attribute, which I believe makes the interactive content inaccessible. From my limited understanding of accessibility, and after reviewing MDN's documentation, it seems that usingaria-details
might help.What are your thoughts on this? Would it be possible to extend/adapt Popover to make possible its sparing usage for these scenarios?
Thanks in advance for your input!
Beta Was this translation helpful? Give feedback.
All reactions