- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Wed, 1 Apr 2009 09:04:24 -0500
- To: Ramón Corominas <listas@ramoncorominas.com>
- Cc: Phill Jenkins <pjenkins@us.ibm.com>, w3c-wai-ig@w3.org
- Message-Id: <F945D875-5F4B-4F1B-A2A9-CE0D856E8CB5@trace.wisc.edu>
A few points to consider in this discussion. - plug-ins are considered user agents by WCAG. In fact AT is also considered part of the user's user agent. - plug-ins should be distributed in an accessible manner especially when they may be required to be added in the middle of a browsing session in order to complete it. - WCAG should be thought of as a ruler. It is a way to measure accessibility. As pointed out, it is up to policy level decisions (not the ruler) to determine what measure should be required where. - Note that "technologies" are not what is required to be accessibility supported. (this was an early error on our working group's part in describing this) It is "uses of a technology" (i.e. techniques) that need to be accessibility supported. Even HTML can be used in ways that are not accessibility supported. The rule is --- the way you use the technologies on your page must be accessibility supported if you are depending on them to conform to WCAG. - as to the level or extent that a "use of a technology" must be 'accessibility supported' - that also is matter of policy and not specified within WCAG (remember the ruler role). We would hope that the use would be widely supported by AT that is in use by people with disabilities. Gregg ----------------------- Gregg Vanderheiden Ph.D. Director Trace R&D Center Professor Ind and Biomed Engr University of Wisconsin-Madison > >
Received on Wednesday, 1 April 2009 14:05:20 UTC