Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Accessibility feedback: the Publish button placement is confusing #3697
Reporting some first feedback from real assistive technologies users, see https://make.wordpress.org/accessibility/2017/11/28/screen-reader-user-experience-with-gutenberg/
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.