Re: Editorial Errors in WCAG Techniques

================================
Response from the Working Group
================================
Thank you for reporting these editorial problems. We are fixing them
as you proposed. In F17, "determined" is correct and we are removing
"provided". In F89, we are changing "two nearly links" to "two
adjacent links".


Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact


On behalf of the WCAG Working Group



On Fri, Sep 17, 2010 at 5:26 AM, Tomas Caspers <tcaspers@me.com> wrote:
> Dear all,
>
> during the translation of WCAG Techniques into German we found a few more errors or omissions.
>
> Kind regards,
>
> Tomas Caspers
>
>
> --------
>
>> A better solution would be eliminate the image and to enclose the text within a header element which has been styled using CSS.
>
> There is a "to" missing before eliminate
>
> --------
>
>> Check if moving from one filed to the next navigates to another screen.
>
> It must read "Field" instead of "filed"
>
> --------
>
>> If steps step #1, step #3, step #4, or step #6 are false, then the content fails the success criterion.
>
> The "steps" after if should be deleted or the words "step" in front of the numbers should be deleted.
>
> --------
>
>> For example, when id attribute values are not unique, they are particularly problematic when referenced by labels, headers in data tables, or used as fragment identifiers, as user agents do not have enough information to provide determine essential relationships (i.e., to determine which label goes with which item).
>
> Should it be provide or determine?
>
> --------
>
>> This makes it possible for users to view pages pages where colors have not been specified by the author in their preferred color combination.
>
> There is one "pages" too many after view.
>
> --------
>
>> Failure Example 4: Specifying only background color with CSS
>
> Here it should read foreground color! Failure example 3 was background color with CSS!
>
> --------
>
>> In addition, by this practice removes focus entirely, which means the content can only be accessed by a pointer device, such as a mouse.
>
> Maybe it would be a good idea to reword this sentence?
>
> --------
>
>> This failure helps ensure that people who cannot perceive color differences can identify links.
>
> Does a failure really help with sth?
>
> --------
>
>> Since they are alternatives to text, they are do not need themselves to have redundant text alternatives in the form of captions, audio descriptions or full text alternatives.
>
> The second "are" (before do not) is probably a leftover of a previously formulated sentence?
>
> --------
>
>> However, if they provide more information than the text for which they are an alternative, then they are more than simply alternatives but are synchronized media content in their own right.
>
> If the sentence ends with "but are more..."  then there would have to be a negative form before it (e.g. then they are not just simple alternatives but...)
>
> --------
>
>> The following CSS example creates a border around links that does not have enough contrast for the focus indicator to seen when drawn on top of it.
>
> There is a "be" missing before seen.
>
> --------
>
>> First do a quick check to see if the contrast between the text and the area of the image that darkest (for dark text) or lightest (for light text) meets or exceeds that required by the Success Criterion (1.4.3 or 1.4.5).
>
> ... of the image that IS darkest ....
>
> --------
>
>> This introduces a "stuttering" effect when two nearly links have the same name, and authors attempts to eliminate the redundancy by providing a null alt attribute for the image.
>
> What do you mean with "two nearly links"  - is it supposed to mean "two nearly identical links" or "two near links" or sth. similar?
>
> Also: the "attemps" must read "attempt"
>
> --------
>
>
>
>
>

Received on Tuesday, 21 September 2010 00:40:53 UTC