Make Search Field for Module Install/Uninstall usable

I would *love* this. It used to work this way. But apparently it is bad for accessibility. At the cost of great usability for sighted users, sadly.

It's an unfortunate compromise. Maybe something has changed in the meantime though.

Hi guys!

Please, can you explain details for this task, not sure that I understand what did you mean
Maybe you mean default focus at search field on modules page?

Thanks

@Greg Sims The issue summary is short but it is pretty clear to me. You could maybe clear it up for others by incorporating your prior comment.

done

tested manually, it works!
really useful!

See #3.

I don't think all our users with visual difficulties are all cured yet. Won't fix.

@Greg Sims: think of it as a show of support for them. And to start with: there is module filter in core and Ctrl+F is actually useful now. Surely a click is not that bad. Contrib can always reduce a11y with a form_alter of some kind :)

Yep, let's get more reviews!
My POV that this page is 99% of time will be visited by developers/builders to enable module.
So having "autofocus" of that will save a lot of hours removing this "single click"

I call to reconsider that so linking previous attempts

Agree with @Andypost, I think it is useful to have autofocus without any additional keyboard manipulations

This is a modules page, so the primary action is to find module and enable, so the argument in #2096347-19: Add "autofocus" attribute to the module search is totally wrong
Maybe autofocus does not fits for a11n but for this page the primary interaction is search
So maybe patch should detect screenreaders (maybe modernizr) and set focus for all others that are 99%

Accessibility is a gate and it's not really up for debate. If you have a solution that makes this usable for screen reader users (and you have verified that by testing it yourself or asking a screen reader user for assistance), feel free to reopen. Otherwise, this has already been debated, redebated, and argued in pretty much every way in many other issues. This is still a won't fix.

Write a contrib module if it bothers you that much, or just use Drush.

@andypost, saying that an argument from somebody that this actually affects is insensitive. I encourage you to try the module page with autofocus enabled via screen reader software. Using the modern web is really damn hard if you can't see what's happening. Drupal shouldn't contribute to that.

Adjusting issue metadata for accuracy.

Ok, let's postpone then and re-scope to theme change and improve usability of primary interaction

No matter what solution we come up with here, anything that automatically focuses a field on the page needs accessibility review.

This is also going to need an issue summary update on why the current field is not "usable".

there's nothing to review yet, summary already updated in #17

Make it Configurable.

Accessibility killing Drupal silently. This issue is not alone:
#2346973: Improve usability, accessibility, and scalability of long select lists

there's no patch, so status wrong. also 8.1 still not open

So hopefully in early January https://www.drupal.org/node/2455081

This came up on a Bug Smash triage

Can we get some steps to reproduce added here so its clear what we're fixing?

Based on the current patch, this feels like a feature request rather than a bug.

There are concerns with auto-focus
https://brucelawson.co.uk/2009/the-accessibility-of-html-5-autofocus/
https://ux.stackexchange.com/questions/60026/when-is-it-appropriate-to-a...

If this is more than auto-focus then this should be more explicit. Otherwise for consistency we should probably close this issue as per https://www.drupal.org/node/2096347

That is until convenience wins over predictability.

Just following up if this should be re-open,. if no follow up in 3 months could be closed

I'm going to close this as works as designed for the following reasons.

Honestly reading through the most recent stack exchange in 43 I think this form actually qualifies and is eligible for auto focus.

99% of the time I visit that page the first thing I do is click in the search field.

The other 1% I ctrl f to search.

However, as pointed out this is a very simple contrib or custom module with a form alter and library so it should be handled in contrib instead of being hashed out here with the ability to disable it.

Then it can be included in cms.

If someone ends up creating that please post it here so people can find it.

I don't think will get this in core though so let's close this for now.

Thanks everyone!

I did add credit here for the effort over the years. It is appreciated so please comment when the contrib module is created.