The attached html file demonstrates the bug. In Safari 7.0.3 on OS X 10.9.2, when you add an additional live region to the page and then change its text, nothing is announced. I was able to figure out a hacky workaround in Chromium that would probably work in WebKit/Mac too - if I remove the wrapper object for the root webarea node and recreate it, then fire a notification on it, that seems to trick VoiceOver into re-scanning the document for live regions and then it works correctly. Does this look like a VoiceOver bug or is there a more proper fix that can be applied in WebKit?
Created attachment 231020 [details] Html that demonstrates the bug
<rdar://problem/16844111>
I haven't tried out your test case, but this may have been fixed with AX: Improve ARIA live region reliability by sending notifications when live regions are created/shown and hidden/destroyed https://bugs.webkit.org/show_bug.cgi?id=124381
You're right, that will probably solve it. I can't find docs for NSAccessibilityLiveRegionCreatedNotification - can you tell me what OS X version added support for it?
(In reply to comment #4) > You're right, that will probably solve it. > > I can't find docs for NSAccessibilityLiveRegionCreatedNotification - can you tell me what OS X version added support for it? It's a web only thing. It's just defined in WebCore as is
The example I uploaded still doesn't work correctly when I try today's WebKit Nightly on OS X 10.9.2, so I'm assuming that AXLiveRegionCreated will only be supported in a future version of VoiceOver.
(In reply to comment #6) > The example I uploaded still doesn't work correctly when I try today's WebKit Nightly on OS X 10.9.2, so I'm assuming that AXLiveRegionCreated will only be supported in a future version of VoiceOver. that is a fair assumption
*** This bug has been marked as a duplicate of bug 124381 ***