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

Hi John,

note the CCs included PF up to Pats response.

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>

On 19 December 2014 at 19:15, John Foliot <john@foliot.ca> wrote:
>
> Steve, Patrick, all,
>
>
>
> Suggestion that this could happen in parallel with WAI-IG or WAI XTECH
> mailing lists, both are open and public, and I would suspect that most
> members of PF watch one or both of those lists.  Just a thought.
>
>
> WAI XTECH: wai-xtech@w3.org
> (This is a public list for discussion of items within scope of the
> Protocols and Formats Working Group. To subscribe to this list, send email
> to wai-pf-call@w3.org.)
>
>
>
> WAI IG: w3c-wai-ig@w3.org
>
> (To subscribe to this list , send an email to w3c-wai-ig-request@w3.org)
>
>
>
> JF
>
>
>
> *From:* Steve Faulkner [mailto:faulkner.steve@gmail.com]
> *Sent:* Friday, December 19, 2014 2:41 AM
> *To:* Patrick H. Lauke
> *Cc:* HTMLWG WG
> *Subject:* Re: use cases 'DOM needs a way to get element's computed ARIA
> role and computed label string'
>
>
>
>
>
> 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/>
>