- From: Marja-Riitta Koivunen <marja@annotea.org>
- Date: Wed, 24 Mar 2004 13:15:29 -0500
- To: Matt May <mcmay@w3.org>, jasonw@ariel.ucs.unimelb.edu.au
- Cc: "Roberto Scano - IWA/HWG" <rscano@iwa-italy.org>, <w3c-wai-gl@w3.org>
I think most of the data will end up to be presented to the humans in one way or the other even when it goes through some intermediate processing by the machines. It is good to keep accessibility in mind when storing, retrieving and processing data. In that way we can make sure that when the data is presented for the users it has a better chance to be accessible. Marja At 08:29 PM 3/23/2004 -0800, Matt May wrote: >On Mar 19, 2004, at 2:15 AM, Jason White wrote: >>On the other hand, suppose there is a collection of XML data that is >>transferred over the Web, but which is not designed or intended to be >>presented in a user interface. This is the kind of example that is >>usually treated as not being Web content, and to which the guidelines >>don't >>apply. >> >>Question: is there a more accurate way of defining or characterizing >>content which is not designed to appear in a user interface? > >MM: >Yes. It's in WCAG 2 [1]: > >These principles apply only to Web content presented to a human reader. >A structured database or metadata collection where the data is intended >for use by another machine, and that requires no interface, lies >outside the scope of these guidelines. > >- >m > >[1] >http://www.w3.org/TR/2004/WD-WCAG20-20040311/#overview-design- principles >
Received on Wednesday, 24 March 2004 17:04:27 UTC