Re: [WSG] Navs at bottom of pages
they can also be of great value to screen reader users, they read through the page and maybe want to have a look through the rest of your site. now you could provide a skip link at the bottom of each article to take them back to the main navigation OR you could provide the footer containing the main navigation so they don't have to clcik simple but i think rather nice and effective - Original Message - From: russ - maxdesign [EMAIL PROTECTED] To: Web Standards Group wsg@webstandardsgroup.org Sent: Friday, September 01, 2006 6:28 AM Subject: Re: [WSG] Navs at bottom of pages The use of broken pipes was mostly used (in my opinion, but then I'm an accessibility specialist ;) to address the Level AAA Checkpoint 10.5: Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. The better solution is to mark them up as a list of links (as they are still a list even if presented horizontally) and then use css to create the horizontal appearance (setting the li to display: inline is one method) and the illusion of pipes (applying a border ro one edge of the li or a elements). You could even add a structural label above them to give them meaning :) http://www.maxdesign.com.au/2006/01/17/about-structural-labels/ Russ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** ___ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Navs at bottom of pages
Kenny Graham wrote: I've noticed many people from this list stil put text-and-broken-pipe navs at the bottom of their pages. Is this still needed? I replicate link-relations as ordinary links in the page-footer, since there are so many browsers that can't make use of, or don't default to presenting, visible link-relations. A simple-styled short-list of basic navigation is a 'nice-to-have' thing IMO, so I'll probably keep adding them until all browsers present link-relations by default. Typical example found on... http://www.gunlaug.no/contents/molly_1_18.html ...and the rest of that site-section. Georg -- http://www.gunlaug.no *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Navs at bottom of pages
Beautiful!! I´ve never seen link-relations working, it should really be a built-in spec for browsers... easy to get used to. A way to let anybody, in any site, know where they are standing. It should have also something like sitemap; Content plays that role? Regards; Eugenio. On 9/1/06, Gunlaug Sørtun [EMAIL PROTECTED] wrote: I replicate link-relations as ordinary links in the page-footer, since there are so many browsers that can't make use of, or don't default to presenting, visible link-relations. A simple-styled short-list of basic navigation is a 'nice-to-have' thing IMO, so I'll probably keep adding them until all browsers present link-relations by default. Typical example found on... http://www.gunlaug.no/contents/molly_1_18.html ...and the rest of that site-section. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Navs at bottom of pages
TuteC wrote: Beautiful!! I´ve never seen link-relations working, it should really be a built-in spec for browsers... easy to get used to. A way to let anybody, in any site, know where they are standing. W3C seems to recommend them... http://www.w3.org/TR/relations.html http://www.w3.org/QA/Tips/use-links ...and have done so for a long time. You can turn on the 'navigation bar' in Opera - ToolsAppearanceToolbars... Mozilla support them too, and Firefox could get an extension last time I looked. IE doesn't support them, and I haven't tested in others. It should have also something like sitemap; Content plays that role? On my pages, yes. Some use 'index', but I find 'content' the most correct (and supported) term the way I have organized that section. regards Georg -- http://www.gunlaug.no *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Navs at bottom of pages
TuteC wrote: Beautiful!! I´ve never seen link-relations working, it should really be a built-in spec for browsers... easy to get used to. A way to let anybody, in any site, know where they are standing. Opera puts them to good use too... You can hold the left mouse button and click the right mouse button to take advantage of Next links instead of reaching for the navigation every time :) I think Opera is a bit tricky and might even bind that mouse shortcut to any (or perhaps only unique) Next link on a page as well. Still cool though! *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Navs at bottom of pages
I've noticed many people from this list stil put text-and-broken-pipe navs at the bottom of their pages. Is this still needed? I always thought the reason for it was to have a text version of the main graphics-with-out-alts-in-a-giant-table nav. Is there a reason that I'm missing, or are they just there out of habbit, asthetics, and the like? I can't think of any benefit of having them, and they often suffer from version lag. I just want to make sure I'm not causing any problems by leaving them out. P.S. Am I also correctly remembering the broken pipes being used because of an early netscape bug regarding adjacent links? *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Navs at bottom of pages
I've noticed many people from this list stil put text-and-broken-pipe navs at the bottom of their pages. Is this still needed? Mostly the links at the bottom of the page are footer links (ie meta navigation) and therefore not provided in the normal navigation. It is rare for the main navigation to be replicated in the footer nowadays (although it was common five or six years ago). I always thought the reason for it was to have a text version of the main graphics-with-out-alts-in-a-giant-table nav. Originally, yes, text links were provided because the original navigation was not accessible. I just want to make sure I'm not causing any problems by leaving them out. You won't be if your original navigation is accessible P.S. Am I also correctly remembering the broken pipes being used because of an early netscape bug regarding adjacent links? The use of broken pipes was mostly used (in my opinion, but then I'm an accessibility specialist ;) to address the Level AAA Checkpoint 10.5: Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. Cheers, Gian *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Navs at bottom of pages
The use of broken pipes was mostly used (in my opinion, but then I'm an accessibility specialist ;) to address the Level AAA Checkpoint 10.5: Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. The better solution is to mark them up as a list of links (as they are still a list even if presented horizontally) and then use css to create the horizontal appearance (setting the li to display: inline is one method) and the illusion of pipes (applying a border ro one edge of the li or a elements). You could even add a structural label above them to give them meaning :) http://www.maxdesign.com.au/2006/01/17/about-structural-labels/ Russ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
