feat: Add custom ARIA labels to built-in block dropdown field options#9880
Merged
Merged
Conversation
gonfunko
approved these changes
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The basics
The details
Resolves
Partially fixes #9660
Proposed Changes
This adds a handful of new translatable strings that are used as ARIA labels in dropdown fields for built-in blocks*. ARIA labels are used as overrides for screen readers when focusing these fields if the normal visible label is not fully understandable when read aloud. For example, symbols like '=' or '#' are given as 'equals' or 'number'.
These changes are straight-forward as they aim to match existing labels verbatim. (The similar follow-up for input labels will require some contextual decisions that are more subjective.)
*Only the built-in blocks featured in the playground Categories toolbox were updated here.
Reason for Changes
A full audit of the built-in blocks in the playground was performed at https://docs.google.com/document/d/1VTi1tXK3QrmOIqoDcZ6kjWGO9DzEiiW_CvDxRV4hlsA/edit?tab=t.0
Test Coverage
No tests were added but existing tests were updated that expect correct labels for blocks that were updated here.