W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > January 2014

Re: Re: Techniques for WCAG 2.0 H45 longdesc: Missing on-page description example ( LC-2791) ( LC-2851)

From: <akirkpat@adobe.com>
Date: Thu, 16 Jan 2014 20:57:37 +0000
Message-Id: <E1W3u0P-0008RQ-Dj@jessica.w3.org>
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: public-comments-wcag20@w3.org,Andrew Kirkpatrick <akirkpat@adobe.com>, Joshue O Connor <joshue.oconnor@cfit.ie>, John Foliot <john@foliot.ca>
 Dear Laura Carlson ,

The Web Content Accessibility Guidelines Working Group has reviewed the
comments you sent [1] on the Last Call Working Draft [2] of the Techniques
for WCAG 2.0 published on 5 Sep 2013. Thank you for having taken the time
to review the document and to send us comments!

The Working Group's response to your comment is included below.

Please review it carefully and let us know by email at
public-comments-wcag20@w3.org if you agree with it or not before 21 January
2014. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Web Content Accessibility Guidelines Working Group,
Michael Cooper
W3C Staff Contact

 1.
http://www.w3.org/mid/CAOavpvftVNKiX0KpBOKeHZrh99tkjsXh5QXQQEi_cUNVBnkOdA@mail.gmail.com
 2. http://www.w3.org/TR/2013/NOTE-WCAG20-TECHS-20130905/


=====

Your comment on H45: Using longdesc:
> Thank you very much for agreeing to provide on-page longdesc syntax in
> order to help people understand how it works and what limitations exist.
> I agree with the direction you are taking but suggest helping authors to
> overcome any limitations by incorporating a end-point solution into
> H45's verbiage and example as well as pointing out the advantages of
> using a separate resource by changing:
> 
> 
> H45: http://www.w3.org/TR/WCAG-TECHS/H45.html
> 
> Authors can provide a description for an image by including text in a
> separate resource or within the text of the page containing the image.
> <ins>An advantage of using a separate resource for the description is
> that it is easily reusable for multiple instances of the same image, it
> does not add on-page visual clutter to the original document, and the
> description's end-point is self evident.</ins> An advantage of providing
> the description within the same page as the image is that all users can
> access the description. A limitation of <del>this</del><ins>the
> on-page</del> method, as well as in providing multiple descriptions on a
> single separate page, is that current implementations supporting
> longdesc <del>read all text on the page that follows the start of the
> long description</del><ins>do not identify the long description's
> end-point</ins>. <del>As a result, an end user may hear the long
> description and all content on the page following it, without knowing
> where the long description is intended to end unless authors provide
> text to help users identify the end-point of the
> description.</del><ins>Authors can solve this by providing a well-formed
> description, which identifies the where the description ends.</ins>
> 
> [On-page Example]
> (suggested change is in addition of H3 and P inside the div#desc)
> 
> <img longdesc="thispage.html#desc"
>  alt="Line graph of the number of subscribers"
>  src="http://www.company/images/graph.png">
> <div id="desc">
>  <h3>Long Description: Line graph of the number of subscribers</h3>
>  <!-- Full Description of Graph -->
>  <p>Long description ends.</p>
> <div>
> 
> 
> Laura also suggests various resources for inclusion, below:
> 
> Related Resources:
> 
> Description Available in a Separate Document Provides Efficiency
> http://www.d.umn.edu/~lcarlson/research/constriants/separate-doc.html
> 
> Forced Visual Encumbrance Adds Visual Clutter
>
http://www.d.umn.edu/~lcarlson/research/constriants/visual-encumbrance.html
> 
> In addition WCAG WG may want to consider demonstrating to authors how to
> provide an actual long description by replacing the comment: <!-- Full
> Description of Graph --> with markup.
> 
> For example:
>
http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/examples/pages/graph2.html#desc
> 
> More longdesc Examples:
> 
>
http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/examples/long.html
> 
>
http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/104ex1_fixed.html#browsers_stats
> 
>
http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/104ex1_fixed.html#painting


Working Group Resolution (LC-2851):
Thank you for your comment.  

We will implement the suggested changes to the second paragraph of the
description for H45 (http://www.w3.org/TR/WCAG-TECHS/H45.html).  We will
also implement the suggested change to the example and add links to
relevant resources.


@@Authors can provide a description for an image by including text in a
separate resource or within the text of the page containing the image.
<ins>An advantage of using a separate resource for the description is that
it is easily reusable for multiple instances of the same image, it does not
add on-page visual clutter to the original document, and the description's
end-point is apparent to the user.</ins> An advantage of providing the
description within the same page as the image is that all users can access
the description. A limitation of <del>this</del><ins>the on-page</del>
method, as well as in providing multiple descriptions on a single separate
page, is that current implementations supporting longdesc <del>read all
text on the page that follows the start of the long
description</del><ins>do not identify the long description's
end-point</ins>. <del>As a result, an end user may hear the long
description and all content on the page following it, without knowing where
the long description is intended to end unless authors provide text to help
users identify the end-point of the description.</del><ins>Authors can
solve this by providing a well-formed description, which identifies the
where the description ends.</ins>

[On-page Example]
(suggested change is in addition of H3 and P inside the div#desc)

<img longdesc="thispage.html#desc"
alt="Line graph of the number of subscribers"
src="http://www.company/images/graph.png">
<div id="desc">
<h3>Long Description: Line graph of the number of subscribers</h3>
<!-- Full Description of Graph -->
<p>Long description ends.</p>
<div>

Resources
Add listing of tools with support for Longdesc:
http://www.d.umn.edu/itss/training/online/moodle_downloads/accessibility_104/longdesc_tools.html



----
Received on Thursday, 16 January 2014 20:57:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:17 UTC