E-mail List Archives
Re: Web Accesibility and popovers
From: Patrick H. Lauke
Date: Apr 11, 2019 6:39PM
- Next message: Patrick H. Lauke: "Re: Web Accesibility and popovers"
- Previous message: David Engebretson Jr.: "using aria too much"
- Next message in Thread: Patrick H. Lauke: "Re: Web Accesibility and popovers"
- Previous message in Thread:
: "Re: Web Accesibility and popovers" - View all messages in this Thread
While not explicitly stated in the bootstrap documentation, popovers
(similar to tooltips) are really not currently meant to contain
interactive content (though this is something planned, in a much more
structured way, in future releases).
In your example, you seem to be using the hover trigger only. This makes
it unworkable for keyboard users.
I'd note that if you have anything focusable in the popover, I'd stay
clear of the using just the focus and hover triggers, as the focus one
will only show the popover when the trigger element has focus...as soon
as you try to move to the interactive elements in the popover itself, it
will close/disapper. You can probably use a combined click and hover
trigger.
Make sure there's an actual visible focus indication when that button
gets focus (currently you're suppressing outline, for instance).
In some mild testing, the aria-describedby seemed to work, which is why
bootstrap uses this approach. Glen, which combination of browser/AT was
causing problems for you?
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
- Next message: Patrick H. Lauke: "Re: Web Accesibility and popovers"
- Previous message: David Engebretson Jr.: "using aria too much"
- Next message in Thread: Patrick H. Lauke: "Re: Web Accesibility and popovers"
- Previous message in Thread:
: "Re: Web Accesibility and popovers" - View all messages in this Thread