Edit comment LC-2786 for HTML Accessibility Task Force

Quick access to LC-2786 LC-2787 LC-2788 LC-2789 LC-2843

Comment LC-2786

Comment Shortname:

Commenter: Richards, Jan <jrichards@ocadu.ca>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeHTML5 Image Description Extension Abstract This specification defines a longdesc attribute to... Status of This Document This section describes the status o... Table of Contents Introduction 1. Conformance 1.1 Depende... Introduction HTML 4 provided a longdesc attribute for the i... 1. Conformance As well as sections marked as non-normative,... 1.1 Dependencies and definitions The IDL fragments in this... 2. Use Cases and Requirements There are many ways users can... Use Cases Requirements for an Image Description functionality 3. The longdesc attribute 3.0 Implementation 3.0.1 Authors... 3.0 Implementation 3.0.1 Authors and Conformance checkers Zero or one longdesc attributes may be added to any img ele... 3.0.2 Authors 3.0.3 User Agents 3.1 Extension to the HTMLImageElement interface partial in... partial interface HTMLImageElement { attribute... 3.1.1 Attribute longdesc of type DOMString The longdesc I... longdesc of type DOMString longdesc A. Acknowledgements Thanks to the HTML Working Group of the... B. References B.1 Normative references [HTML5] Robin Berj... B.1 Normative references [HTML5] Robin Berjon et. al., eds... [HTML5] [RFC2119] [WEBIDL] B.2 Informative references [ATAGB3] Jutta Treviranus et. a... [ATAGB3] [WCAG] [UAAG] C. Change History (This section is not normative) Since the...
or

Refinement of the section concerned:

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)