- From: Gian Wild <findme@gianwild.com.au>
- Date: Fri, 21 Jun 2013 20:34:04 +1000
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, Vivienne Conway <v.conway@webkeyit.com>
- Cc: w3c-wai-ig@w3.org
- Message-ID: <CAOTNkVmoDs1JjGKvcW8DDBCZYq+6520J2zj-MdfJWg_W6YFV6A@mail.gmail.com>
It's an advisory technique under Guideline 2.4. http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms.html Cheers Gian On 21 Jun 2013 20:32, "Patrick H. Lauke" <redux@splintered.co.uk> wrote: > On 21/06/2013 10:57, Vivienne CONWAY wrote: > >> I pity anyone using a screen reader or keyboard navigation >> having to wade through miles of links or text to get to the >> information they need. >> > > It's possibly the same for mouse users, though...wearing out my mouse's > scroll wheel or endlessly dragging on the scrollbar. In fact, once proper > headings/structure are added, AT users may well be at an advantage here > with the ability to jump to headings etc directly. > > For what it's worth, when faced with a long document, I start to usually > do an in-page search (provided I know the wording of what I'm looking for, > e.g. a technical term inside a long W3C spec document). Of course, that > doesn't help in situations when I'm after a broader/fuzzier set of > information or advice. > > P > -- > Patrick H. Lauke > ______________________________**______________________________**__ > re·dux (adj.): brought back; returned. used postpositively > [latin : re-, re- + dux, leader; see duke.] > > www.splintered.co.uk | www.photographia.co.uk > http://redux.deviantart.com | http://flickr.com/photos/**redux/<http://flickr.com/photos/redux/> > ______________________________**______________________________**__ > twitter: @patrick_h_lauke | skype: patrick_h_lauke > ______________________________**______________________________**__ > >
Received on Friday, 21 June 2013 10:34:31 UTC