WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Table headers not behaving

for

From: ::kevination::
Date: Sep 10, 2002 11:00AM


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Foliot - bytown internet wrote:
>
> Developing complex tables is work enough to ensure accessibility, do we need
> to also work around software bugs? Everybody has their role to play,
> including Freedom Scientific. While not everybody agreed with the WaSP
> stance (http://www.webstandards.org/) when they first emerged, two years
> later we have (generally) compliant browsers. So who was right?
>

Pro: No one get's left behind
By recognizing and accommodating the failings of various User
Agents(UA) we allow more people to access in the short-term. After-all
it's pretty damn hard to blame someone you don't even know for a buying
a non-standards compliant or buggy browser.

Con: Hacks are time-bombs
By coding hacks into our code we risk that some updated UA is going to
interpret the hack incorrectly. Essentially we are leaving a time-bomb
in the code and daring UA developers to trigger it. In the long-term
this may reduce the number of people able to access your information.

The answer for me is to never use hacks.

I don't always succeed. If I do end up using a hack I try to educate the
client on the consequences. I may also apologize for not recognizing the
problem before I hit development. I also include a clear explanation of
the hack in the code. My hope is that when the hack does explode,
another developer will understand my comment and be able to develop a
new fix quickly.

The real answer may lie in linking Accessibility compliance with
software quality liability legislation. Such a solution may also cause
more problems than it would solve.

- --
- ---
kevin D. white
email, <EMAIL REMOVED>
im, simplecypher
- ---
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.90-nr1 (Windows 2000)

iQIVAwUBPX4xXe4zpFgPJZelAQJk3hAAkwO2CUvqJMRBp3p4nXqJlU7cfuJMCPsw
5Rw2uMTYQdTzqqI45Rc+Ywe0dUDwuY8pNstd4Wd0d2Vpn3e0XlTs6aOMOjYPFh00
6ROIEsmGq0YNWABtXZKq0ELfM3JT2ynkwJoC5tNjUqpxbfP/+W3hBhHzJJX2q2uS
y+44Oi6VRTA+mLcUIFvKVmtCxlJibf/QdSSDuV9DPyef6SHt4VoWY9smo9/2Blg9
y6B0SPUOTDnklHs3/H3XwH5ZTNl2lUACQgq1zVt9osy3rNvoK+Wlm5YWekhNmrdB
efBcN2Vjx+W+SDFFn9EnnVYD+sw46AbxYBPRcbfhuPwzRW8chzfd/OXOs1p/xztX
HsBN0n+tSghy7LIUJ8QorrkweAUw6vT0fUgaJdCv0unQ4OZAKOxY7/8S9ae0D3Dq
X8Y4rRGrkrnLf0ruCr0F//FE7I9XpJg5nw1suWf61RPdUj7qw9Uo+MBGjKcKR28E
e3nLHc/WIlBPFavTIFyx5Djs2ZqqcgPeJTxX635Lbr6rc0R9CmSZg2wK8+qL4ZOg
Px3mibxPSExGfZY7ZrMG7mTzrMKlC2/Da+byEbI2u6KlmlQMXkhGl0p8NHzDgpZK
xFFxc8jzt3babVc6G/3dk3y5O5oAj5BwX7pts7NMvV3WJEi3YkRnoVlpY54tPdOw
gxXQdi+LURA=
=T4kT
-----END PGP SIGNATURE-----


----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/