Thanks for the report.

It looks like you're running an older version of Chrome (I'm assuming you tested on the machine you're filing from). We fixed quite a few bugs between version 53 to version 57 (which is currently on stable channel). Any chance you could update? Thanks!

Thanks!

Just updated my chromebook to the latest beta release (58), and I'm still not hearing the notification when I change between expanded and collapsed. This is in both verbose and non-verbose mode.

Sorry, I can't reproduce.

When I'm on the or tree item and I press left, ChromeVox says:
" or expression 2 inputs, tree item, collapsed, multiselect, 5 of 5, level 1

when I press the right arrow key,
I get the same as above, except "expanded" rather than "collapsed".

Sped up the reading speed, and now I realize what's going on. CV is re-reading the element label before moving on to other information (such as collapsed state, arity, etc).

Both NVDA and Jaws read the state change first, which (a) I'm used to and (b) seems far more intuitive. Since the the active element doesn't change when expanded is toggled, the most relevant information is the changed state. Describing the element *first* means forcing the user to wait for redundant information to pass before getting to the relevant info.

Of course, reasonable minds can disagree, and a UI critique is outside the scope of this bug report. I'm comfortable closing this, but would love to continue the UI discussion offline.

Closing this bug as WontFix (cannot reproduce), but please feel free to follow up with your thoughts on the chromium-accessibility Google group!