W3C home > Mailing lists > Public > public-pfwg@w3.org > October 2014

Re: Element.getComputedRole()

From: Alexander Surkov <surkov.alexander@gmail.com>
Date: Thu, 16 Oct 2014 20:23:15 -0400
Message-ID: <CA+epNsdRd46iAF5wbxcJuzkZ0dZpXXXeUpr0cc6jLcttd56d7g@mail.gmail.com>
To: David Bolter <dbolter@mozilla.com>
Cc: Dominic Mazzoni <dmazzoni@google.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, PF <public-pfwg@w3.org>
Right, the Accessible should have tree navigation methods for that. I
realize that they can be introduced on Element too but it has a perf
problem (#1) and it introduces a new problem of interface fussiness (#4).

On Thu, Oct 16, 2014 at 8:14 PM, David Bolter <dbolter@mozilla.com> wrote:

> Nit: you didn't address your #2 but I guess that would be done via some
> child accessor?
>
> Cheers,
> D
>
> ----- Original Message -----
> > From: "Alexander Surkov" <surkov.alexander@gmail.com>
> > To: "Dominic Mazzoni" <dmazzoni@google.com>
> > Cc: "Richard Schwerdtfeger" <schwer@us.ibm.com>, "PF" <
> public-pfwg@w3.org>
> > Sent: Thursday, October 16, 2014 6:53:33 PM
> > Subject: 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
> > >>
> > >
> > >
> >
>
Received on Friday, 17 October 2014 00:23:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:10 UTC