Re: Use and abuse of @summary

Hi patrick, good point, with which i concur with, I also disagree with
marking up layout tables with summary="", but as you pointed out all WCAG
2.0 techniques are advisory only.

regards
stevef

2009/2/23 Patrick H. Lauke <redux@splintered.co.uk>

> On Mon, Feb 23, 2009 at 11:32 AM, Lachlan Hunt <lachlan.hunt@lachy.id.au>
> wrote:
>
>
> > It also doesn't seem to fit the description in WCAG2 about how to use the
> > summary attribute:
> >
> > "... to provide a brief overview of how data has been organized into a
> >  table or a brief explanation of how to navigate the table."
> >
> > http://www.w3.org/TR/WCAG20-TECHS/H73.html
>
> Worth noting that WCAG 2 techniques are advisory, rather than
> mandatory. Personally, I disagree with this technique's particular
> suggested use of summary for simple tables...and, as it's only
> advisory, that's fine...as long as i and my users are happy that the
> actual mandatory SC 1.3.1 is satisfied.
>
> P
> --
> Patrick H. Lauke
> ______________________________________________________________
> re·dux (adj.): brought back; returned. used postpositively
> [latin : re-, re- + dux, leader; see duke.]
>
> www.splintered.co.uk | www.photographia.co.uk
> http://redux.deviantart.com | http://flickr.com/photos/redux/
> ______________________________________________________________
> Co-lead, Web Standards Project (WaSP) Accessibility Task Force
> http://webstandards.org/
> ______________________________________________________________
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html