- From: Charles McCathieNevile <charles@w3.org>
- Date: Wed, 12 Jul 2000 12:47:13 -0400 (EDT)
- To: Ian Jacobs <ij@w3.org>
- cc: Jon Gunderson <jongund@uiuc.edu>, w3c-wai-ua@w3.org
I agree with Ian - this proposal goes too far into the detail of User Interface implementation. Charles McCN On Wed, 12 Jul 2000, Ian Jacobs wrote: Jon Gunderson wrote: > > To make checkpoint 2.3 more explicit, I suggest the following changes: > > <OLD> > 2.3 If content available in a viewport has equivalent alternatives, provide > easy access in context to the alternatives. > </OLD> > > <NEW> > 2.3 If content available in a viewport has equivalent alternatives, render > the alternative equivalents next to the primary content in the user > interface. If it is not possible to render the alternative equivalents > next to primary content, provide a one step command to access the equivalents. > </NEW> I don't know what "next to" means. What if styling is used (or must be used) to reposition it? What does next to mean in an international context? What if there is more than one equivalent? I imagine a much better UI (e.g., that of amaya) where information is available through consistently designed context-sensitive menus (that are accessible). I actually prefer not altering content if we can avoid it. - Ian P.S. I'm sending these comments late at night, after a ftf meeting, without a lot of thought. -- 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 Wednesday, 12 July 2000 12:47:15 UTC