[wip?] Accessibility-motivated markup changes #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This originated from https://www.drupal.org/project/ckeditor5/issues/3209517, there are several changes here
role="button". Although those items represent buttons, they should not be conveyed as buttons to assistive tech as they are not clickable elements that trigger a reposnse when clickedaria-expandedis no longer used as an attribute, the content that is hidden/shown isn't really toggleable, it's shown on hover/focus. The content of the tooltip is in the aria-labelledby span, so the tooltip content is announced on focus already.role="option", so the containing<ul>really should haverole="listbox". I submitted a PR to vue.draggable Expand isHtmlAttribute SortableJS/vue.draggable.next#35 to make this possible. However, I think the fallback behavior (describing the list option as a "text element",) is preferable to it being described as a button.If this lands a bit CSS in Drupal will need to be changed since aria-expanded won't be used (and ideally aria attributes shouldn't be used for CSS anyway)
to