- From: Kynn Bartlett <kynn-edapta@idyllmtn.com>
- Date: Sat, 9 Feb 2002 12:05:26 -0800
- To: Nick Kew <nick@webthing.com>, Jason Megginson <jason@bartsite.com>
- Cc: <w3c-wai-ig@w3.org>
At 7:32 PM +0000 2/9/02, Nick Kew wrote: >On Wed, 6 Feb 2002, Jason Megginson wrote: > > Should I not use the scope method for table headers? > >For **** sake, don't do that! If something is clearly a browser bug, >then it's the browser that should be fixed, but if you start working >to the bug instead of the standard, you'll just perpetuate it. >Unless the browser bug is of critical severity, pandering to it is >just another variant on trendy-1995 Netscapization. Actually, it depends on what you're doing and how you're doing it. If you're doing server-side tweaks for browser bugs -- highly advisable in this day and age -- then this makes perfect sense to remove scope attributes if you know they're going to cause problems with certain browsers or assistive technologies. Until those user agents are fixed, you'll want to use workarounds which don't break the standard, or else you may be cutting off far more _real_ users with disabilities than you will _theoretical_ users of standards-compliant software which doesn't exist yet. --Kynn -- Kynn Bartlett <kynn@idyllmtn.com> http://kynn.com Chief Technologist, Idyll Mountain http://idyllmtn.com Web Accessibility Expert-for-hire http://kynn.com/resume Next Book: Teach Yourself CSS in 24 http://cssin24hours.com
Received on Saturday, 9 February 2002 15:03:58 UTC