- From: Dana Simberkoff <danalouise@hisoftware.com>
- Date: Wed, 14 May 2008 17:51:37 -0400
- To: "Jan Richards" <jan.richards@utoronto.ca>, "WAI-AUWG List" <w3c-wai-au@w3.org>
- Message-ID: <680477E5249362459DB89AE89482B7D101712410@be06.exg3.exghost.com>
Jan- Sorry if I am miss-understanding your meaning here-but to your point with regards to checkers-are you saying that the checker should be configurable by the user in such a way that the user can identify the technologies (AT or User Agent) that should be supported-and then based on those settings-check against that? Thanks- Dana Dana Louise Simberkoff HiSoftware Inc. www.hisoftware.com <http://www.hisoftware.com/> Phone: +1-603-578-1870 x11 Mobile: +1-603-496-0359 ________________________________ From: w3c-wai-au-request@w3.org on behalf of Jan Richards Sent: Wed 5/14/2008 4:44 PM To: WAI-AUWG List Subject: Authoring tools and WCAG 2.0's "Accessibility Supported" Just a thought... Looking at WCAG 2.0's concept of "Accessibility Supported" (http://www.w3.org/TR/WCAG20/#accessibility-supporteddef) I started wondering about support that authoring tools might provide. Checkers aren't likely advanced enough yet but I can imagine multi-format checkers that would have settings re: which technologies the user believed to be accessibility supported. (or similarly at the stage of choosing formats) Any other thoughts? Cheers, Jan The information in this transmittal (including attachments, if any) is privileged and confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal. Thank you.
Received on Wednesday, 14 May 2008 21:56:50 UTC