Re: For your perusal

Hi Rob

First, re the Bobby reference to splitting up links with more than
whitespace - that's because some older text and speech browsers are
unable to differentiate between a series of consecutive links if they
are not separated by one or more unlinked characters, and not just by
spaces or line breaks.  These older browsers see these consecutive links
as a single link, making it impossible for the user to follow anything
other than the first link in the series.  The problem with the links you
refer to below is that the square brackets have been included as part of
each link, rather than being unlinked, which would neatly separate the
links and ensure that they work in all browsers.  This is a legacy issue
which is gradually disappearing as people upgrade their software.

Most of what programs like Bobby output *is* common sense - one just
needs to know the background issues which the recommendations relate to,
and can then make an informed decision as to whether or not to follow
any particular recommendation.

There's a problem if the user needs to increase the font size using
their browser settings - the line of links at the bottom of the title
graphics expands onto two rows of text, with some of the link text
overlaying the picture of the server, with resulting poor contrast
between the link text and the background.  And if they are using IE and
have set the browser additionally to ignore the font sizes in the page,
the piece of headline text in bold a few lines down from the start of
the main content gets squashed together so that the lines of text
overlap, making it hard to read (possible use of absolute units in
line-height property? - I took a quick look at the page last night, but
can't get into it at the moment to check).

The ALT text on some of the images gives very little information
compared to what is available visually - e.g. price information on the
hosting packages, and the list of credit cards accepted - those are
important bits of information which blind users are not being given.
Some partially sighted users may have problems reading the price
information on these graphics too, since the text and background colours
used on the hosting packages graphics is low contrast.

The "hidden" links which you've included on the page are useful for
those using screen reader software, but they can be confusing for
sighted users who use the keyboard - the visible "focus" vanishes as you
TAB through the page.  You might consider putting the "Page Content"
link first, so that those using text, speech or braille output can jump
past all the navigation and get straight to the content of the page.

HTH!

Regards,
Donna

----- Original Message -----
From: Rob Atkinson <robatkinson(at)nucleus.com>
To: hwg-business <hwg-business(at)mail.hwg.org>
Sent: Monday, August 26, 2002 9:18 PM
Subject: For your perusal


> I invite everyone to visit: http://etanow.com/ and have a look at
> my first Tableless code. By all means, rip it apart and if
> needed, let me have it with both barrels. Don't let the URL throw
> you (it's a spare of mine) as this will be the new look for my
> main site, PotentProducts.com. Note that only the 4 buttons up
> top & the first image, are working links. More work to do of
> course, but this is the general over-all layout.
>
> Although the Standards are met for XHTML 1.0 Transitional and CSS
> (htmlhelp.com doesn't like 'html>body' though?) I have found this
> very challenging to bring the coding up to (what I think) Triple
> A Accessibility Standards.
>
> Can someone explain to me why Bobby says:
>    "Separate adjacent links with more than whitespace."
> about links like this:
>    [Navigation] [Directories] [This Dir Menu]
>
> Says the same thing about image links using a <br> which I don't
> particularly agree with either. Mind you, I have yet to use a
> Speech Reader myself and am going by what I learned through book
> reading and online examples.
>
> Do we assign our "own" level of Accessibility if programs like
> Bobby do not apply common sense or do Reader programs truly have
> problems with links as listed above?
>
> Except for the "whitespace" problem I have coding (Tableless
> even!!!) that meets with Triple A requirements. Would love to be
> able to mention that and would truly appreciate, anyone using a
> Reader Program to "tell it like it is."
>
> All comments welcome and appreciated.
>
> Thanks,
>
>
> Website Rob
> Sitemaster at
> http://www.PotentProducts.com
> ------------------------------------------
> Helping people create a Potent Web Site
>
>
>

HTML: hwg-business mailing list archives, maintained by Webmasters @ IWA