- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Fri, 21 Feb 2014 15:30:16 -0500
- To: James Craig <jcraig@apple.com>
- Cc: Steve Faulkner <faulkner.steve@gmail.com>, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>, HTMLWG WG <public-html@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>
- Message-ID: <CA+epNscdw-T3NqwEWFMxy074gfqY1PLz=-Q_0y8VHzZW3zrSaA@mail.gmail.com>
Thanks, James. Answering inline (if it's out scope of the topic then let's move it somewhere else). On Fri, Feb 21, 2014 at 3:06 PM, James Craig <jcraig@apple.com> wrote: > Ah. There are several reasons and use cases: > > 1. ARIA is used for more than just HTML, (e.g. SVG <g role="table">) > afaik SVG allows HTML inside, it doesn't seem the author have to use ARIA if he wants tabular data for AT in SVG. > 2. Some people need to retrofit tablular data on existing sites that do > not use <table> (e.g. <div role="table">) > What does prevent them to use HTML tables? > 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 > I don't follow these cases, can you elaborate please? > 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 <http://www.w3.org/html/wg/drafts/html/master/> >>> >>> >> >> > >
Received on Friday, 21 February 2014 20:30:44 UTC