This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16916 - long list typos and nits
Summary: long list typos and nits
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 alt techniques (editor: Steven Faulkner) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-03 09:41 UTC by steve faulkner
Modified: 2012-10-16 16:02 UTC (History)
4 users (show)

See Also:


Attachments

Description steve faulkner 2012-05-03 09:41:02 UTC
feedback from loretta
1. "points to the a version" -> "points to a version

2. programmatically associated using
<a href="http://www.w3.org/TR/wai-aria/roles#group">
<code></code>
</a>
on the containing
<code>figure</code>

(I think something is missing between <code></code>)

3. "The the longer text" -> "The longer text"

4. "chart, It" -> "chart. It"

5. This may not be a typo, but I don't understand why the Advantages and Disadvantages are listed under Example 3.2. They seem to relate to this entire section.

6. Another place where something is missing in <code></code>.

and a longer text alternative in text.
<a href="http://www.w3.org/TR/wai-aria/roles#group">
<code></code>
</a>
is used to add usable semantics to the figure element

7. "is be used a container" -> "is being used as a container"?

8. " Its use conforms to WCAG 2.0 [WCAG20], but is a willful violation of HTML5 [HTML5]." I'm not sure why we need these terms both outside and inside the square brackets, but it seems like we should be consistent about which one is the link. Probably inside the brackets? This usage happens in several places.

9. " for a persons blog" -> " for a person's blog"

10. I think it would be less confusing if the following were labeled as failures by starting with 'Failure:'

    Omitting the alt-attribute for non-text content used for decorative purposes only in HTML [WCAG20-TECHS]
    Providing a text alternative that is not null. (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology [WCAG20-TECHS]

Otherwise, they look like two more sufficient techniques in WCAG.

11. " included in the alt attribute, there is a link" -> " included in the alt attribute, and there is a link"

12. "points to points to a page" -> "points to a page"

13. " both the image an the text" -> " both the image and the text"

14. "it is also be appropriate" -> "it is also appropriate"

15. "next the the icon" -> "next to the icon"

16. " img elements alt attribute"  ->  "img element's alt attribute"

17. "has an caption" -> "has a caption"

18. "type of image, although this" -> "type of image. Although this"

19. Another <code></code>:

"<a href="http://www.w3.org/TR/wai-aria/roles#group">
<code></code>
</a>
is used to add usable semantics to the figure element..."
20. "image is updated, this can be" -> "image is updated. This can be"

21. Another <code></code>:
in a paragraph associated with the image using
<a href="http://www.w3.org/TR/wai-aria/roles#group">
<code></code>
</a>
on the
<code>figure</code>
element

22. " time and and date" -> " time and date"

23. "2 versions are provided the first includes the description as part of the alt attribute content the second ..." -> "2 versions are provided; the first includes the description as part of the alt attribute content; the second ..."

24. And another <code></code> right after that...

25. "Neither the alt or the caption" -> "Neither the alt nor the caption"

26. "edequate" -> "adequate"

27. Another "<code></code>"

28. "used a a container" -> "used as a container"

29. Further techniques at the end of section 13.1 should reference [WCAG20-TECHS] rather than "W3C Note"

30. "the name of the what that it represents" -> "the name of what it represents"

31. "should have a text alternative, its identification" -> "should have a text alternative, and its identification"

32. "it is the authors intent the purpose of the using an image of text " -> "it is the author's intent that the purpose of using an image of text "

33. "some users, in order" -> "some users. In order"

34. "which is incorrect, the image is not meaningless" -> " which is incorrect. The image is not meaningless"

35. "text is required, using an empty alt attribute" -> "text is required; using an empty alt attribute"

36. "a caption with with a variety" -> "a caption with a variety"

37. "is be used a container for" -> "is being used as a container for"

38. "provide a caption for an image, use the figure" -> "provide a caption for an image; use the figure"
Comment 1 steve faulkner 2012-10-16 16:02:34 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: accepted
Change Description: fixed all issues
Rationale: editorial changes only