There are 5 comments (sorted by their types, and the section they are about).
question comments
general comment comments
Comment LC-2787 : JCraig-Examples where longdesc inappropriate
Commenter: James Craig <jcraig@apple.com> (archived message ) Context: 3.0 Implementation
Status: open
proposal
pending
resolved_yes
resolved_no
resolved_partial
other
assigned to Nobody
Allan, Jim
Bolter, David
Brewer, Judy
Cain, Sally
Cooper, Michael
Cotton, Paul
Diggs, Joanmarie
EVAIN, Jean-Pierre
Faulkner, Steve
Foliot, John
Hickson, Ian
Kardell, Brian
Kiss, Jason
Kobayashi, Masatomo
Le Hégaret, Philippe
Lund, Bob
MacDonald, David
Mann, Jatinder
McCathie Nevile, Charles
O'Connor, Joseph Karr
Quin, Liam
Ruby, Sam
Schnabel, Stefan
Taylor, Suzanne
Watson, Mark
Type: substantive
editorial
typo
question
general comment
undefined
Comment :I have an additional suggestion that I believe would help the acceptance of this document within the general working group. Add an informative section detailing several of the many cases where it is inappropriate to use @longdesc. For example…
1. @longdesc is inappropriate when an EPUB footnote is sufficient.
2. @longdesc is inappropriate for Math. Use MathML instead.
3. @longdesc is inappropriate for SVG graphics. Make the SVG DOM accessible instead.
4. @longdesc is inappropriate for graphics of tabular data. Use an accessible table instead.
More examples at http://cookiecrook.com/longdesc/
These should probably be added to the WCAG 2.0 Techniques documents as well.
Related issues: (space separated ids)
WG Notes:
Resolution: (Please make sure the resolution is adapted for public consumption)
Comment LC-2788 : MTurvey-Additional example longdesc inappropriate
Commenter: Matthew Turvey <mcturvey@gmail.com> (archived message ) Context: 3.0 Implementation
Status: open
proposal
pending
resolved_yes
resolved_no
resolved_partial
other
assigned to Nobody
Allan, Jim
Bolter, David
Brewer, Judy
Cain, Sally
Cooper, Michael
Cotton, Paul
Diggs, Joanmarie
EVAIN, Jean-Pierre
Faulkner, Steve
Foliot, John
Hickson, Ian
Kardell, Brian
Kiss, Jason
Kobayashi, Masatomo
Le Hégaret, Philippe
Lund, Bob
MacDonald, David
Mann, Jatinder
McCathie Nevile, Charles
O'Connor, Joseph Karr
Quin, Liam
Ruby, Sam
Schnabel, Stefan
Taylor, Suzanne
Watson, Mark
Type: substantive
editorial
typo
question
general comment
undefined
Comment :I'd also add:
5. @longdesc is inappropriate when a normal link is sufficient. Example:
<a href="descrip"><img src="pic" alt="*the purpose of the link*"></a>
-Matt
Related issues: <B6A6F56A-C7A3-4A59-860C-4276A33B2BCD@apple.com>
(space separated ids)
WG Notes: Wanted to treat this as a separate comment. It adds another example of when it is "inappropriate" to use longdesc.
Resolution: (Please make sure the resolution is adapted for public consumption)
editorial comments
Comment LC-2789 : Gmoreau-More cleary define "available" RE longdesc links
Commenter: Guy Moreau <gmyx@gpws.ca> (archived message ) Context: in
Status: open
proposal
pending
resolved_yes
resolved_no
resolved_partial
other
assigned to Nobody
Allan, Jim
Bolter, David
Brewer, Judy
Cain, Sally
Cooper, Michael
Cotton, Paul
Diggs, Joanmarie
EVAIN, Jean-Pierre
Faulkner, Steve
Foliot, John
Hickson, Ian
Kardell, Brian
Kiss, Jason
Kobayashi, Masatomo
Le Hégaret, Philippe
Lund, Bob
MacDonald, David
Mann, Jatinder
McCathie Nevile, Charles
O'Connor, Joseph Karr
Quin, Liam
Ruby, Sam
Schnabel, Stefan
Taylor, Suzanne
Watson, Mark
Type: substantive
editorial
typo
question
general comment
undefined
Comment :In my opinion, 3.0.3 User Agents (UAs) is deficient. While it requires
UAs to make the link available, it arguably does not require anything
more than access to the source code.
My rational is that access to the source code is a regular user
interface. Access to source code is provided in most if not all UAs. The
word 'available' does not specify what we can do with the link or how we
use it.
As a result of using the word 'available', I feel there is nothing in
3.0.3 that would compel UAs to make easy access to longdesc links
possible. I feel it needs to be more prescriptive to UAs that everyone
should benefit from longdescs.
I am suggesting a change or addition:
"If the longdesc value is valid, User agents must make the link
actionable or able to be activated to all users through the regular user
interface(s) similar to regular links."
Choose the wording the best describes how a regular link is activated.
A Non-normative example: Add to the context menu of the image a 'Go to
long description' menu item.
I hope my opinion is clear and my goal is entice UAs to make longdesc
readily available to all users. I also hope that you agree with me.
Thank you.
Guy Moreau
@gmyxgpws (twitter)
Related issues: (space separated ids)
WG Notes: Chaals has sent a reply that attempts to close this issue:
http://lists.w3.org/Archives/Public/public-html-a11y/2013Jul/0043.html
Resolution: (Please make sure the resolution is adapted for public consumption)
Comment LC-2786 : Jan-Editorial-ATAG
Commenter: Richards, Jan <jrichards@ocadu.ca> (archived message ) Context: 3.0 Implementation
Status: open
proposal
pending
resolved_yes
resolved_no
resolved_partial
other
assigned to Nobody
Allan, Jim
Bolter, David
Brewer, Judy
Cain, Sally
Cooper, Michael
Cotton, Paul
Diggs, Joanmarie
EVAIN, Jean-Pierre
Faulkner, Steve
Foliot, John
Hickson, Ian
Kardell, Brian
Kiss, Jason
Kobayashi, Masatomo
Le Hégaret, Philippe
Lund, Bob
MacDonald, David
Mann, Jatinder
McCathie Nevile, Charles
O'Connor, Joseph Karr
Quin, Liam
Ruby, Sam
Schnabel, Stefan
Taylor, Suzanne
Watson, Mark
Type: substantive
editorial
typo
question
general comment
undefined
Comment :Nice work. I just have a few suggestions:
1. Double-check the consistency of capitalization in "Requirements for an Image Description functionality". Some items have each word capitalized while others do not and then some have different capitalization in different places ("Simple Return" ). My preference is usually for less capitalization.
2. re: the section referencing ATAG 2.0 that is marked with " ISSUE: This doesn't seem a great reference - is there anything better? This is tracked in bug 21501 and its dependent bugs. Unless a proposal for improvement is made and accepted this bug will simply be closed after Last Call."
Right now it points to:
" Implementing PRINCIPLE B.3: Authors must be supported in improving the accessibility of existing content " (http://www.w3.org/TR/ATAG20-TECHS/#principle_b3)
...which is probably too general.
There are other anchors in "Implementing ATAG 2.0" that provide more specific information. This is probably the most specific:
http://www.w3.org/TR/ATAG20-TECHS/#prompt-long-description
Also, these two sections that explain how checking and repair can range from manual to fully-automated also include relevant descriptive text examples: http://www.w3.org/TR/ATAG20-TECHS/#checking-types
http://www.w3.org/TR/ATAG20-TECHS/#repair-types
Cheers,
Jan
Related issues: (space separated ids)
WG Notes:
Resolution: (Please make sure the resolution is adapted for public consumption)
Add a comment .