but does have very strong ideas as to how a site should look and feel.
it can do, but with knowledge based on experience of very bad design.
> scripts break the accessibility issues, would do the correct approach.
Although it may seem that I am absolutely against scripting, I'm not.
a web resource, and I would rather not have cosmetic only scripting.
they stand legally, without having to take a risk.
> regards to the information presented/attained."  And leave it to that.
it is almost always possible to drop presentation but retain content.
advertising is not about information.
only to make the page easier to use, not to provide additional information.
application that is appropriate for HTML where not having "instantaneous"
feeback would make the site unusable.
feature testing, and never by trying to match the user agent string.
not buy it, even though that was done because it is bad for accessibility.
disability, with no financial constraints, only) accessibility.
only option to preserve the intellectual property.
Next message: David Woolley: "Re: Heading markup in tables"
Previous message: David Woolley: "Re: More scripting thoughts Pt. 2 (was RE: Accessible road maps)"
In reply to: Steven Dale: "Banning and Guidelines V Techniques"
Next in thread: Sailesh Panchang: "Heading markup in tables"