- From: Roberto Scano - IWA/HWG <rscano@iwa-italy.org>
- Date: Mon, 25 Apr 2005 19:43:02 +0200
- To: "Phill Jenkins" <pjenkins@us.ibm.com>
- Cc: "Jan Richards" <jan.richards@utoronto.ca>, <jongund@uiuc.edu>, <w3c-wai-au@w3.org>
----- Original Message ----- From: "Phill Jenkins" <pjenkins@us.ibm.com> To: "Roberto Scano - IWA/HWG" <rscano@iwa-italy.org> Cc: "Jan Richards" <jan.richards@utoronto.ca>; <jongund@uiuc.edu>; <w3c-wai-au@w3.org> Sent: Monday, April 25, 2005 7:21 PM Subject: Re: ATAG requirements on accessible authoring interfaces Impossible? Isn't this the responsibility of the assistive technology? ZoomText and Majic are just a few of the magnifiers that handle this all the time. The "chrome" of the browser also has some of the responsibility - for example the zoom feature in the browsers. The point here is that the client is doing the magnification, not the server that is sending the HTML in a Web based authoring tool. Another point here - the requirement or need of authors with low vision is valid, but the placement of the responsibility of the solution on the authoring tool vendor is not, in my opinion, correct or most efficient. That is the role of the assistive technology. Only the enablement of the authoring tool to not prevent the use of magnifiers and zoom features is required here. Roberto Scano: I think this is not responsability of the assistive tecnology: ATAG refer to the authoring tools (web or "client side").
Received on Monday, 25 April 2005 17:43:46 UTC