W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2005

Re: Provisional results of the Lexicon Task Force

From: Chuck Letourneau <cpl@starlingweb.com>
Date: Fri, 14 Jan 2005 07:47:30 -0500
Message-Id: <>
To: "Henk Snetselaar" <H.Snetselaar@bartimeus.nl>,<w3c-wai-eo@w3.org>
My comments are mixed in below.

At 05/01/12 03:16, Henk Snetselaar wrote:

>- Are the descriptions of the words/terms according to the requirements 
>- Attribute
>Information that explains or identifies a tag or element in a markup 
>language. Element types may have more than one attribute like size, shape, 
>wight and color. Some attributes are integral to the accessibility of 
>content (for example, the "alt", "title", and "longdesc" attributes in HTML)

I thought that attributes could also modify the default behavior of markup 
elements.  Should we say: "Information that explains, identifies or changes 
the behavior of..." ?

>- Captions
>Captions are equivalent alternatives for an audio track of a movie. 
>Captions consist of a text transcript of the auditory track of the movie 
>(or other video presentation) that is synchronized with the video and 
>auditory tracks. Captions are generally rendered graphically. They benefit 
>people who are deaf or hard-of-hearing, and anyone who cannot hear the 
>audio (for example, someone in a noisy environment).

The first sentences seems redundant.  To shorten the entry, the first two 
sentences might be combined as:
"Captions are equivalent alternatives that consist of a text transcript of 
the auditory track of the movie (or other video presentation) that is 
synchronized with the video and auditory tracks.

>- Device independence
>The use of a webpage or event handler without a specific kind of input 
>device. Scripting should be device-independent or provide multiple input 
>and output options for different devices.For example, onDblClick requires 
>a mouse; there is no keyboard equivalent for double clicking. Input 
>devices may include pointing devices (such as the mouse), keyboards, 
>braille devices, head wands, microphones, and others.

The first sentence doesn't seem right to me.  To use a Web page or event 
handler the person doing it is always using a specific input device: the 
developer/authoring tool just shouldn't limit the choice for the end-user. 
The concept in the first sentence might be better stated as: "The use of a 
webpage or event handler with any kind of input device."

>- Transcript
>Transcripts are equivalent alternatives for the sounds in an audio clip or 
>an auditory track of a multimedia presentation. A "collated text 
>transcript" for a video is a combination of caption text with text 
>descriptions of video information (descriptions of the actions, body 
>language, graphics, and scene changes of the visual track).

Is there any benefit in this definition of mentioning that a transcript is 
not synchronized with the audio track, to further distinguish it from 
"Captions"?  Or would this be redundant, or even confusing?

Chuck Letourneau
Starling Access Services

>H. Snetselaar
>Bartimeus Educational Institute for the Blind and Partially Sighted &
>Foundation Bartiméus Accessibility
>Utrechtseweg 84, 3702 AD  Zeist, the Netherlands
>Tel: +31-(0)30-6982211 or +31(0)30-6982350
>Fax: +31-(0)30-6982388
>E-mail: H.Snetselaar@bartimeus.nl
>Website: www.bartimeus.nl and www.accessibility.nl
>Zie voor disclaimer (Read our disclaimer): 
Received on Friday, 14 January 2005 13:11:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:37 UTC