issue-444

Do IE and FF modify the DOM?

DB: FF does modify the DOM in the case of aria-activedescendant and aria-selected.

RS: don't think ATs are going to use the API to modify selection

CS: seems like modifying the DOM is the right thing to do

<davidb> I don't like modifying the DOM.

RS: the reason it's a problem is that authors are in complete control - track keyboard events
... but authors are not looking for changes to active-descendant
... are you modifying the DOM or doing styling?

DB: FF does modify the DOM for aria-selected

CS: seems like it is a bad idea to not have the DOM in sync with what the AT thinks

RS: ATs are not using API to change selection, web authors won't know it's changed
... to make it work end to end, we need the device independent events to notify the web app

CS: but that WG is not even off the ground yet

RS: are we going to take WAI-ARIA back to Last Call because of this?

DB: what about removal of features from ARIA? does that require another LC?

AS: we can only remove something if there is an Ed Note that says the feature is at risk and might be removed.

DB: so if we have Safari and IE that would be two implementations

RS: would like to do a point release of WAI-ARIA right after this to include the device independent events strategy

CS: but the DI events will take two years

RS: all agree we need DI events - reduces work for developers

CS: agree it is needed but if it went to LC tomorrow, it would be two years before it would be a Rec

RS: essential for mobile

CS: agree

RS: if we go back to LC, we would change the spec and remove the MUST which would raise a red flag with the WHATWG

<scribe> ACTION: Cynthia to find out what IE does [recorded in http://www.w3.org/2011/08/04-aapi-minutes.html#action01]

RS: voice reco technologies are not using APIs to change selection. They send keyboard and mouse events.

AS: what about using an API to change focus?

RS: not sure

AS: sounds like we need to poll the AT vendors to see if anyone is using the AAPI to change focus or selection

CS: even if they're not, this forces them to go to the DOM rather than using the API
... would like to find out how bad the issue is and publish an errata ASAP after WAI-ARIA goes to Rec

skip to main content

RS: need a feature in the browsers to get to the main landmark
... can IE put this in IE 10?

CS: IE doesn't have document structure navigation feature - not sure where they would put it
... would love for somebody to do a plug-in

RS: if we could have a skip to main content keyboard function would be ideal

CS: changes to UI at this point have a low chance of getting in

back to issue-444

AS: how does it work if the UA modifies the COM for aria-activedescendant?

RS: today can use DOMAttrModified event but that is going away

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/be two releases/be two implementations/
No ScribeNick specified.  Guessing ScribeNick: Andi
Inferring Scribes: Andi

WARNING: No "Present: ... " found!
Possibly Present: AS CS DB RS aapi cyns davidb left
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 04 Aug 2011
Guessing minutes URL: http://www.w3.org/2011/08/04-aapi-minutes.html
People with action items: cynthia

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.