W3C home > Mailing lists > Public > w3c-wai-au@w3.org > October to December 2012

Re: Towards a description of ATAG 2.0's approach to testing

From: Greg Pisocky <gpisocky@adobe.com>
Date: Mon, 1 Oct 2012 12:43:35 -0700
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <64BAFF76F7529141BBCFE3457F1D81AD016A32BAD84C@NAMBX02.corp.adobe.com>
The issue of producing accessible content is also something ATAG 2.0 addresses which should also be addressed in the testing. The application may be accessible, but the output or one of its many outputs may be inaccessible or highly inaccessible. If you use tools x which produces content in formats A, B, and C be aware that A and B are not terribly accessible and should be avoided in favor of C.

Greg

[cid:image001.png@01CD9FEB.84B52F50]

Greg Pisocky
Sr. Business Development Mgr.
Adobe Accessibility

571.765.5410 (tel)
703.678.3541 (cell)
gpisocky@adobe.com

7930 Jones Branch Dr.
McLean, VA 22102
www.adobe.com







Adobe's Accessibility Resource Center | www.adobe.com/accessibility<http://www.adobe.com/accessibility>
Product Compliance Info | http://www.adobe.com/accessibility/products/compliance/




image001.png
(image/png attachment: image001.png)

Received on Monday, 1 October 2012 19:44:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:03 UTC