- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Fri, 21 Feb 2014 14:30:08 -0600
- To: surkov.alexander@gmail.com
- Cc: Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>, W3C WAI Protocols & Formats <public-pfwg@w3.org>, James Craig <jcraig@apple.com>
- Message-ID: <OFC808C657.71531D63-ON86257C86.007052F5-86257C86.0070A012@us.ibm.com>
I want to reiterate James points. Additionally, we have gaps in HTML5
intrinsic host language semantics which we are defining now for both HTML5
and SVG2.
Note: With HTML5.1 and ARIA 1.1 you will not need to put role="table" on a
table element or role="row" on a <tr>. This will continue to reduce
footprints.
Rich
Rich Schwerdtfeger
From: James Craig <jcraig@apple.com>
To: Alexander Surkov <surkov.alexander@gmail.com>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, W3C WAI Protocols &
Formats <public-pfwg@w3.org>, HTMLWG WG <public-html@w3.org>,
Richard Schwerdtfeger/Austin/IBM@IBMUS
Date: 02/21/2014 02:08 PM
Subject: Re: addition of HTML role requirement mappings
Ah. There are several reasons and use cases:
1. ARIA is used for more than just HTML, (e.g. SVG <g role="table">)
2. Some people need to retrofit tablular data on existing sites that do not
use <table> (e.g. <div role="table">)
3. The 1:1 role mapping to HTML is also required for presentation
inheritance. (e.g. <table role="presentation">)
4. The 1:1 role mapping will be useful once we add the Element.computedRole
interface. PFWG-ISSUE-427
HTH,
James
On Feb 21, 2014, at 10:33 AM, Alexander Surkov <surkov.alexander@gmail.com>
wrote:
No. As I understood there's a suggestion to introduce ARIA table and
table cell roles duping HTML tables semantics. That was looking the
bloat for me since I don't see any use case for that.
On Fri, Feb 21, 2014 at 1:24 PM, James Craig <jcraig@apple.com>
wrote:
Are you saying grids are the bloat, or the 1:1 mappings against
html:table is the bloat?
On Feb 21, 2014, at 9:38 AM, Alexander Surkov <
surkov.alexander@gmail.com> wrote:
If table and table cell ARIA roles are supposed to be a part
of browser implementation then it looks like spec
overbloating with no usecase.
On Fri, Feb 21, 2014 at 12:22 PM, James Craig <
jcraig@apple.com> wrote:
Yeah, I think this illustrates that we need to get table and
cell roles in soon for ARIA 1.1. cell and gridcell can
probably just be aliases, but table and grid are
semantically different.
On Feb 21, 2014, at 5:17 AM, Steve Faulkner <
faulkner.steve@gmail.com> wrote:
Hi all,
hixie has added some role requirements and
restrictions in the whatwg spec that will soon come
up for cherry picking [1] to the HTML 5.1 spec.
previously we determined that some of the following
were not appropriate, so am asking for ARIA folk to
review:
note: implementers MUST map to these roles and authors
are restricted to applying the roles listed for each
element (authors can also apply role=presentation).
strong semantics:
table element grid role
tbody element rowgroup role
td element gridcell role
tfoot element rowgroup role
thead element rowgroup role
tr element row role
implicit semantics:
th element gridcell role Role must be either columnheader, rowheader, or gridcell
[1] https://github.com/w3c/html/commit/5b5ad72b8e7bb36ab863effc942829eef82fe3c4#commitcomment-5449710
--
Regards
SteveF
HTML 5.1
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: ecblank.gif
Received on Friday, 21 February 2014 20:30:50 UTC