W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2005

RE: issue about the WCAG and XSLT

From: Michael Cooper <michaelc@watchfire.com>
Date: Sun, 13 Mar 2005 15:41:15 -0500
Message-ID: <A0666B3C59F1634290FDC88674D87C3202124C76@1WFEMAIL.ottawa.watchfire.com>
To: <w3c-wai-gl@w3.org>

I'll take a stab at answering your questions. I think the question of whether client-side XSLT causes issues with WCAG requirements depends on how we resolve what is now known as "the baseline question". But in principle, if we can count on proper client support for the XSLT, and the output of the XSLT meets WCAG requirements, then this should be WCAG conformant. But this is my opinion and reflects my own take on the baseline discussion. I do believe the evaluation is in context of the transformed document, not the original, because evaluation is in context of what the user actually experiences; how you get to that experience is not relevant. Michael

> -----Original Message-----
> From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org]On
> Behalf Of Luca Mascaro
> Sent: March 10, 2005 5:45 PM
> To: w3c-wai-gl@w3.org
> Subject: issue about the WCAG and XSLT
> 
> 
> 
> A general question about the WCAG:
> 
> If in a page we use XSLT at client side, this one compromise the
> accessibility of the page?
> And, in this document, the accessibility evaluation is about 
> the original
> document or about the (virtual) transformed document?
> 
> Regards
> 
> Luca Mascaro
> IWA/HWG Member
> 
> 
> 
> 
Received on Sunday, 13 March 2005 20:41:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:36 GMT