#25460 closed defect (bug) (fixed)
Unhelpful tab order when updating post status and visibility
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.9 | Priority: | normal |
Severity: | normal | Version: | 3.6.1 |
Component: | Editor | Keywords: | has-patch commit 3.9-early |
Focuses: | accessibility | Cc: |
Description
Steps to create:
- Go to Edit Post screen in admin
- Tab to Edit (Status) link and press enter to action link. Focus is transferred to Published dropdown.
- Shift-tab to reverse out, and focus is transferred to bottom of page - a long way from wher you'd expect it to be.
Suggest focus is put back to the Preview Changes button in this instance.
Same is true of Edit (Visibility) link.
Attachments (1)
Change History (11)
#2
@
11 years ago
Tested successfully. If the user happens to shift+tab from the status select, focus moves to the Preview Changes button - which is consistent with the tab order expected. Also, the same is true with the visibility radio buttons.
#5
@
11 years ago
- Keywords commit 3.9-early added
- Milestone changed from Awaiting Review to Future Release
#6
@
11 years ago
Just to be curious. What does need unit tests for this mean? To be able to test this we need behavior testing what we currently not do.
Note: See
TracTickets for help on using
tickets.
25460.1.diff adds a focus() call to put focus on the html element that is sensible.
After cancel you want it to be focused on the Edit link and after you click Edit you want it to be focused on the first select or input.
Is it possible we get js unit tests for this? Can I make them somehow?