- From: Charles McCathieNevile <charles@w3.org>
- Date: Tue, 25 Jul 2000 10:01:19 -0400 (EDT)
- To: "Poehlman, David" <David.Poehlman@usmint.treas.gov>
- cc: "'Ian Jacobs'" <ij@w3.org>, "'Jon Gunderson'" <jongund@ux1.cso.uiuc.edu>, w3c-wai-ua@w3.org
Lynx creates a whole range of links to things that it generates - the history file is a link in the history file, based on a temporary file. There are links to recent status messages, and various other things added to documents. Mechanically it is pretty trivial - find a place to put something, add a link to it, and if the user activates the link, show it to them. Netscape does the same thing with various special URI's - about: and javascript: (I have never tried to make them links in a document, but in theory they should work - does someone want to test this? Charles On Tue, 25 Jul 2000, Poehlman, David wrote: I guess I'm not sure just how having the ua create a link would or might work. "Poehlman, David" wrote: > > I've a bit of a problem with this because if the link alternative is chosen > it might mean that the fascility is broken. I'm not sure what you mean here. > As I understand it, the primary > expectancy is for choice so we could narrow the number of items to two if we > keep the link option by listing the configurations as one other alternative > rather than three? 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 -- Charles McCathieNevile mailto:charles@w3.org phone: +61 (0) 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI Location: I-cubed, 110 Victoria Street, Carlton VIC 3053 Postal: GPO Box 2476V, Melbourne 3001, Australia
Received on Tuesday, 25 July 2000 10:01:26 UTC