#2296 closed defect (bug) (fixed)
FAQ question toggles accessibility
Reported by: | joedolson | Owned by: | obenland |
---|---|---|---|
Milestone: | Priority: | high | |
Component: | Plugin Directory | Keywords: | ui-feedback |
Cc: |
Description
The FAQ is toggled directly from a dt
element, which is not keyboard focusable. The toggle should be attached to a button
element nested inside the dt
element, so that it can be operated from the keyboard.
Attachments (1)
Change History (11)
#2
@
8 years ago
What about using a transition on :hover and :focus so that there's a visible change that occurs on focus?
E.g., default state is as currently exists; :hover and :focus rotates 90 degrees then returns to position.
The movement would provide a visual indicator but the state would still return to a constant state.
This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.
8 years ago
#4
@
8 years ago
Also, a change in background color that indicates focus and current would probably work fine. Either way, the change in HTML to add the buttons is a *critical* feature for accessibility.
This ticket was mentioned in Slack in #meta by tellyworth. View the logs.
8 years ago
#7
@
8 years ago
For future reference: https://wordpress.slack.com/archives/C02QB8GMM/p1490220718836135
That could be resolved by moving .focus() to the FAQ answer, which can be made focusable using tabindex=-1, I'd think.
We need to find a solution for focus styles that don't impede mouse interactions