[Screen reader] Announcing move mode for top-level blocks without constrained positions #757
Description
Check for duplicates
- I have searched for similar issues before opening a new one.
Description
When inserting top-level blocks on to the workspace (or to a lesser extent, putting them into move mode with 'M') where they have no constrained positions, it's not necessarily clear that they are in move mode as this is not announced by screen readers. There's definitely an argument here that this is a learned behaviour, but the difference in readout between blocks with and without constrained positions feels awkward.
A related issue is when you put any block into move mode (even if it has constrained positions available), confirm it's position, then immediately put it back into move mode again. The fact that it is now in move mode is not announced, probably because the content of the aria-live region hasn't changed? Perhaps it needs aria-atomic or needs clearing after a move has been confirmed? Again, less of an issue when the user presses 'M' (unless by accident) as there are also earcons associated with entering and confirming moves.
Reproduction steps
- Go to https://google.github.io/blockly-keyboard-experimentation/screenreader/
- Turn on a screen reader
- Insert a function block
- The screen reader output doesn't make it clear that the block is in move mode
Stack trace
Screenshots
No response
Browsers
No response