#40515 closed defect (bug) (fixed)
Settings: date and time custom format keyboard trap
Reported by: | afercia | Owned by: | afercia |
---|---|---|---|
Milestone: | 4.8 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Administration | Keywords: | has-screenshots has-patch |
Focuses: | accessibility | Cc: |
Description
Noticed while working on the Settings API enhanced.
When using a keyboard and trying to set the Date and Time format, users get "trapped": when focusing the custom format field.
The related radio button gets automatically selected and there's basically no way to select a radio button other than the custom format one. The only options would be:
- select a radio button and then tab backwards through the whole interface until tabbing reaches the top of hte page and starts again from the bottom of the page: at that point users can finally reach the Save Changes button and save
- select a radio button and press Enter to submit the form while the radio button is selected
To reproduce:
- use your keyboard Tab key to navigate to the Date format setting
- once the active radio button has focus, use the arrow keys to change format
- at that point you need to press the Tab key to move away from the radio buttons
- as soon as you do that, the custom format field gets focused
- the related custom format radio button gets automatically selected
While this may make sense when using a pointing device (mouse or similar), it's a huge barrier for keyboard and screen reader users. Since the fix is simple enough, I'd propose this ticket for 4.7.5 consideration.
Simply changing the focus
event to click input
would solve the issue:
- for mouse users: the automatic selection would still work when clicking on the input field
- for keyboard users: the automatic selection would happen just when they actually change the value in the input field, thus they would be allowed to keep navigating trough the form using the Tab key
Attachments (1)
Change History (7)
#3
follow-up:
↓ 4
@
8 years ago
Patch works like a charm. +1 from me.
Would it make sense to disallow tabbing into the input fields unless the 'Custom' radio button is selected?
#4
in reply to:
↑ 3
@
8 years ago
Replying to swissspidy:
Thanks for testing!
Would it make sense to disallow tabbing into the input fields unless the 'Custom' radio button is selected?
From an a11y perspective, yes. But for mouse users that would require an additional click?
Forgot to mention this was also tested at WordCamp Torino 2017 Contributor Day, props to:
@danuccia, @vallisca, @giux2, @viroproject