Description
Similar to #65112
See the above issue for more context.
When possible, the visual labeling of controls should match the actual accessible name (provided for example by a visually hidden <label> element, or an aria-label or aria-labelledby attributes).
All the search inputs in the editor should be audited and any mismatch avoided.
As an example, the Search input in the Styles panel > Blocks is visually labeled via its placeholder attribute. This is already arguable, as placeholders should not be used as replacement for labels.
- The placeholder value is
Search.
- The actual accessible name is
Search for blocks.
While the added context may help blind screen reader users, it doesn't help other users and may even be an accessibility barrier, for example for sighted screen reader users and speech recognition / voice control users.
Step-by-step reproduction instructions
- Go to Site Editor > Styles > Blocks.
- Observe the search input placeholder is the only visible 'label' of the input and it's
Search.
- Observe the actual accessible name provided by a visually hidden
<label> element is Search for blocks.
Screenshots, screen recording, code snippet

No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Description
Similar to #65112
See the above issue for more context.
When possible, the visual labeling of controls should match the actual accessible name (provided for example by a visually hidden
<label>element, or anaria-labeloraria-labelledbyattributes).All the search inputs in the editor should be audited and any mismatch avoided.
As an example, the Search input in the Styles panel > Blocks is visually labeled via its placeholder attribute. This is already arguable, as placeholders should not be used as replacement for labels.
Search.Search for blocks.While the added context may help blind screen reader users, it doesn't help other users and may even be an accessibility barrier, for example for sighted screen reader users and speech recognition / voice control users.
Step-by-step reproduction instructions
Search.<label>element isSearch for blocks.Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Please confirm that you have tested with all plugins deactivated except Gutenberg.