At 7:44 PM -0700 10/27/07, Tee G. Peng wrote:
I am having an issue and I can't seem to see the whole picture objectively.

Thanks to your influences, it has become my second nature to have 'skip to content' in every site I do (sites I have control over the design and layout); when I do markup coding, clients often ignore the 'skip to content' and 'skip to nav' - I managed to convinced them a couple times with a compromise to hide it from browsers by using 'display:none', because, according to them, only screen users need 'skip to content'.

I am doing a site that I have control on design and layout, client asked to remove the 'skip to content' when I showed him the first layout, I tried to talk him out by stating how important it is to have the 'skip to content' implemented. He didn't buy it, so I came out with this technique: (move your mouse to the top to see the result).

Hi Tee,

I appreciate your desire to provide navigational accessibility for disabled users however "Skip to content" is not the best way to do it. Most disabled users, particularly sight impaired, will use your header markup to navigate the page rather than skip links. Most often the audience who need the skip nav functionality will be using an accessible browser like Firefox which allows them to display a header list whereby they can easily surf through a properly structured page which makes use of header tags.

You've done a fairly good job on the teesworks page using header tags so the skip to content link is not going to serve much purpose. Also keep in mind that display:none and visibility:hidden remove content from screen readers. A screen reader will not pick up elements styled like that so unless that's your purpose, don't use those kinds of rules in your CSS for markup you intend for a screen reader.

Nice page btw.

       Tim Offenstein  ***  Campus Accessibility Liaison  ***  (217) 244-2700
            CITES Departmental Services  ***

List Guidelines:

Reply via email to