-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update toggletip element roles #13475
Update toggletip element roles #13475
Conversation
…enter and start setting in Editor js
…ement' into a11y/live-region-and-roles # Conflicts: # src/web/assets/cp/dist/cp.js # src/web/assets/cp/dist/cp.js.map # src/web/assets/cp/dist/css/cp.css # src/web/assets/cp/dist/css/cp.css.map
…ement' into a11y/live-region-and-roles # Conflicts: # src/web/assets/pluginstore/dist/css/app.css.map # src/web/assets/pluginstore/dist/js/app.js # src/web/assets/pluginstore/dist/js/app.js.map
I’m not seeing any of those behaviors on my end. It’s not getting a
Agreed, done. |
Apologies for the confusion - I meant that the If you scroll down to the "Toggletips with live regions" section, it outlines the markup/functionality in order to have the info announce after the button is toggled open. |
Gotcha. Most of the HUD code is just for displaying/positioning it properly, so I think it makes sense to use that. We can tweak other behaviors to match the toggletip recommendations though. So to make sure we are on the same page, you are saying:
Is that right? And if so, what should we do instead of |
Yes, if by container you mean the HUD/tooltip container. 👍🏼 All looks good with those bulletpoints.
The |
…ement' into a11y/live-region-and-roles # Conflicts: # src/web/assets/cp/dist/cp.js # src/web/assets/cp/dist/cp.js.map # src/web/assets/cp/dist/css/cp.css # src/web/assets/cp/dist/css/cp.css.map
Alright, made those changes. Let me know how it looks. Also there’s this question, ICYMI: #13475 (comment) |
Looks and sounds great! I made a quick update to add a region role to the container. I only noticed a couple things:
|
…cms/cms into a11y/live-region-and-roles # Conflicts: # src/web/assets/cp/dist/cp.js # src/web/assets/cp/dist/cp.js.map
Alright, those are addressed! |
635d4f2
into
feature/dev-1154-show-other-authors-editing-the-same-element
Description
Updated roles so that toggletip uses button role instead of
li
. The button label has also been updated to use a disclosure message rather than the contents of the toggletip. Upon testing, live region messages have been nixed as they don’t communicate a status update and may cause the interface to be too chatty.A couple of outstanding questions I’m hoping to get your opinion on @brandonkelly
role="status"
, the message container will be empty and present in the accessibility tree on page load (notdisplay: none
when closed), and the message container will be emptied and then re-injected when the button is toggled open. In that case, should the message container be something other than a HUD?Related issues