- From: Steven Faulkner <faulkner.steve@gmail.com>
- Date: Tue, 24 Aug 2010 12:15:12 +0100
- To: HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
- Message-ID: <AANLkTinky5xMhEVLO6R0mjK+amP4TJ4qHt-zCnvVwe_s@mail.gmail.com>
remailing with example code sans extraneous role and tabindex code: On 24 August 2010 12:09, Steven Faulkner <faulkner.steve@gmail.com> wrote: > Hi all, > an idea: > > using the summary /details elements to provide a long description for an > image: > > > - image goes in the <summary> > - long description in <details> > - use of longdesc attribute on image provides indication to browser/AT > that details/summary is being used for the specific purpose of providing a > long description. > - longdesc attribute with URL value (longdesc="URL") provided for > backwards compatibility (suggest deprecated in HTML5) > - longdesc attribute without an URL "longdesc" be specced as an > indicator that a long description is present when image is sole content of > the summary element. > > example code: > > <details> > <summary ><img src="images/table.gif" alt="Average rainfall in > millimetres by country and season." width="407" height="341" > longdesc="details.html#table"></summary> > > <table border="1" id="table"><caption>Rainfall in millimetres by Country > and Season.</caption><tr> <td></td><th scope="col">UK</th><th > scope="col">Japan</th><th scope="col">Australia</th></tr><tr> <th > scope="row">Spring</th><td>5.5</td><td>2.4</td><td>2</td></tr><tr> <th > scope="row">Summer</th><td>4.5</td><td>3.4</td><td>2</td></tr><tr> <th > scope="row">Autumn</th><td>3.5</td><td>1.8</td><td>1.5</td></tr><tr> <th > scope="row">Winter</th><td>1.5</td><td>1.2</td><td>1</td></tr></table> > > </details> > > sort of working example > http://www.paciellogroup.com/blog/misc/details.html (haven't had time to > work out glitches, but gives an idea of how it could work, doesn't work in > IE yet. note: scripting would not be required once details/summary > implemented by browsers). > resolves issues of: > > - providing *standardized* method for a programnmatically associated > long description > - provides it inline next to the image > - only displayed on user request > - does not clutter design (note example does not a disclosure triangle > as is suggested for details/summary in spec, but this would not clutter > desigh , i don't think) > - deprecates current longdesc use, but provides for backwards compat > and continued use of longdesc attribute > - details could conatin a.n <iframe> to display long descriptions > external to the page. > - long desc available to anybody who wants it. > > > > -- > 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 > > -- 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
Received on Tuesday, 24 August 2010 11:16:06 UTC