RE: PROPOSAL: The meaning of "Easy access" in checkpoint 2.3

thanks.  I see now.  it helps to have different modalities for different ui
possibilities. so, is there one say acontext menu that would be preffered
over say a link if it is applicable?

"Poehlman, David" wrote:
> 
> I guess I'm not sure just how having the ua create a link would or might
> work.

Suppose you have an image with an associated long description. Some
approaches for providing access to the long description would be:

1) Allow me to open a context menu and select a menu entry for
   access to the long description. Note that some content may
   have more than one associated equivalent, so such a dynamic
   menu might have several entries.

2) Allow me to open a "get info" (inspect) view of some piece of
   content that included details about the object, including links
   to it's alternatives.

3) Insert a link after (or before, which might be configurable)
   the image. This is the "D-link" approach to providing access
   to long descriptions. This is what I mean by a link in context.

For some types of content, having the alternative inline might be
very burdensome (notably, for long text equivalents). Therefore
a link to that content is a better solution than simultaneous rendering
inline. For short equivalents (like alt), having the content
subsituted or rendered next to the primary content is probably
a better solution.

 - Ian

> Ian wrote:
> We could say "allow configuration for one of the following:"
> 1) Render alt instead
> 2) Render alt alongside
> 3) Render link
> 4) Provide accses through the UI.
> 
>  -Ian
> 
>  > Ian,
> > I am OK with this, how about anybody else?
> >
> > Jon
> >
> > >  <NEW_UI>
> > >  2.3 If content available in a viewport has equivalent alternatives,
> > >    provide easy access to the alternative equivalents
> > >    through at least one of the following mechanisms:
> > >     - Allowing configuration to render alternative
> > >       instead of primary content.
> > >     - Allowing configuration to render alternative in addition to
> > >       primary content.
> > >     - Providing a direct link to the alternative in content,
> > >       just before or after the primary content.
> > >     - Allowing the user to select the primary content and then
> > >       inspect its alternatives.
> > >  <NEW_UI>
> > >
> > >Notes:
> > >
> > >1) I put back the word "easy" since that helps understand the
> > >    rationale.
> > >
> > >2) I hesitate to put four techniques in a checkpoint, but if
> > >implementing any one of them would mean that the UA met the
> > >requirement, then I'm ok with that level of specificity.
> > >
> > >  - Ian
> > >
> > >--
> > >Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
> > >Tel:                         +1 831 457-2842
> > >Cell:                        +1 917 450-8783
> >
> > Jon Gunderson, Ph.D., ATP
> > Coordinator of Assistive Communication and Information Technology
> > Division of Rehabilitation - Education Services
> > MC-574
> > College of Applied Life Studies
> > University of Illinois at Urbana/Champaign
> > 1207 S. Oak Street, Champaign, IL  61820
> >
> > Voice: (217) 244-5870
> > Fax: (217) 333-0248
> >
> > E-mail: jongund@uiuc.edu
> >
> > WWW: http://www.staff.uiuc.edu/~jongund
> > WWW: http://www.w3.org/wai/ua
> 
> --
> Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
> Tel:                         +1 831 457-2842
> Cell:                        +1 917 450-8783

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783

Received on Tuesday, 25 July 2000 09:54:16 UTC