Skip to content
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

New post: automatically focus post title #1649

Closed
JDGrimes opened this issue Jul 2, 2017 · 4 comments
Closed

New post: automatically focus post title #1649

JDGrimes opened this issue Jul 2, 2017 · 4 comments
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes).

Comments

@JDGrimes
Copy link
Contributor

JDGrimes commented Jul 2, 2017

When creating a new post, I expect to be able to just start typing. Instead, I have to manually focus the title field before entering my title.

(Apologies if this is a duplicate or has already been rejected for some reason.)

@afercia
Copy link
Contributor

afercia commented Jul 3, 2017

Auto focusing some UI controls is always a bit tricky and, generally, assumes just one workflow. It makes sense when there's one, very specific, task. For example, a short form gets displayed in some UI section with a very specific task to complete: focusing the first form field makes sense.
However, in the editor there are several, possible, workflows. Users may prefer to start setting some post settings, or clicking on the inserter to add some blocks. Also, some custom post types don't have a title.

For keyboard users, auto focusing the title field would "skip" all the UI controls that are placed before the field, forcing them to tab backwards. For screen reader users, "skipping" all the toolbar would make those controls harder to discover.

Somewhat related also to the general grouping and order of controls, see #467

Ideally, if a UI controls is important enough to automatically receive focus, then maybe it's worth considering placing it as the very first thing in the interface. This is what WordPress has already done, for example, with the comments textarea. See https://core.trac.wordpress.org/ticket/29974

@JDGrimes
Copy link
Contributor Author

JDGrimes commented Jul 3, 2017

Yeah, I thought that might be an issue. However, WordPress already does this on the add new post screen, so I guess I just kind of missed it and it felt like a regression.

@afercia
Copy link
Contributor

afercia commented Jul 3, 2017

WordPress already does this on the add new post

Yep, right. I missed to mention that. However, in the current edit screen there's very little before the title field: main heading, screen options/help tabs. Instead, in Gutenberg many important controls are placed before the title.

@afercia afercia added the [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). label Jul 12, 2017
@mtias
Copy link
Member

mtias commented Aug 31, 2017

Going to close this, as it's not clear it'd be an improvement (specially if you don't want a title).

@mtias mtias closed this as completed Aug 31, 2017
Tug pushed a commit that referenced this issue Feb 28, 2020
* improve test:e2e:ios:local, skip bundling on CI since we do it manualy

* use already existing command

* run preios before tests build and use --repo-update flag
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes).
Projects
None yet
Development

No branches or pull requests

3 participants