OSP and tabular data

[Michael S Elledge]

I don't know. Sean? How were the headings marked up when you've 
evaluated it in the past? Which checker did you use?

Mike

Richard Schwerdtfeger wrote:
>
> So, if it is tabular and the headers have meaning why would these 
> tools flag this as presentational? Were the headers mared as <TH>?
>
> Rich
>
>
> Rich Schwerdtfeger
> Distinguished Engineer, SWG Accessibility Architect/Strategist
> Chair, IBM Accessibility Architecture Review Board
> blog: http://www.ibm.com/developerworks/blogs/page/schwer
> Inactive hide details for Michael S Elledge <elledge at msu.edu>Michael S 
> Elledge <elledge at msu.edu>
>
>
>                         *Michael S Elledge <elledge at msu.edu>*
>                         Sent by: fluid-work-bounces at fluidproject.org
>
>                         07/24/2007 03:33 PM
>
> 	
>
> To
> 	
> dcambrid at gmu.edu
>
> cc
> 	
> sakai-dg-ui DG <sakai-dg-ui at collab.sakaiproject.org>, 
> fluid-work at fluidproject.org
>
> Subject
> 	
> Re: OSP and tabular data
>
> 	
>
>
> I'd call it tabular, also. Think of it this way: if you have (or could
> have) column and row headers that ascribe meaning to the content where
> they intersect, you can call it a table. Be sure to: associate the
> headers with the cells (for example, using the <scope> attribute), and
> include a table summary and caption.
>
> Mike
>
> Darren Cambridge wrote:
> > Sean--
> >
> > I think I'd lean towards calling it tabular data. The table structure
> > conveys meaning; it's not merely a way to make things look pleasant. I
> > would guess that switching to a css layout would actually make it less
> > straightforward to convey that meaning in an accessible way. We should
> > probably be looking to the good practices for dealing with tabular
> > data for strategies.
> >
> > Darren
> >
> >
> > Sean Keesler wrote:
> >> I am doing a UI review of the OSP matrix tool (see attched image) and
> >> need a little advice:
> >>
> >> The matrix is big table that is being used as a big grid to represent
> >> the accumulation of information (files and filled out forms) related
> >> to established criteria and levels (rows and columns). The colors of
> >> the table cells convey information about the cell status and the
> >> icons/images convey information about the number and type of
> >> files/forms that have been added to the matrix cell.
> >>
> >> Its sort of tabular data, and its sort of not. Accessibility
> >> validators yell at me because we seem to be using a table for
> >> formatting only...and indeed, much of the information being conveyed
> >> is not being conveyed in a very accessible manner (yes, that is
> >> covered in my review) and I wonder if this is "tabular data" or
> >> not...I need a ruling!
> >>
> >> Would the recommendation of this group be to redesign the matrix
> >> without a table and do some css/div magic? or is this a table of
> >> tabular data? What say ye?
> >>
> >>
> >> [see attachment: "Matrix.png", size: 56698 bytes]
> >>
> >>
> >> ------------------------------
> >> Sean Keesler
> >> Project Manager
> >> The Living SchoolBook
> >> 030 Huntington Hall
> >> Syracuse University
> >> 315-443-3450
> >>
> >>
> >>
> >> Attachments:
> >>
> >> Matrix.png
> >> 
> https://collab.sakaiproject.org/access/content/attachment/9c727d77-ccfb-4b2e-004f-d95fae45c804/Matrix.png 
> >>
> >>
> >> ----------------------
> >> This automatic notification message was sent by Sakai Collab
> >> (https://collab.sakaiproject.org/portal) from the DG: User
> >> Interaction site.
> >> You can modify how you receive notifications at My Workspace >
> >> Preferences.
> >>
> >>
> >
> /(See attached file: 
> elledge.vcf)/_______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: elledge.vcf
Type: text/x-vcard
Size: 136 bytes
Desc: not available
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20070724/413b4c4d/attachment.vcf>