Is it not possible to place the navigation near to the top of your Source Code and position the navigation using CSS? That whay people who cannot use CSS will have the navigation at the top.
Source Order is important for this very reason. There may be a reason to why you can't do it, but from what ive read there isn't really much to bounce off, so thats my 2 pence. On 6/28/07, Tate Johnson <[EMAIL PROTECTED]> wrote:
On 28/06/2007, at 7:34 PM, Frank Palinkas wrote: > Thanks David, much appreciate your feedback. That's exactly what I > thought, > but I'm not inclined to assume anything. > > As you mention, I'm experimenting with moving the "skip to content" > link off > screen with a margin-left of -9999em, leaving its markup intact > just above > the floated global nav div. > > Kind regards, > > Frank This is the preferred method. Using display none may actually hide content from screen readers. Usually, I set an absolute position in conjunction with a negative em margin. This will hide the element from modern, graphical browsers. If you place the accessibility links at the top of your markup, it will be one of the first elements that disabled users will view. Cheers, Tate > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of David Little > Sent: Thursday, 28 June, 2007 11:06 AM > To: wsg@webstandardsgroup.org > Subject: Re: [WSG] Skip to Content? > > Hi, > > I'd still include the link (as the first link on the page) as I > imagine you're still going to have other browser content before you > get to your page's main content (headers, logos etc.) -- unless you > want users of screenreaders to have to sit through that for every > page. > > I'd say anything that adds to the usability of a site for any group is > worth including. Also, it's very easy to hide these links from other > "standard" browsers if you so wish, so it's not really much of an > overhead to include them. > > Hope this helps, > David > > On 28/06/07, Frank Palinkas <[EMAIL PROTECTED]> wrote: >> Hi All, >> >> Just a quick question and please pardon my ignorance.. >> >> If the global site navigation on a page is marked up below the >> content, and >> then floated left (or right) to bring it visually next to the >> content in a >> two column manner, is it good practice to include a "Skip to >> Content" link > as >> part of the navigation markup for users with assistive technologies? >> >> More simply put, given that the global nav is structurally >> situated below > the >> content, will this preclude the use of a skip to content link? >> >> Looking forward to your comments, >> >> Kind regards, >> >> Frank >> >> >> >> ******************************************************************* >> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >> Help: [EMAIL PROTECTED] >> ******************************************************************* >> >> > > > -- > David Little > > -m: 077 6596 5655 > -e: [EMAIL PROTECTED] > -w: www.littled.net > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
