New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility feedback: the Publish button placement is confusing #3697

Closed
afercia opened this Issue Nov 28, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@afercia
Contributor

afercia commented Nov 28, 2017

Reporting some first feedback from real assistive technologies users, see https://make.wordpress.org/accessibility/2017/11/28/screen-reader-user-experience-with-gutenberg/

Well I doodled with the editor, the best thing about it, well there isn’t, I guess the heading where the title should be is nice. The rest, I was able to add a block of text, typing it up but the publish menu I couldn’t exactly navigate, I preferred the button as it was.

As already mentioned a few times on other issues, the placement of the Publish button is not ideal, as users are forced to navigate tabbing backwards to find it.

In the Classic Editor, in terms of keyboard navigation, the publish button is placed after the editor. This matches a logical flow, where users first add a title, add a content, and then they find the publish options and button.

In Gutenberg, the Publish button is placed before the editor. As mentioned a few times before, this has nothing to do with the visual placement. What matters here is the placement of the button in the markup, and thus its position in the tab sequence.

For keyboard and screen reader users, navigating content is a linearized experience. Placing the Publish button before the content is just counterintuitive and doesn't match a common sense logical flow where users first edit the content, and then they publish.

@afercia

This comment has been minimized.

Show comment
Hide comment
@afercia

afercia Nov 28, 2017

Contributor

For some previous discussion about this issue, see #467 "Editor toolbar: controls order and grouping" then renamed to "Add keyboard shortcuts à la Slack to jump through the main UI sections"

Contributor

afercia commented Nov 28, 2017

For some previous discussion about this issue, see #467 "Editor toolbar: controls order and grouping" then renamed to "Add keyboard shortcuts à la Slack to jump through the main UI sections"

@afercia

This comment has been minimized.

Show comment
Hide comment
@afercia

afercia Jul 16, 2018

Contributor

Discussed during today's accessibility bug-scrub. Worth noting the Publish button and related panel have been greatly improved recently in #7552. Pending some more testing, this issue is a close-candidate.

Contributor

afercia commented Jul 16, 2018

Discussed during today's accessibility bug-scrub. Worth noting the Publish button and related panel have been greatly improved recently in #7552. Pending some more testing, this issue is a close-candidate.

@aaronjorbin

This comment has been minimized.

Show comment
Hide comment
@aaronjorbin

aaronjorbin Oct 8, 2018

Member

I'm going to close based on the last comments. We can reopen if there are still major concerns.

Member

aaronjorbin commented Oct 8, 2018

I'm going to close based on the last comments. We can reopen if there are still major concerns.

@aaronjorbin aaronjorbin closed this Oct 8, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment