W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2000

Re: Equivalency, Languages, Checkpoint 2.3

From: Ian Jacobs <ij@w3.org>
Date: Mon, 06 Nov 2000 11:54:15 -0500
Message-ID: <3A06E237.277983B4@w3.org>
To: Harvey Bingham <hbingham@ACM.org>
CC: w3c-wai-ua@w3.org
Harvey Bingham wrote:
> 
> At 2000-11-02 08:13-0600, Jon Gunderson wrote:
> >Al,
> >Here is another try at the wording of checkpoint 2.3.  I hope this is more
> >than just another circle.
> >
> ><NEW>
> >2.3 For any elements with recognized equivalents, provide easy access to all
> 
> HB: What are "recognized" equivalents? By whom? user or user agent?


Yes: We have a definition of recognize in the glossary that explains
what this means.

 - Ian

> Omit "all",  not all assistive technology can handle "all" the equivalents,
> same problem as in the prior version where "each" was used.
> 
> <newer>2.3 For any elements with recognized equivalents, provide easy
> access to equivalents through one of the following mechanisms:</newer>
> 
> >equivalents through one of the following mechanisms:
> >(1) allowing configuration to render just one the alternatives from the
> >available equivalents;
> >(2) allowing configuration to render at least two of the alternatives at
> >the same time from the available equivalents;
> 
> HB: "Concurrently", rather than "at the same time". The latter can be
> interpreted
> as requiring time synchronization (of text, audio, video), such as through
> SMIL,
> at some detail level, such as to the word, as we'd like to do in digital
> talking
> books, but as a general requirement I believe this is asking too much.
> 
> <newer>(2) allowing configuration to render at least two of the alternatives
> concurrently from the available equivalents.</newer>
> 
> >(3) allowing the user to select the rendered element and then inspect its
> >alternatives;
> 
> HB: Do we expect selection of each entire "rendered element" (such as
> parent container DIV for many children) to have an alternative?
> 
> How about:
> <newer>(3) allowing the user to select any element that directly contains
> content,
> and then inspect its alternatives;</newer>
> 
> >(4) providing a direct link to the alternatives in content, just before or
> >after the element in document order.
> >
> >[Priority 1]
> >...</NEW>
> >
> ><CURRENT>
> >2.3 Provide easy access to each equivalent and each equivalency target
> >through at least one of the following mechanisms: (1) allowing
> >configuration to render the equivalent instead of the equivalency target;
> >(2) allowing configuration to render the equivalent in addition to the
> >equivalency target; (3) allowing the user to select the equivalency target
> >and then inspect its equivalents; (4) providing a direct link to the
> >equivalent in content, just before or after the equivalency target in
> >document order. [Priority 1]
> >...
> 
> Regards/Harvey

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783
Received on Monday, 6 November 2000 11:54:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:22 GMT