- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Fri, 23 Aug 2013 10:59:04 -0500
- To: "public-wcag2ict-tf@w3.org Force" <public-wcag2ict-tf@w3.org>
- Message-Id: <537827B8-13C1-4895-A93A-87067992A58C@trace.wisc.edu>
Someone asked me the definition of non-web. and I went to WCAG2ICT to see and we don't define it we define document but not non-web though we use it everywhere I don't know if we need to define it -- but if we do - (and is suspect we might) here is one to look at -- and a heads up that this will be on todays discussion at least. non-web (as used in WCAG2ICT) not obtained from a URI using HTTP, and not a resource that is only used in the rendering or intended only to be rendered together with something obtained from a URI using HTTP. RATIONALE WCAG2ICT is about things that are not already covered by WCAG WCAG applies to things obtained from a URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it Gregg -------------------------------------------------------- Gregg Vanderheiden Ph.D. Director Trace R&D Center Professor Industrial & Systems Engineering and Biomedical Engineering University of Wisconsin-Madison Technical Director - Cloud4all Project - http://Cloud4all.info Co-Director, Raising the Floor - International - http://Raisingthefloor.org and the Global Public Inclusive Infrastructure Project - http://GPII.net
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 23 August 2013 15:59:33 UTC