Replacing content in a browser context loses track of focused DOM node.

Originator:nathan
Number:rdar://26630697 Date Originated:2016-06-03
Status:Open Resolved:
Product:Accessibility Product Version:OS X 10.11.*
Classification:Bug Reproducible:Always
 
Summary:
VoiceOver appears to be losing track of the items in its buffer and, after browser repaint/setting of focus, still maintains a reference to the element which has been removed. When Accessibility Inspector asks what it believes currently has focus, VoiceOver is setting focus to the closest previous item which is still present in its buffer.

Steps to Reproduce:
Using VoiceOver, visit:
1. http://ember-a11y.github.io/ember-a11y/
2. Click the "Messages" link.
3. Click the "Conversation with Jimmy" link.
4. Click the "Back to message list." link.

Can recreate the issue using vanilla JavaScript (without Ember) as well.

Expected Results:
The focus should be reset to the header, not remain highlighting the previously focused link.

Actual Results:
The browser focus is set to the proper area, VoiceOver reads the correct content, but the VoiceOver cursor position remains the non-existent previous link, and the Accessibility Inspector believes that the focus is the closest prior element which still exists in the browser DOM.

Version:
OS X 10.11.*

Notes:
Full details, including a step-by-step analysis in Accessibility Inspector can be found here: https://github.com/ember-a11y/ember-a11y/issues/1

Configuration:
Use VoiceOver on El Capitan and test in Safari.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!