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

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

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 23 Dec 2010 18:12:12 -0800
Message-ID: <AANLkTin92B9duPO1FsqhrnJr3DYuO61TTJV=WtNNgxnZ@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: 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>
Hi Steve,

In other threads I know that you have argued that many ARIA roles show
be allowed since scripts and CSS could produce the same behavior for
non-AT users. For example in bug 10449 it is argued that role=checkbox
should be allowed on <h1> since you can use CSS and script to make a
<h1> look and act like a checkbox.

However isn't that true in this case too? For example

<input onfocus="blur()">

is purely presentational since you can't interact with it to enter
text. Shouldn't then role=presentation be allowed?

Or do you simply disagree with both and think that bug 10449 should be
WONTFIXed?

/ Jonas

On Wed, Dec 22, 2010 at 2:13 AM, Steve Faulkner
<faulkner.steve@gmail.com> wrote:
> Hi all,
> as per the ARIA spec [1] and implementaion guide [2]
>
> "If an element with a role of presentation is focusable, user agents
> MUST ignore the normal effect of the role and expose the element with
> implicit native semantics, in order to ensure that the element is both
> understandable and operable."
>
> [1]http://www.w3.org/WAI/PF/aria/roles#presentation
> [2] http://www.w3.org/TR/wai-aria-implementation/#mapping_role
>
> I agree with the above, but currently the HTML5 spec allows
> role="presentation" on any element (including focusable elements) and
> this is how it is implemented in Firefox, chrome and IE, they  apply
> the presentation role to focusable elements.
>
> example:
> <p><input type="submit" role="presentation"></p>
>
> IE removes the input from the accessibility tree (Cannot get object
> from Focus event: [Error: AccessibleObjectFromEvent: hr=0x80004005 -
> Unspecified error]) but they are still focusable.
> In firefox the input is still focusable and exposes a role of
> presentation "Role: "presentation" [ BUG? State/Role should not be a
> string ]" (not the same behaviour as for non focusable elements)
> In chrome the focus is moved to the parent element the parent element
> role is exposed.
>
> I think bugs need to be filed on the browsers and on the HTML5 spec,
> anybody disagree?
> --
> 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, 24 December 2010 02:13:07 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:07 UTC