Make WordPress Core

Opened 7 years ago

Closed 5 years ago

#40391 closed enhancement (duplicate)

Make the Live Search accessible

Reported by: travel_girl's profile Travel_girl Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Administration Keywords:
Focuses: ui, accessibility Cc:

Description

The Live Search for

  • search installed plugin
  • install plugin
  • search installed Themes
  • install theme

need some improvement for accessibility and in my eyes also for user experience.

When a user start typing, the search for plugins/themes starts right away, which is a bit distracting and confusing, especially if you don't type fast.

A possible solution could be

  • the result starts after 3 letters (not with the first one)
  • expand the timeout, when results get displayed
  • allow users to set a profile option, that they are slow typers (and lets them define the speed. I think "fast" and "slow" would be not detailed enough)


Change History (6)

#1 @swissspidy
7 years ago

  • Component changed from General to Administration

expand the timeout, when results get displayed

What I mentioned before is that we could pass this timeout to the live search JavaScript using wp_localize_script(), thus making it possible for plugin authors to filter that value.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


7 years ago

#3 @afercia
7 years ago

  • Keywords close added

Thinking there's already #31818 which aims to cover all the search implementations in core, including the "live search", I'd propose to keep the conversation just in one place and close this ticket. The only reason #31818 hasn't seen so much progress so far, is the lack of time and volunteers to actually start some coding. Volunteers welcome! 🙂

This ticket was mentioned in Slack in #accessibility by trishasalas. View the logs.


7 years ago

#5 @trishasalas
7 years ago

Suggesting that we keep this open and reference it to #31818. The idea is to keep tasks small and manageable while still referencing the topic it addresses...in this case 'Uniform Search' WCAG 3.2.3

#6 @afercia
5 years ago

  • Keywords close removed
  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Closing in favor of #31818, to help the accessibility Trac reports stay clean.

Note: See TracTickets for help on using tickets.