- From: Charles McCathieNevile <charles@sidar.org>
- Date: Thu, 1 Apr 2004 08:40:29 +1000
- To: Francois Jordaan <Francois.Jordaan@wheel.co.uk>
- Cc: "'w3c-wai-ig@w3.org'" <w3c-wai-ig@w3.org>
Actually, lots of things about frames are good - unfortunately there are a few architectural problems with them. In this case I would rely on the users. In common setups like IE/Jaws the users will be able to move between frames as a function of the user agent. In systems that don't present all the frames (Lynx, Amaya, etc) the user will be offered a choice of which frame they want to see (so they can choose the navigation frame, or the content frame, or whatever), or they can just work with the noframes version. Cheers Chaals On 1 Apr 2004, at 01:37, Francois Jordaan wrote: > > Simple question for the benefit of screen reader users and > keyboard-navigators: > > Can I provide a link from one frame into another that doesn't involve > re-loading the second frame? > > I'm providing a "jump to content" link at the start of the page, only > the > content happens to be in another frame. (I know frames are bad; it > happens > to be unavoidable on this one particular page.) > > At the moment my best idea is to put the anchor (the target of the <a > href="#content"> link) at the *end* of the first frame. I expect the > screen > reader to then announce the start of the next frame, titled "Content". > That > sounds OK. > > But then, what do I do to let the user return to the navigation in the > previous frame? > > francois > > Wheel Group, Beaumont House, Kensington Village, Avonmore Road, > London W14 > 8TS > www.wheel.co.uk > > > _____________________________________________________________________ > This e-mail has been scanned for viruses by MessageLabs. > > -- Charles McCathieNevile Fundación Sidar charles@sidar.org http://www.sidar.org
Received on Wednesday, 31 March 2004 17:44:03 UTC