[13.0.0-beta.4] Screen reader mode prevents valid moves

[microbit-matt-hillsdon]

Check for duplicates

• I have searched for similar issues before opening a new one.

Description

Enabling screen reader mode makes it impossible to move some blocks into some constrained positions.

Reproduction steps

1. Arrange blocks per screenshot
2. Use M and up/down to move the 123 block and note you have two positions (repeat count, workspace)
3. Enable screen reader mode via Cmd+Opt+Z (confirm toast is shown)
4. Repeat 2, but note you can unexpectedly no longer do any constrained moves for the block

If you remove the function around the repeat then this no longer happens.

Priority

No response

Stack trace

Screenshots

Browsers

No response

[microbit-robert]

At of beta.6, there is still something strange happening here when screen reader mode is switched on. The video below starts with screen reader mode switched off. Once on, there is asymmetry in the positions visited when moving up verses down.
https://github.com/user-attachments/assets/9f3ad2ae-3d19-4d55-86fd-b5291af31ed8

[gonfunko]

That's working as intended; when looping is off, it still offers a top-level-block-on-the-workspace position, but it would be weird if you hit up and it moves it way down the page, or vice versa, so a top-level position is offered above all the other blocks and below them depending which direction you're moving. With looping on, that behavior would feel weird, so there's just one top-level-block stop that's part of the overall loop. IIRC this also made the implementation a bit easier, but it's mostly a vibes-based thing.

[microbit-robert]

Okie dokie. I think it's unfortunate that it will mostly be blind users who experience the looping off behaviour. They won't know where a block on the workspace is in relation to other blocks so may find this behaviour surprising. We can test with it though.

[gonfunko]

That's a reasonable point; would you prefer this behavior be present for looping mode too, or only have one top-block stop for both?

[microbit-robert]

This feels like a product decision which needs discussion as we don't have any user test data for this.