- From: Roberto Scano - IWA/HWG <rscano@iwa-italy.org>
- Date: Fri, 6 May 2005 20:58:37 +0200
- To: "Gregg Vanderheiden" <gv@trace.wisc.edu>, "'John M Slatin'" <john_slatin@austin.utexas.edu>, <lguarino@adobe.com>
- Cc: <jasonw@ariel.its.unimelb.edu.au>, "'Web Content Guidelines'" <w3c-wai-gl@w3.org>
----- Original Message ----- From: "Gregg Vanderheiden" <gv@trace.wisc.edu> To: "'John M Slatin'" <john_slatin@austin.utexas.edu>; <lguarino@adobe.com> Cc: <jasonw@ariel.its.unimelb.edu.au>; "'Web Content Guidelines'" <w3c-wai-gl@w3.org> Sent: Friday, May 06, 2005 8:48 PM Subject: RE: RE: working definition of baseline Interesting How about this slight edit to the end - to say that it is what is required to get full access to the content. That may address your comment/concern. <new NewProposal> Any minimum set of technologies assumed in the design of accessible Web Content to be supported by, and enabled in, all user agents capable of providing full access to the information and functionality of the content. </newNewProposal> Roberto Scano: Sorry but, at least, this isn't like a classic "Software requirements"? So, why not refer - instead of "baseline" - to "User interface requirements" ?
Received on Friday, 6 May 2005 18:58:53 UTC