Posted by Chaddy2222 on 06/11/06 04:12

dorayme wrote:
> In article
> <1149948759.860382.60700@j55g2000cwa.googlegroups.com>,
> "Chaddy2222" <rockradio2000@yahoo.com.au> wrote:
>
> > Also, I know some of my spelling might not be that flash, but it's
> > better then your TOTAL DISREGARD FOR WEB ACCESSIBILITY!!!.
> > --
> > Regards Chad.
>
> Hi Chad, I am extremely interested to ask you a couple of things
> because of the way you must be using computers and reading
> websites. I realise that general table layout has many faults
> but what I want to hear is an accurate view of how much of a
> stumbling block, if any, it is in simple cases compared with,
> say, an equally simple css driven organization of material.
>
> Imagine a table layout that has just two cols and one row,
> navigation in a list in one col, content in the other. Lets say
> the nav col is read out first. In addition, the navigation col
> has information as to which "link" corresponds to the content
> that is presently available in the other.
>
> All this compared to say a navigation list in one div ("floated
> left" in the css) and a content section in another div.
>
> I would be keen to hear anything you might comment on in this
> regard that I am not likely to hear normally. What is it actually
> like? There is a "summary" in the table saying what the two cols
> are for, it being simple enough. From there on, how awkward an
> experience is it? Compared with the two div arrangement?
>
> Used to have a blind student, he was top of the class, I would
> ask him if I could find him these days - he went on to greater
> things and left me in his brilliant wake... :)
Ha, fare enough.
Well, take my older website as an example, it is still where the web
design tips pages are http://freewebdesign.cjb.cc/design-tips.html Jaws
v 5.0 my Screen Reader of choice has no problems accessing the content
from that site. It is a simple two colum table with links on the left
and content on the right. As you can see.
Where it can have problems is with tables with moltiple colums and
rows, it reads something like: "Table has 6 colums and 17 rows. In your
example it would say that it has two colums and, well actually it may
just read the layout sumary and ignore the rest. So if a table with a
large amount of nested colums is to be used for layout, it needs to
have a sumary. If it doesn't the less clood up people will tab around
the table looking for the data.
Compare that with a three colum div layout, Jaws ignores the layout and
just reads the content, useually the nav first, depending on what the
author sets in the CSS, which is really how it should be.

>
> [Sorry to hijack this thread, but here you are and here am I..
> and come to think of it, it might not be so bad considering OP is
> being so "tough-minded" to go into it a bit. He seems a
> reasonable bloke underneath and he might come around a bit in the
> end]
Yes, I know what you mean their.
A note to the op. If you can't get your design to work useing pure CSS
for layout, with a bit of simple HTML to help it a long. Then you need
to scrap your design and start again.

--
Regards Chad. http://freewebdesign.cjb.cc

[Back to original message]