- From: Doug Schepers <schepers@w3.org>
- Date: Mon, 29 Sep 2008 22:52:45 -0400
- To: Al Gilman <Alfred.S.Gilman@IEEE.org>
- CC: "w3c-wai-pf@w3.org PF" <w3c-wai-pf@w3.org>, www-svg <www-svg@w3.org>
Hi, Al- Thanks for your comment. I've added this to our Tracker as ISSUE-2076, and the SVG WG will discuss it and get back to you soon. Thanks- -Doug, on behalf of the SVG WG Al Gilman wrote (on 9/28/08 9:01 PM): > > > As regards WAI-ARIA alone, the answer should be 'no.' In our best > practices we instruct script authors not to change the role of an > element, but rather to destroy the DOM object for that element and > create a new object with the new role. > > This is because the consumers of the accessibility APIs expect the role > of a node to be static, just as xml:lang is not animatable in SVG. > > SVG documents that animate the value of @role would confuse the AT > consumers of the accessibility APIs. I suppose that the browser could > trap these > property-change events and destroy and create the object in the > accessible object graph, but then... > > Can anybody come up with a use case for animating the @role value using > the currently-defined roles from either the XHTML Role Module or WAI-ARIA? > > Al > /self > > http://www.w3.org/TR/2008/WD-xhtml-role-20080407/ > http://www.w3.org/WAI/PF/aria/ >
Received on Tuesday, 30 September 2008 02:53:22 UTC