Re: Element.getComputedRole()

I think DOM Element interface extension is misdesign because of reasons:
1) that is performance issue because of potential misuse and overuse, it's
so easy to hit accessibility properties among other methods on Element;
2) it doesn't make sense to expose accessible properties on every DOM
element (like on inaccessible DOM elements) and Element API approach cannot
be used for accessibles having no DOM elements.
3) it's not extensible as part of Element interface, that means you cannot
reuse on text nodes, on document node, on JS accessible trees if they are
ever invented.

I would design an Accessible interface instead following the accessibility
desktop APIs.
interface Accessible {
  string role;
};

Then DOM Window object can be extended by:
interface Window {
  Accessible getAccessibleFor(Node aNode);
};

Thanks.
Alexander.


On Thu, Oct 16, 2014 at 5:51 PM, Dominic Mazzoni <dmazzoni@google.com>
wrote:

> Sure, I think it's a good idea.
>
> How about getComputedAccessibleText next?
>
> In both Blink and WebKit I imagine we'll have to think about efficiency
> when implementing this - typically we enable accessibility lazily and then
> leave it on - at least for that page. We'd want to use the real
> accessibility code to compute this, but then disable accessibility support
> and clean up if it wasn't enabled previously.
>
>
> On Thu, Oct 16, 2014 at 1:19 PM, Richard Schwerdtfeger <schwer@us.ibm.com>
> wrote:
>
>> Hi Dominic,
>>
>> We have an issue to add a getComputedRole() function on  Element. This
>> would help application developers as well as accessibility test tools. Here
>> is the issue:
>>
>> https://www.w3.org/WAI/PF/Group/track/issues/427
>>
>> Would you support implementing this feature in Chrome?
>>
>> Thanks,
>>
>> Rich
>>
>>
>>
>>
>> Rich Schwerdtfeger
>>
>
>