WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 8 years ago

#23891 closed task (blessed) (invalid)

Post Formats: tab accessibility

Reported by: markjaquith Owned by:
Milestone: Priority: normal
Severity: critical Version: 3.6
Component: Accessibility Keywords: needs-patch needs-codex
Focuses: Cc:

Description

Post Format UI should allow for natural tabbing through the editable fields.

Change History (7)

#1 @DrewAPicture
8 years ago

  • Keywords needs-codex added

Adding needs-codex because keyboard accessibility will be part of the overall article.

#2 @lessbloat
8 years ago

#23838 is related.

#3 @azaozz
8 years ago

#23838 was marked as a duplicate.

#4 @azaozz
8 years ago

How exactly do we want thins to work?

Currently there is JS that "jumps over" from the title to the editor bypassing anything in between (like the Edit Slug field/button, etc.). Tabbing backwards works as before to access any bypassed fields.

#5 @joedolson
8 years ago

What I'm seeing is that tabbing stops entirely when you hit the Title field; the JS that is intended to jump over the title to the editor doesn't appear to be functioning.

This is complicated, actually, from a usability standpoint for keyboard editors -- though it really goes beyond just the post format UI; this is a general post editor UI issue.

Regardless, I wonder if it would be helpful to add a set of skip link navigation tools after the content editor textarea. I don't think that there's a single answer that is actually ideal. I do think that a user should be able to navigate straight through the title/content fields, but after passing through the content field, it's unclear what is most desirable: to continue to post meta fields (which could be a very long process), or to jump to the publishing meta. I could imagine that a set of skiplinks offering navigation choices to keyboard navigators after leaving the content field would be valuable: a choice to jump over to the publish fields or to continue to the post meta fields. (e.g., a choice to continue in the source order or jump directly to publishing.)

It's not a perfect solution, but would allow a usable interface that allows a user to either publish immediately or add meta data easily, depending on their usage.

#6 @SergeyBiryukov
8 years ago

#23838 was marked as a duplicate.

#7 @markjaquith
8 years ago

  • Milestone 3.6 deleted
  • Resolution set to invalid
  • Status changed from new to closed

Removing post formats UI from core: #24452

Note: See TracTickets for help on using tickets.