Re: Editorial Errors in WCAG Techniques

On Thu, Feb 24, 2011 at 4:47 AM, Tomas Caspers <tcaspers@me.com> wrote:

> Dear all,
>
> during the translation of Flash Techniques for WCAG into German we found a
> few more errors or omissions.
>
> Thanks for clarification,
>
> Tomas Caspers
>
>
>
> ----
>
> > Each following role contains a question and a radio button in each cell
> corresponding to answer choice in the three columns.
>
> Shouldn't that be "row" instead of “role“?
>
> ----
>
> > Check that a label element associates the text with all input elements
> of type "radio", "checkbox", "text", "file" or "password", for all textarea
> elements, and for all select elements
>
> Shouldn't that be "with all textarea elements, and with all select
> elements"?
>
> ----
>
> > The id reference list contains one or more unique element id's.
>
> id's ist not a Genitive - it's just a plural so there shouldn't be an
> apostrophe I think.
>
> ----
>
> > Note: Note: At this time, WAI-ARIA is a Working Draft.
>
> Note appears twice.
>
> ----
>
> > Flash player is often used to display video, and it provides support for
> text tracks which can be used to provide closed captions or subtitles in
> any language, and it also support multiple tracks of audio, thereby
> enabling support for video description, and support for multiple video
> tracks, enabling the delivery of sign language interpretation for
> audio-visual content.
>
> ...it also support...  there is an "s" missing in the word support -
> should read "supports".
>
> The last part of the sentence would be easier to understand if it would
> either be: " ... and it supports multiple video tracks.."  or else " ...and
> it provides support for multiple video tracks.... "
>
> ----
>
> > The Flash Player supports the ability for authors to control which
> graphics appear to assistive technologies using the silent property of the
> accessibility opbect, as indicated in the examples below.
>
> object is spelled wrong (obpect)
>
> ----
>
> > The hotspot are implemented as invisible Flash buttons, which are each
> given an accessible name that describes the hotspot's target.
>
> Should either read  "the hotspot is" or "the hotspots are"
>
> ----
>
> > When focus has been placed inside the Flash movie, press the tab order
> repeatedly to traverse its contents by keyboard.
>
> Should one press the Tab key?
>
> ----
>
> > The objective of this technique is to demonstrate how to invoke a
> scripting function in a way that is keyboard accessible by attaching it to
> keyboard-accessible, standard Flash components provided by the Adobe Flash
> Profressional authoring tool.
>
> Should be Professional (without the r after the Prof)
>
> ----
>
> > 'swfNext-<next ID>', where '<next element>' should be the ID value of
> the next element in the tab order.h
>
> What is the h after the period supposed to mean?
>
> ----
>
> > The working example of Providing a button in the HTML before the Flash
> object to stop sound  is available.
>
> Should read: The source of ....
>
> ----
>
> > The working version of A thick blue border to indicate focus is
> available.
>
> Should read: The source of ....
>
> ----
>
> > This example is the same as example 2, except using ActionScript instead
> of the accessibility control panel in the Flash Professional authoring tool.
>
> This text is the text of example 2 - so it can't be the same as example 2
>
> ----
>
> > Ensure that the textual descriptions for each form control within the
> flash application is placed adjacent to the control itself.
>
> textual descriptions is a plural form, the verb (is) is singular.
>
> ----
>
> > Open a web page containing an embedded flash objects
>
> Flash objects should either be in the singular or the verb should be plural
>
> ----
>
>
>
> ================================
Response from the Working Group
================================
Thank you for catching these. We have fixed these errors as appropriate.

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