NVDA reads multiple inline-block items in one line

[nvaccessAuto]

Reported by james.curd.razorfish on 2015-04-06 18:52
When using up and down arrows to navigate, NVDA reads all display: inline-block; elements—whether they are buttons or links—simultaneously with a single press of an arrow key. Pressing the arrow key again will move the user on without stopping on the any of the remaining inline-block elements. The user must hit tab in order to land on subsequent elements.

[http://codepen.io/aminimalanimal/pen/WbWgjb]

[nvaccessAuto]

Comment 1 by nvdakor on 2015-04-06 18:55
Hi,
This happens if use screen layout is on. Have the user press NVDA+V to turn screen layout off.
Thanks.

[nvaccessAuto]

Comment 2 by jteh on 2015-04-07 01:47
Rendering of inline elements on the same line is intentional with screen layout enabled. Aside from the tab key, the user could move by character (rightArrow), move by word (control+rightArrow) or use quick navigation (e.g. k to get to links) to get to the next element.

Inline-block is a bit controversial. It's debatable as to whether inline-block should be treated as if it's on the same line or on a different line. We found that it's usually desirable to treat them as inline. See #1378.

In short, if you don't want this behaviour, disable screen layout as suggested in comment:1.
Changes:
Added labels: wontfix
State: closed

[nvaccessAuto]

Comment 3 by james.curd.razorfish on 2015-04-07 18:04
Thanks for explaining. :)