- From: Kynn Bartlett <kynn@idyllmtn.com>
- Date: Mon, 14 Jan 2002 14:49:16 -0800
- To: "Phill Jenkins" <pjenkins@us.ibm.com>, w3c-wai-er-ig@w3.org
At 4:03 PM -0600 1/14/02, Phill Jenkins wrote: >I wouldn't add it. I don't consider it an accessibility tool. It's not >transforming or filtering anything . It's more like turning off JavaScript >or other settings in the browser. The question to ask is: "Can a user with >a disability now use the site with this tool without breaking necessary >functionality?" Perhaps it could be part of user agents - or add-ons to >compliment user agents so they can meet UAAG. Tools are used by developers >and content providers, browsers and plug-ins are used by consumers. This distinction makes sense to me -- although it's possible we may have to revisit the distinction between content providers and consumers in the future, the Web is still far from that in practical use today. --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 January Web Accessibility eCourse http://kynn.com/+d201 Forthcoming: Teach Yourself CSS in 24 Hours
Received on Monday, 14 January 2002 18:09:19 UTC