Re: [WSG] source order
On 13/10/07 (09:21) JonMarc said: with all the skips and jump tos and methods for pulling links and whatnots, i wonder how many people using screen readers ever make it down there to the footer/copyright/whatever-else-you-put-there Remember that screen reader applications can commonly call up a handy list of all the links on a page, so those in the copyright section would also be presented in that list (albeit probably at the end of the list) without the user necessarily needing to 'read' their way down to them. -- Rick Lecoat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] source order
Rick Lecoat wrote: Remember that screen reader applications can commonly call up a handy list of all the links on a page Has anyone tested how skip links work from a link list? I have a little theory called the hierarchy of link specificity that I've been meaning to write up for years. The theory concerns itself with source order and link lists. It goes something like this: with a reverse source order (content before nav) content specific links will always appear before the current section nav ,main nav, and utility links - this should have the effect of allowing the most relevant (to the current context) links to appear at the top of lists - effectively shortening them considerably. With traditional source order link lists are essentially random and people still have to scroll through the entire list to find relevant links. kind regards, Terrence Wood. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] source order
Terrence Wood wrote: It goes something like this: with a reverse source order (content before nav) content specific links will always appear before the current section nav ,main nav, and utility links - this should have the effect of allowing the most relevant (to the current context) links to appear at the top of lists Most relevant to whom, though? If I landed on a page (say from a google search) but actually want to navigate further into/around the site, *my* most relevant links are the navigation ones. One size does not always fit all. 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 __ Co-lead, Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __ Take it to the streets ... join the WaSP Street Team http://streetteam.webstandards.org/ __ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] source order
If you landed on the page from a search result and it's not the page you want... can we assume that it be close, given you clicked to there in the first place? Patrick, I suspect your assumptions are way bigger than mine on this one :-) But, like I said, it's a theory (untested), so we don't really know either way. kind regards, Terrence Wood. On 16/10/2007, at 10:47 AM, Patrick H. Lauke wrote: Terrence Wood wrote: It goes something like this: with a reverse source order (content before nav) content specific links will always appear before the current section nav ,main nav, and utility links - this should have the effect of allowing the most relevant (to the current context) links to appear at the top of lists Most relevant to whom, though? If I landed on a page (say from a google search) but actually want to navigate further into/around the site, *my* most relevant links are the navigation ones. One size does not always fit all. 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 __ Co-lead, Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __ Take it to the streets ... join the WaSP Street Team http://streetteam.webstandards.org/ __ *** 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] ***
[WSG] How to make DHML cover flash
I have a page where there are some dhtml menus with drop downs across the top of the page, and a large flash object in the body of one of the pages. However the drop-down menu items are going underneath the flash object so they can't be clicked on. I thought I should just put the flash into a div with a z-index lower than the z-index of the drop down list item, but that doesn't seem to work.Can anyone please tell me how I ought to deal with this? Here's what I have: In the menus: style .dropmenudiv { z-index : 800; } /style ul limenu item 1/li liMenu item 2/li Etc /ul !--1st drop down menu -- div id=dropmenu1 class=dropmenudiv a href=/nw/tshirtsstock.cfmT Shirts/a a href=/nw/polosstock.cfmPolos/a a href=/nw/singletsstock.cfmSinglets/a a href=/nw/sweatersstock.cfmSweaters/a a href=/nw/shortsstock.cfmShorts/a a href=/nw/rashtopsstock.cfmRash Tops/a a href=/nw/clearance.cfmClearance/a /div And in the flash object: div style=z-index: 1; [flash object code here] /div *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***