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

Re: role=presentation must not be applied to focusable elements

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Thu, 23 Dec 2010 07:51:14 +0000
Message-ID: <AANLkTinf6U=a3k=j4EhYdqvRKrGHkxXFxx2Ss99OakaV@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, David Bolter <dbolter@mozilla.com>, Marco Zehe <marco.zehe@googlemail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>
On Thu, Dec 23, 2010 at 7:37 AM, Maciej Stachowiak <mjs@apple.com> wrote:
> In Safari on Mac, the set of elements that is actually focusable depends on user preferences.

Per spec, you are describing differences in whether the elements "can
be reached using sequential focus navigation". The set of "focusable"
elements includes elements that /cannot/ be reached using sequential
focus navigation.

That is, the spec distinguishes the concept of focusable from the tab
cycle. See especially the normative requirement for negative tabindex:
"The user agent must allow the element to be focused, but should not
allow the element to be reached using sequential focus navigation."

http://dev.w3.org/html5/spec/editing.html#focus

I guess the critical point here is that when an element receives
focus, users must be made aware of what sort of control it is, so
"presentation" makes no sense. So it seems that this wider definition
of "focusable" is more important than the narrow tab cycle sense?

--
Benjamin Hawkes-Lewis
Received on Thursday, 23 December 2010 07:52:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:27 GMT