Users are reporting a bug when navigating Google Inbox in Chrome with NVDA - as you move between messages, NVDA is announcing both the old message and new message.
See http://crbug.com/600150 for context.
I've reduced this down to the essential issue, which is that Inbox is effectively renaming the old and new messages at the same time as it's moving focus. If NVDA gets the name change event on the old list item before it gets the focus event on the new item, it reads out the name change but doesn't interrupt / cut it off when it gets the focus event.
I don't think it's incorrect that NVDA reads out the changed name of the old list item because it was focused, but I think it should interrupt that when focus changes, just like it interrupts any speech from a previous focus event when focus changes again.
The attached standalone HTML file demonstrates the issue in both Firefox and Chrome. Other screen readers work fine with the same example.
listbox-namechange.zip
Users are reporting a bug when navigating Google Inbox in Chrome with NVDA - as you move between messages, NVDA is announcing both the old message and new message.
See http://crbug.com/600150 for context.
I've reduced this down to the essential issue, which is that Inbox is effectively renaming the old and new messages at the same time as it's moving focus. If NVDA gets the name change event on the old list item before it gets the focus event on the new item, it reads out the name change but doesn't interrupt / cut it off when it gets the focus event.
I don't think it's incorrect that NVDA reads out the changed name of the old list item because it was focused, but I think it should interrupt that when focus changes, just like it interrupts any speech from a previous focus event when focus changes again.
The attached standalone HTML file demonstrates the issue in both Firefox and Chrome. Other screen readers work fine with the same example.
listbox-namechange.zip