- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Thu, 19 Mar 2015 15:41:10 +0000
- To: Joanmarie Diggs <jdiggs@igalia.com>, Joseph Scheuhammer <clown.idi@gmail.com>
- CC: Joseph Scheuhammer <clown@alum.mit.edu>, PF <public-pfwg@w3.org>, Alexander Surkov <surkov.alexander@gmail.com>
> Fair enough regarding proceeding. But how do we handle things like hidden rows and columns? A real-world use case is the Google Docs spreadsheet. The use of aria-hidden on a row or set of column cells from top to bottom should work I would think, which can be programmatically set. Would this make sense? Developers would need to exercise due diligence to make sure that the right column cells included it though. -----Original Message----- From: Joanmarie Diggs [mailto:jdiggs@igalia.com] Sent: Thursday, March 19, 2015 8:10 AM To: Joseph Scheuhammer Cc: Joseph Scheuhammer; PF; Alexander Surkov Subject: Re: Action-1293 Proposal Hey Joseph. On 03/19/2015 10:42 AM, Joseph Scheuhammer wrote: > If there are gaps, then something else is needed :-). I think that it can be solved by specifying the colindex on each cell rather than making it optional/imply-able. > So, before proceeding, I think we need to decide if ARIA is going to > support non-contiguous data sets. IMHO, this adds a layer of > complexity that will make authors lives more difficult, and likely > make for badly marked up tables and grids. Fair enough regarding proceeding. But how do we handle things like hidden rows and columns? A real-world use case is the Google Docs spreadsheet. --joanie
Received on Thursday, 19 March 2015 15:41:47 UTC