> > 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.
Received on Tuesday, 19 May 2015 22:58:51 UTC