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

Making ARIA and native HTML play better together

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Thu, 7 May 2015 06:42:06 +0100
Message-ID: <CA+ri+V=zhoYRyNR3b0_MpekcGVbhbmo0yK8waEGvr0FujDYYdg@mail.gmail.com>
To: HTMLWG WG <public-html@w3.org>
Cc: Chaals from Yandex <chaals@yandex-team.ru>, LĂ©onie Watson <lwatson@paciellogroup.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Alice Boxhall <aboxhall@google.com>
On another thread recent thread, leonie and chaals [3] talked about adding
behaviours to ARIA. Here are a few ideas:

1. When a role is used that matches the default implicit semantics of
labelable HTML elements [1] use of the label element will result in the
same behaviour as the native element and a <label>.

<span role="checkbox" id="customcheck"></span> <label for="customcheck">i
like this idea</label>

User able to click on label to check/uncheck

2. roles that match the default implicit semantics of interactive elements
are focusable (without need to explicitly set tabindex)

<div role="button">press me</div>

will be included in the focus order.

3. roles that match the default implicit semantics of interactive elements
[2] inherit the interaction behaviour of the native elements

<div role=button>press me</div>
can be activated the same way a html <button> element can be:.
via space, enter ,click , touch or whatever.

Why? reduce manual labour of web devs. provide more consistent cross
browser behaviours for custom UI. Make custom UI more robust out of the box.

Review at your leisure, respond at will.

[1] http://www.w3.org/TR/html51/semantics.html#category-label
[2] http://www.w3.org/TR/html51/dom.html#interactive-content-2


HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
Received on Thursday, 7 May 2015 05:43:14 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:13 UTC