> You should add a section on accessibility and structured
> document coding, and in that section advise Web monsters
> NOT to use CSS-positioning and DOM to manipulate
> navigational controls (e.g. dynamic menus) and to make
> animations (no option for user to pause or slow animations).
> Should people pay more attention to accessibility, most of
> compatibility problems would be gone already.
I'd rather not. I'll explain some ideas of mine. IMO there are several
levels a web developers can achieve with his page:
Level 0 - Page complies with standards. JS and layout don't break.
Level 1 - Page can be navigated with any browser (accesibility,
"alt"'s).
Level 2 - Page uses tags appropiately (except tables).
Level 3 - Page doesn't use tables.
(Note that I haven't mentioned validation. A valid page could in fact be
worse than a non-valid one).
My idea is to help people to achieve "level 0". I try to help the author
to do what he wants, not what *i* want him to do, not to try to convince
to change the way he has always created pages. Of course I'd like to be
able to be succesful in making people comply with all these levels, but
I'm afraid that if I try other levels I will loose the readers!
At least in this article, which aims to be like a "checklist" kind of thing.
