Opened 10 years ago
Closed 4 months ago
#32768 closed enhancement (fixed)
Customizer Widgets and Themes search improvements
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 4.9 | Priority: | normal |
Severity: | normal | Version: | 4.2 |
Component: | Customize | Keywords: | reporter-feedback |
Focuses: | accessibility, javascript | Cc: |
Description
Widgets and Themes search would need the same improvements done for the Menu Customizer.
Widgets:
- activating "Add a Widget" with the Space bar doesn't prevent the default action, as a result the search field gets a space character and the placeholder text is gone. See https://github.com/voldemortensen/menu-customizer/issues/107
Both:
- 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 (10)
#4
@
9 years ago
The first widgets part was fixed in [35304]. Still to do: the search for both Widgets and Themes.
This ticket was mentioned in Slack in #accessibility by afercia. View the logs.
8 years ago
#9
@
4 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.
This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.
4 months ago
#11
@
4 months ago
- Milestone changed from Future Release to 4.9
- Resolution set to fixed
- Status changed from assigned to closed
I've confirmed that everything cited in the original ticket is now fixed, and this can be closed. If there are any additional issues, they should be raised in a new ticket.
Closing this as fixed in 4.9, as suggested by @celloexpressions.
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.