Re: For your perusal

Hi Rob,

I haven't visited the page (I am working offline now) but I am blind and I
use a screen reader.
The idea is that you shouldn't care about all the accessibility standards
because some of them have no sense.

For example, you can put links one after another even without a space.
The screen readers read the HTML code and not the screen only, and know what
to read.

I've seen other things that are not helpful at all like the fact that a form
field should contain a default value and not be empty.

There are a lot of tags used in the <table> that are not important at all
for a screen reader.
However, if I used a html validator like tidy DBG, it tells me that my html
code is not valid.

For someone who use a screen reader, the most important things on a web page
are:
- Not to have Java applets because they are not supported.
- not to have Flash annimations, because even though they are supported by 2
screen readers, the support is not very good.
-To have alt tags for images.
-A design thing: Not to repeat the same links on all the pages and put the
links on the top of the page.
- Not to use a meta refresh to the same page because the focus will move to
the top of the page and this problem can't be solved by most screen readers.

Teddy's Center: http://teddy.fcc.ro/
Mail: orasnita(at)home.ro

----- Original Message -----
From: "Rob Atkinson" <robatkinson(at)nucleus.com>
To: "hwg-business" <hwg-business(at)mail.hwg.org>
Sent: Monday, August 26, 2002 11: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