RE: bug in Web Page definition

That is correct Jason.


An HTML page that is not on the Web is not a Web Page.

This is not to say that you cannot use the same guidelines for that page
that are used for Web pages if you choose.   You could also use many of them
for HTML Help files and other HTML or Flash or PDF or other non-Web
documents that use similar technologies to those used on the Web.

Sometimes all of the WCAG guidelines can be used.  Other-times only some of
them.


Gregg
 -- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: w3c-wai-gl-request@w3.org
> [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Jason White
> Sent: Saturday, November 03, 2007 7:16 PM
> To: w3c-wai-gl@w3.org
> Subject: Re: bug in Web Page definition
>
>
> On Sat, Nov 03, 2007 at 01:30:56PM -0500, Gregg Vanderheiden wrote:
>
> > Web Page
> >
> >
> > a non-embedded resource [obtained] from a single URI [using
> HTTP] plus
> > any other resources that are used in the rendering or
> intended to be
> > rendered together with it by a user agent
> > <http://www.w3.org/WAI/GL/WCAG20/#useragentdef>
> >
> >
> >
> > Comments?
>
> By this proposal, the very same resource can be a Web page if
> I obtain it via HTTP, but not a Web page if it is on my local
> file system, acquired via an NFS-mounted remote file system, etc.
>
> What's the problem this is trying to solve? Resources
> obtained by ftp generally aren't rendered by a user agent;
> they are saved to a local file system. If they are rendered
> by a user agent, then surely they should count as Web pages
> (e.g., a collection of HTML documents on an ftp site).
>
> Resources referred to by the Mailto: URI scheme aren't
> rendered by a user agent; they are used to send mail, not to
> receive it.
>
> Thus I don't understand the problem which this is trying to address.
>
>

Received on Sunday, 4 November 2007 04:53:09 UTC