W3C home > Mailing lists > Public > public-html@w3.org > March 2012

ARIA roles for hit regions

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Tue, 27 Mar 2012 11:02:33 +0100
Message-ID: <CA+ri+Vk7ZXJexvvcKaYDc7xP7Q7BRU1bWwrSr3qifkOSFwYD2Q@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: HTMLWG WG <public-html@w3.org>
Hi Ian,

In your proposed spec text for hit regions [1] you state the following
role (default null) An ARIA role for accessibility tools to use to
determine how to represent this region, if there is no control.
Can you provide some examples of how this would be used? ie use cases.
you appear to suggest that structural roles (non control roles) can be
used, yet many non control roles require states and properties to be
assigned to be meaningful, yet there is no method provided to assign them,
how will that work?
As ARIA does not provide roles for all roles defined in the various acc
API's how do you propose that any gaps be filled?


[1]
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#hit-regions

-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Tuesday, 27 March 2012 10:03:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:47 GMT