|
|
Posted by dorayme on 06/10/06 23:24
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... :)
[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]
--
dorayme
Navigation:
[Reply to this message]
|