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

hit regions not tied to DOM elements

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Fri, 4 May 2012 10:48:58 +0100
Message-ID: <CA+ri+VkaYxP6E9P+9sBVWGar1eLwVw6cfoNi33dUd3mWEuJErw@mail.gmail.com>
To: "Edward O'Connor" <eoconnor@apple.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Frank Olivier <Frank.Olivier@microsoft.com>, Cynthia Shelly <cyns@microsoft.com>, Anne van Kesteren <annevk@opera.com>
Cc: HTMLWG WG <public-html@w3.org>, Ian Hickson <ian@hixie.ch>
Hi all,
reading through the IRC logs from yesterday in reference to hit regions not
associated with HTML DOM elements:
http://krijnhoetmer.nl/irc-logs/html-wg/20120503

   - richardschwerdtfe: these things are lightweight
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1098> [22:29]
   <timeless> ... and they might belong to the DOM?
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1099> [22:29]
   <timeless> hober: there are two things
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1100> [22:29]
   <timeless> ... elements themselves
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1101> [22:29]
   <timeless> ... or a description of a javascript object
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1102> [22:29]
   <timeless> ... in terms of wiring up to the Accessibility Tree
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1103> [22:29]
   <timeless> ... that could be done by the UA
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1106> [22:30]
   <timeless> ... if one hit region is contained in another
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1107> [22:30]
   <timeless> ... that could get complicated
   - [22:30] <timeless> richardschwerdtfe: how do you make those elements
   keyboard navigable?
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1109> [22:30]
   <timeless> anne: the browser does that
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1110> [22:30]
   <timeless> ... hit regions would be added to focus order
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1111> [22:30]
   <timeless> richardschwerdtfe: it's not just fully defined then?
   - # <http://krijnhoetmer.nl/irc-logs/html-wg/20120503#l-1112> [22:31]
   <timeless> hober: i'm sure the editor would like to hear


I get the impression that for hit regions not associated with DOM elements
that they also will be focusable

>  richardschwerdtfe: how do you make those elements keyboard navigable?
>
anne: the browser does that
>


If so, this is not what the spec says and what hixie has stated:

* Hixie, How are states and properties added to the objects not bound to
> DOM elements with roles assigned? How is focus exposed for objects not
> bound to DOM elements? - Stevef*
>
> *Use elements if you need states, properties, or focus. -Hixie*
>
Can you provide examples of roles that don't require states or properties?
> - Stevef"

 http://wiki.whatwg.org/wiki/Canvas

So is the suggestion to enable focus on hit regions not associated with DOM
elements counter to whats in the spec and hixies position? It appears to be.

-- 
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 Friday, 4 May 2012 09:49:52 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:52 UTC