Orca incorrectly announces content-editable elements in Chromium
When changing between tree elements which transform to be editable, Orca will sometimes fail to announce that the element is editable.
Microsoft Edge and the Chromium Project DevTools use a scheme in the Elements-Styles pane which might be somewhat unusual. An active element is marked
contenteditable="plaintext-only", among some other ARIA attributes, and then the overarching control handles tabbing so that it can account for read-only elements, committing changes, etc.
I've produced a minimal repro here: https://jsfiddle.net/u8ems31n/1
Both NVDA on Windows, and Narrator on Mac OS, behave as expected. As an example, NVDA will read out "Item key edit subMenu multi line selected Item 1", "Item value edit subMenu multi line selected Value". On the first item, Orca will read out the complete set of things, but in the second, Orca would simply say, for example, "Value selected Value".
Orca does seem to correctly announce it differently when navigating between different tree levels, or for the first time that one such item is selected.