W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2004

RE: Gateway Techniques draft: responses to two editorial notes

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Thu, 29 Jul 2004 14:37:11 -0500
Message-ID: <C46A1118E0262B47BD5C202DA2490D1A03B521F4@MAIL02.austin.utexas.edu>
To: "Wendy A Chisholm" <wendy@w3.org>
Cc: <w3c-wai-gl@w3.org>

Wendy, responding to one of my posts yesterday::


>Editorial Note:The use of "clearly" and "concisely" makes this 
>Will that be an issue for readers?
>[js: I hope not-- the idea here is to provide guidance that helps
>understand what they need to do. We could add a note saying that
>and concision require human judgment, and that such judgment should be 
>informed by at least informal feedback from users, or at best by formal

>user testing.]

WAC: My intent with this note was to get feedback from people about what

they expected to see at the gateway level.  Thus, I'm tempted to leave
note as it is and see if we get any responses. Thoughts?
John: I agree that feedback from the list is important! But I do want to
make a case for allowing the Gateway document to discuss techniques and
strategies that may not be testable, or, in cases where techniques may
produce results that aren't *machine*-testable, to include suggestions
about testing techniques as well.
Wendy again:
>Editorial Note: In this draft, part C of the Level 1 success criterion 
>Guideline 1.1 is divided into two techniques this one (music without
>and the next (visual art). Is this confusing? Should they merge into
>[js: I think it would be more confusing to treat the tasks of
>non-vocal audio and visual art somewhat differently-- the descriptive 
>techniques and vocabularies are very different, and so is the issue of 
>what gets "displayed," since you can't "display" audio. We may need to
>a note to this effect.]

I interpret this as, "keep the two techniques separate because the 
strategies and vocabularies are different."  Is that what you intended
were you aiming for something else?
Yes, I intended to say keep these items separate because the strategies
and techniques are different." In another message to the list yesterday
[1], I added some other thoughts about this issue, which I'll paste in
below for convenience' sake:
There are significantly different requirements for different types of
audio content, and I think they're covered by different items under 1.1
L1 SC 1.  In my judgment, spoken-word audio would be covered by ther
requirement to provide "the same information" as the non-text content--
in this case, a text transcript that includes the words in the
recording.  For non-vocal music, the minimum requirement is for a text
label that identifies the piece.  Typically this would be provided via
alt text on a graphical link to the audio file (such as an icon of an
ear or something) or by a a text link.  In some contexts (e.g., a
history of music or a music review) it might be appropriate to include
an additional text description of the piece.  This could be done in
several ways, including nested <object> elements, etc.  In any case, I
think we can solve the problem by dealing with spoken-word audio under
the requirement to provide the same information and with non-vocal music
under the requirement to identify non-text content that creates a
specific sensory experience.
Hope this helps!
wendy a chisholm
world wide web consortium
web accessibility initiative
Received on Thursday, 29 July 2004 15:37:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:50 UTC