Re: aria-interactive and the authoring/debug process problems

> If the table is static -- non-interactive, then don't make it a 
> grid. In HTML this is entirely possible since there is a table element.

Dominic Mazzoni <dmazzoni@google.com> wrote on 05/19/2015 03:58:23 PM:
> What about SVG?

For this and the other situations you describe, We need something in ARIA. 
Current consensus in the meetings has been forming around grid with 
aria-interactive=false as opposed to adding table roles.

> If you think we shouldn't have role=table because it's already in 
> html, then why do we have role=heading or role=list? Those are 
> already in HTML too - but they can be really useful when 
> retrofitting accessibility.

I was not saying that; Sorry I was not clear. 
I agree we need some ARIA way of indicating an element is a static table.

Matt King
IBM Senior Technical Staff Member
I/T Chief Accessibility Strategist
IBM BT/CIO - Global Workforce and Web Process Enablement 
Phone: (503) 578-2329, Tie line: 731-7398
mattking@us.ibm.com



From:   Dominic Mazzoni <dmazzoni@google.com>
To:     Matthew King/Fishkill/IBM@IBMUS, 
Cc:     "Gunderson, Jon R" <jongund@illinois.edu>, "W3C WAI Protocols & 
Formats" <public-pfwg@w3.org>, Alexander Surkov 
<surkov.alexander@gmail.com>
Date:   05/19/2015 03:58 PM
Subject:        Re: aria-interactive and the authoring/debug process 
problems



Dominic, that is the definition of grid; grid is always interactive. There 
is no need for aria-interactive to say that a grid is interactive; it is 
by default.

No disagreement.

If the table is static -- non-interactive, then don't make it a grid. In 
HTML this is entirely possible since there is a table element.

What about SVG?

Plus, I've seen cases where authors wish to create a logical table but the 
HTML <table> element doesn't meet their needs. One example is a large 
table where the row headers are always present but the cells are inside an 
element that scrolls. Or there's simply the case where content has already 
been created 

If you think we shouldn't have role=table because it's already in html, 
then why do we have role=heading or role=list? Those are already in HTML 
too - but they can be really useful when retrofitting accessibility.

> Here's the original bug I filed: 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=27866

Unfortunately, bug 27866 was not on the agenda or part of the discussion 
of aria-interactive. Bug 27866 is for a completely different kind of 
issue.

That is unfortunate. I'll try to move all of the bugs I've reported to the 
right place.