- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Wed, 17 Dec 2008 16:07:36 -0600
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- Cc: Aaron M Leventhal <aleventh@us.ibm.com>, Joseph Scheuhammer <clown@utoronto.ca>, wai-xtech@w3.org, wai-xtech-request@w3.org
- Message-ID: <OF10BDEECD.02C7EA2F-ON86257522.007914D3-86257522.00798B5A@us.ibm.com>
Boris, The AT needs to be able to know when parts of the document change to support live regions as well. There needs to be some formal way for the AT to register and be notified of document mutation events whether they are through the DOM API or not. There are platform accessibility API that can be used to allow the AT to listen for these types of change events and not necessarily by accessing the DOM. I don't believe this belongs in the ARIA specification but rather the user agent implementers guide. Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist blog: http://www.ibm.com/developerworks/blogs/page/schwer Boris Zbarsky <bzbarsky@MIT.EDU > To Sent by: Joseph Scheuhammer wai-xtech-request <clown@utoronto.ca> @w3.org cc Aaron M Leventhal/Cambridge/IBM@IBMUS, 12/09/2008 03:46 wai-xtech@w3.org, PM wai-xtech-request@w3.org Subject Re: ARIA should require DOM mutation event support for compliance. Joseph Scheuhammer wrote: > Webapp scripts are written to listen for various events, and handle as > appropriate. Having to also poll for changes that an external agent may > or may not make is not an option. Sure. >> Even more alternately, authors could ignore the SHOULD-level requirement. > Even if they do, the possibility remains that ATs might change aria-* > attributes, and the scripts need to handle this. Agreed. Just saying that this doesn't mean that a UA can't ARIA-compliant without implementing mutation events. -Boris
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: pic06905.gif
- image/gif attachment: ecblank.gif
Received on Wednesday, 17 December 2008 22:08:19 UTC