Re: issues on BAD after pages

Shadi Abou-Zahra wrote:
> 
> Hi,
> 
> Here is a very brief summary of some of the issues on the BAD "after" 
> pages. Please respond to the list with your comments and thoughts:
> 
> 
> 1. improve skip-links
> - there should be mechanisms to skip over the "warning" bar at the top 
> of the page
> - the "warning" bar should be more apparent as such to screen reader users
> - do we *need* "Screenreader Tips and other Accessibility Features"?

Don't need screenreader tips. Do need

Implement the target like this:

<h1><a id="skiptarget">text textr text</a></h1>

and style
a#skiptarget {text-decoration: none; color: #000}

Assuming the h1 is indeed black

This avoids most skip bugs I know of, except the skip-to-top 
IE-not-moving-the-viewport bug.

I've commented to Shadi regarding proliferation of cruft around this 
resource, and my concerns about it. We are going the wrong way with it 
and making it a less useful resource for developers. Shadi, if I didn't 
cc the list with my mini-rant (may not have, apologies), please forward 
any relevant bits of my email!

> 2. quick-links menu
> - should the current page be inactive or not available at all from the 
> menu?

Keep it the same on each page (i.e. all active). But this isn't a WCAG 
issue, it's a best practice argument. Avoid.

> 3. links to articles
> - should we use fragments to jump into the page content (i.e. specific 
> articles)?

Yes. It's a normal part of the web and is, again, not a WCAG issue, it's 
a best practice argument. Avoid.

> 4. headings structure
> - need to have headings for the menu and the right navigation bar. 
> visible or not?

Left-shifted.

> - do we need an (invisible) first-level heading for each page?

No. The h1 should be the main headline of the page.

Regards all

Liam
www.communis.co.uk

Received on Tuesday, 15 August 2006 12:45:12 UTC