Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 89223 Live Region updates are not announced
Starred by 5 users Project Member Reported by, Jul 13 2011 Back to list
Status: Fixed
Owner: ----
Closed: Jan 2015
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocked on:
issue 447962

Sign in to add a comment
Chrome Version       : 14.0.821.0
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)

UserAgentString: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.821.0 Safari/535.1

Comment 1 by, Jul 13 2011
Labels: Action-FeedbackNeeded
Please provide more details about the issue you are facing.
Labels: -Area-Undefined -Action-FeedbackNeeded Feature-Accessibility
More info here:

We need to fire the right accessibility events when live regions change. WebKit has some support for this already; 

Hans, do you know what event should be fired when a live region changes?

Project Member Comment 3 by, Sep 1 2011
The following revision refers to this bug:

r99161 | | Thu Sep 01 01:44:16 PDT 2011

Changed paths:

Add a big grab bag of missing web accessibility
functionality on Windows. (Much of this will benefit
Mac in a future changelist.) Improvements include
dozens of corrected roles and states for various
elements, improved support for tables with rowspan
and colspan, range control support, and live region

Also adds a new command-line flag to turn on
logging of accessibility events, to help making
this type of bug fixing much easier in the future.

BUG= 89181 , 89185 , 89187 , 89188 , 89202 , 89205 , 89210 , 89212 , 89213 , 89223 
TEST=Manual testing with JAWS, NVDA, AViewer, and accProbe.
Review URL:
Status: Started
This is now somewhat working. Simple tests succeed.

There are a few cases that don't seem to work correctly:
* When a text node changes but no nodes appear or disappear
* When a node is removed and aria-relevant includes "removals"

Needs more investigation. Also, note that sending some sequences of events results in dramatically different results in NVDA and JAWS, be sure to test with both!

This resource explains in more detail how Firefox handles live region updates:
Project Member Comment 6 by, Mar 10 2013
Labels: -Feature-Accessibility Cr-UI-Accessibility
Status: Untriaged
(a11y bug triage: this one goes back to untriage state for further resolution).
Comment 8 by, Feb 28 2014
The reason a lot of cases don't work for NVDA is that Chrome doesn't fire IA2_EVENT_TEXT_INSERTED. We usually use this instead of EVENT_OBJECT_SHOW/REORDER because it works correctly for both text and objects and gives them to us in the correct order and because it's more efficient for text. When the event is fired, IAccessibleText::newText needs to return the new segment at least until NotifyWinEvent returns. (NVDA and other screen readers handle live regions in-process, which means win events can be handled synchronously.) Returning the new segment for longer is okay, but not necessary.
Blockedon: chromium:447962
Status: Fixed
Fixed by  bug 447962 .

I manually tested the attached html and js with JAWS and NVDA.

Chrome passes all of the tests with NVDA, and JAWS behaves the same as it does with Firefox (most tests pass, changes to non-text nodes like images aren't announced).

477 bytes View Download
7.5 KB View Download
Sign in to add a comment