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: Wed, 22 Dec 2010 15:58:37 +0000
Message-ID: <AANLkTi=0MT5KsA7JWf3pEj0gRVbOiyP13jmiB7asQRtt@mail.gmail.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, Cynthia Shelly <cyns@microsoft.com>, David Bolter <dbolter@mozilla.com>, Marco Zehe <marco.zehe@googlemail.com>, HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Wed, Dec 22, 2010 at 2:29 PM, Richard Schwerdtfeger
<schwer@us.ibm.com> wrote:
>
> Being pragmatic, we are not going to be able to validate a document based on what is focusable because due to support for tabindex="-1".

I don't follow.

Elements with tabindex="-1" are programmatically focusable but not in
the default focus order. It doesn't make much sense for elements to be
focusable and presentational.

So why would this be a problem for machine validation?

> So, I don't think a bug needs to be generated. The ARIA spec. is clear. We absolutely need to create a normative implementation guide for HTML 5 and ARIA. It will include things like this.

Currently, the HTML5 spec defines what roles may be placed on what, so
this is the right place to do this if we're going to do it.

If it's the wrong place, then that's a broader issue.

--
Benjamin Hawkes-Lewis
Received on Wednesday, 22 December 2010 15:59:16 GMT

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