Skip to content

[v13.0.0-beta.2] Move mode - moving a block to an input #9803

@microbit-robert

Description

@microbit-robert

Check for duplicates

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

Description

Moving a block to an input inside another block uses the same "inside" terminology as a statement block moving inside a container block at the moment. It can also be unclear which input you are moving to. Please see screen shots below for more information. These also compare what we did for user testing.

Reproduction steps

Priority

No response

Stack trace

Screenshots

I could be on either input that currently has the value of "1", how does the user know which one? There are going to be many cases where the default values are 0 or empty connections so I think this is a real problem. Is the most important information at the start of the screen reader output?
Image

This is from our user testing branch which uses specific messaging for moving to block inputs. In this case, the output also uses a custom input name we have provided to differentiate these inputs from each other. "Moving to number (0) input in plot x, 0, x, 0," is still not that helpful by itself because it doesn't tell the user which input, even if the value is included.
Image

Browsers

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue: bugDescribes why the code or behaviour is wrongissue: triageIssues awaiting triage by a Blockly team member

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions