Re: use cases 'DOM needs a way to get element's computed ARIA role and computed label string'

Hi. #2 and #3 use case look very similar, it appears they both want to
iterate over landmarks and roles. The only difference between them is #2 is
in-content JS utility, i.e. part of the web app, but #3 is browser-wise
extension, i.e. applicable for all web pages. I see why they need
computedRole but I'm not sure I get what's computedName for. It'd be good
to give it a more detailed explanation. Are there other examples for
in-content or browser-wise stuff?

Also I think I miss aria-labelledby querySelector idea. It'd be great to
have an example.

Thanks.
Alex.

On Fri, Dec 19, 2014 at 5:41 AM, Steve Faulkner <faulkner.steve@gmail.com>
wrote:

>
> On 19 December 2014 at 10:19, Patrick H. Lauke <redux@splintered.co.uk>
> wrote:
>>
>> Same use cases as Jon mentioned, as far as I'm concerned. As hinted at
>> partially here http://discourse.specifiction.org/t/dom-apis-to-expose-
>> accessible-role-states-properties/693 (are we fragmenting these
>> conversations enough, ya think? ;) )
>>
>
> have captured your use case on wiki, and yeah there is a fragmentation
> issue, I would have stuck with PF origin, but due to restrictive public PF
> mailing list and tracker it makes it difficult for anybody other than PF
> members to contribute, and there are many non PF stakeholders and
> implementers to consider and get input from :-( Hence the reaching around.
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
>