Thanks Jon. It's not really a promotion, but more like a related sub content. Ideally I'd like it to be placed after the actual content, but the design had to be this way.
Is it safe to say that screen reader and/or text-based browser users would 'learn' a web page? I figured if I could follow Jon's second idea consistently for these pages, users could then adapt to this structure. Thanks for your help. On Wed, May 13, 2009 at 10:17 PM, Jon Gunderson <jong...@gmail.com> wrote: > One idea is the first skip should be "skip to title" and the second > link "skip to content". > > a second ideas is for your second link to be "skip over promotion" > > It is not clear to me why there would need to be promotional material > between the heading and the content. COuld you send a link of an > example? > > Jon > > > On Tue, May 12, 2009 at 8:30 PM, Ben Lau <bensan...@gmail.com> wrote: > > Hi all, > > > > I am to build templates for a page, and below is a pseudo example of my > code > > order: > > > > -skip to #content- > > [div#navigation] > > <a name="content"></a> > > [h1] > > [div#promotion] > > [div.content] > > > > I've always believed my h1 should always come after the 'content' anchor > (or > > within a #content div), so when screen reader skips my navigation to the > > content, they're able to read the h1 as well. Ideally I'd like to connect > > the h1 and div.content together, however I'm stuck with the div#promotion > in > > between as I need to adhere to the visual layout. > > > > I was thinking of inserting another skip link to .content (and add > another > > anchor name before it), so it'll read as: > > > > -skip to #pageContent- > > [div#navigation] > > <a name="pageContent"></a> > > [h1] > > -skip promotion to #content- > > [div#promotion] > > <a name="content"></a> > > [div.content] > > > > My question is, is it bad to have a skip link right after you've skipped > > from the top? > > (hope I've explained it well...) > > > > Thanks, > > Ben > > > > ******************************************************************* > > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > > Help: memberh...@webstandardsgroup.org > > ******************************************************************* > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
