- From: Janina Sajka <janina@rednote.net>
- Date: Tue, 26 Aug 2014 13:53:55 -0400
- To: James Craig <jcraig@apple.com>
- Cc: chaals@yandex-team.ru, Joanmarie Diggs <jdiggs@igalia.com>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Please correct me if I'm wrong, but my understanding is that the long desc spec, as currently in CR, would accomodate implementations that expose longdesc in iframes. As I understand it, a user agent that did that would be conforming. But, the spec does not compell iframes as the only allowable implementation mechanism, as James apparently wants us to do. For my own part I think this illustrates a confusion between means and ends. Janina James Craig writes: > On Aug 25, 2014, at 6:16 AM, chaals@yandex-team.ru wrote: > > > It doesn't convey the requirement that users of magnification software who can use a mouse can access the description (one group of users excluded by James Craig's "iframe" technique), nor various other situations. > > Charles, > > You're misrepresenting that example. Nothing about the iframe technique excludes this set of users. > > You may have missed this text in the example; it was first posted in September 2012: "The iframe approach is also more in line with universal design principles in that it could be scripted to show the alternative frame contents to sighted users upon request, without the need for assistive technology." > > To connect the dots, I spent a few minutes this morning updating the example. It's exactly the same, except now there is a scripted button that toggles the visibility of the image. It works for sighted individuals, screen reader users, zoom users, switch and keyboard users, and everyone else with a browser developed in the last 15 years. > > For the handful of users whose browsers don't support <iframe> or scripting, support for @longdesc is also less likely. For most situations, I recommended the <details>/<summary> technique which is even backwards-compatible with text-only browsers like Lynx, and is a better overall approach than the iframe technique. The iframe example only exists because several longdesc proponents insisted that the external bolt-on description was a requirement for legacy longdesc and "D link" content. A standard rendered link here is a better option too, whether inside or outside of a <figcaption> element to associate it with the image. > > The updated iframe vs longdesc approach (now with visible toggle button). > <http://cookiecrook.com/longdesc/iframe/> > > Other, better examples of longdesc alternatives available in HTML5 today. > <http://cookiecrook.com/longdesc/> > > Thanks, > James Craig -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Email: janina@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols & Formats http://www.w3.org/wai/pf Indie UI http://www.w3.org/WAI/IndieUI/
Received on Tuesday, 26 August 2014 17:55:10 UTC