fix: Do not use custom input labels for connection positions and move start#9932
Merged
mikeharv merged 2 commits intoMay 26, 2026
Merged
Conversation
maribethb
approved these changes
May 26, 2026
mikeharv
changed the title
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
Fixes #9922
Proposed Changes
Stop using custom input labels when computing block ARIA labels for the start of a move announcement.
Before:
After:
Stop using custom input labels when using a subset of input labels, for example, when focusing a statement input on a container block.
Before:
After:
Reason for Changes
Fixes two bugs where custom input labels are used in place of more useful computed labels from fields.
Additional Information
I think it would be worth considering making
useCustomLabelsdefault tofalse.