Make WordPress Core

Opened 9 years ago

Last modified 3 years ago

#32768 assigned enhancement

Customizer Widgets and Themes search improvements

Reported by: afercia's profile afercia Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 4.2
Component: Customize Keywords: reporter-feedback
Focuses: accessibility, javascript Cc:


Widgets and Themes search would need the same improvements done for the Menu Customizer.



  • the search results (or no results) should be announced to assistive technologies, possible use case for wp.a11y.speak see #32720
  • a short description of the "live" search functionality could help, see the Menu items search in core, i.e.: aria-describedby="menu-items-search-desc"

Change History (8)

#1 @celloexpressions
9 years ago

  • Milestone changed from Awaiting Review to Future Release

#2 @valendesigns
9 years ago

  • Owner set to valendesigns
  • Status changed from new to assigned

There really should be more parity in the Customizer, whether that be functionality or accessibility it should all work relatively the same. I'll take this one on in 4.4.

#3 @afercia
9 years ago

  • Keywords 4.4-early added

#4 @afercia
8 years ago

The first widgets part was fixed in [35304]. Still to do: the search for both Widgets and Themes.

#5 @afercia
8 years ago

Related: #32882.

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

7 years ago

#8 @afercia
5 years ago

  • Keywords needs-patch 4.4-early removed

For history: the parts mentioned here as still to address (the search for both Widgets and Themes) were actually fixed in [38709] for the Widgets and in [41648] for the Themes, with the introduction of the new "Themes browser".

#9 @celloexpressions
3 years ago

  • Keywords reporter-feedback added
  • Owner valendesigns deleted

@afercia what is left to do here? From 8 it sounds like these items are fixed now and this ticket can be retroactively closed as fixed in 4.9 (the themes panel redesign).

Noting that customizer widgets are being replaced with blocks in 5.8, so that piece should be addressed with the upcoming version if it wasn't already fixed.

Note: See TracTickets for help on using tickets.