Tab order of text in blocks in not consistent

[mscherotter]

Check for duplicates

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

Description

Using Windows 11 & Microsoft Edge or Google Chrome
The tab order of text in blocks is not consistent - left to right, top to bottom as can be seen in this video recording using the Narrator tool in Windows. I am just pressing the Tab key to move the cursor:

See video recording:
https://github.com/user-attachments/assets/d8fb3393-0547-4136-a0cc-8ead34bc5bba

Reproduction steps

1. Navigate to https://google.github.io/blockly-keyboard-experimentation/
2. Place a Loops/Count-with block on the canvas
3. Use the tab key to narrate the block contents
4. Notice that the tab order is not expected: first fields and then static text. it should be left to right, top to bottom.

Stack trace

Screenshots

No response

Browsers

Chrome desktop

[BenHenning]

This is actually a really interesting issue--thanks for filing it and especially for the recorded video. I'm surprised to see how tab is behaving with Narrator. Unless I'm mistaken, it actually seems to be violating the spec here. Per https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/tabindex a negative tab index should not be reachable with sequential navigation, and in fact those text elements don't even have a negative tab index.

I can't easily test with Navigator, but I will need to look into why it's doing this.

[mscherotter]

Please reach out if you need some help testing. Michael S. Scherotter ***@***.***

…

________________________________ From: Ben Henning ***@***.***> Sent: Monday, July 28, 2025 10:22:14 AM To: google/blockly-keyboard-experimentation ***@***.***> Cc: Michael S. Scherotter ***@***.***>; Author ***@***.***> Subject: Re: [google/blockly-keyboard-experimentation] Tab order of text in blocks in not consistent (Issue #672) [https://avatars.githubusercontent.com/u/12983742?s=20&v=4]BenHenning left a comment (RaspberryPiFoundation/blockly-keyboard-experimentation#672)<#672 (comment)> This is actually a really interesting issue--thanks for filing it and especially for the recorded video. I'm surprised to see how tab is behaving with Narrator. Unless I'm mistaken, it actually seems to be violating the spec here. Per https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/tabindex a negative tab index should not be reachable with sequential navigation, and in fact those text accessibility nodes don't even have a negative tab index. I can't easily test with Navigator, but I will need to look into why it's doing this. — Reply to this email directly, view it on GitHub<#672 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAE4VJQQDAE5XYEVAM37UQL3KZL4NAVCNFSM6AAAAACBYQSXYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMRYGI2DAOBQGI>. You are receiving this because you authored the thread.Message ID: ***@***.***>