W3C home > Mailing lists > Public > public-html@w3.org > December 2014

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

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Fri, 19 Dec 2014 10:19:51 +0000
Message-ID: <5493FBC7.3090904@splintered.co.uk>
To: public-html@w3.org
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? ;) )

P

On 19/12/2014 09:35, Steve Faulkner wrote:
> thanks Jon, I have set up a wiki page and added your use cases:
> https://www.w3.org/wiki/HTML/accAPI/
>
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
>
> On 18 December 2014 at 17:44, Gunderson, Jon R <jongund@illinois.edu
> <mailto:jongund@illinois.edu>> wrote:
>
>     Steve,____
>
>     __ __
>
>     Where do you want the use cases defined?  In the bug trackers or
>     some wiki?____
>
>     __ __
>
>     Use Case #1: Accessibility Evaluation Tools____
>
>     Accessibility evaluation tools like AInspector Sidebar for Firefox
>     and FAE 2.0 that are based on the OpenAjax Accessibility Evaluation
>     Library can use this API as part of the analysis of the web
>     resources for accessibility information.  Currently these tools must
>     implement their own algorithms to compute the label and role
>     values.  The computed values can be compared to markup to identify
>     coding errors when labeling information like aria-labelledby
>     reference invalid or duplicate ids.____
>
>     __ __
>
>     References:____
>
>     OpenAjax Web Accessibility Evaluation Library____
>
>     http://www.openajax.org/member/wiki/Accessibility ____
>
>     __ __
>
>     Use Case #2: “SkipTo” Javascript Utility ____
>
>     “SkipTo” is a javascript utility to provide keyboard navigation  to
>     a list of headings and landmarks for use in navigating the
>     structured content of a web page. The ability to search the DOM for
>     role (e.g. heading, landmark) and get accessible names through
>     computed label values would make this code immensely simpler (e.g.
>     do not need to replicate code already in the browser for computing
>     these values, similar to get computedStyle).  I am currently working
>     on updating this code to include HTML5 section elements with labels.____
>
>     __ __
>
>     Reference:____
>
>     https://github.com/paypal/skipto____
>
>     __ __
>
>     Jon____
>
>     __ __
>
>     __ __
>
>     __ __
>
>     __ __
>
>     __ __
>
>     *From:*Steve Faulkner [mailto:faulkner.steve@gmail.com
>     <mailto:faulkner.steve@gmail.com>]
>     *Sent:* Thursday, December 18, 2014 10:25 AM
>     *To:* HTMLWG WG
>     *Cc:* Alice Boxhall; David Bolter; Dominic Mazzoni; Richard
>     Schwerdtfeger; Domenic Denicola; Alexander Surkov; W3C WAI Protocols
>     & Formats; James Craig
>     *Subject:* use cases 'DOM needs a way to get element's computed ARIA
>     role and computed label string'____
>
>     __ __
>
>     Can people who are interested in getting this[1] stuff defined and
>     implemented[2] provide use cases?
>
>     [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=27294
>     [2]
>     https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/WToTEn4lveY
>     ____
>
>     --
>
>     Regards
>
>     SteveF____
>
>     __ __
>


-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Friday, 19 December 2014 10:20:14 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:11 UTC