RE: DPUB Set of Web Pages

I think as Tzviya Siegman noted on the call today, that the  ‘Packaging on the Web’ W3C First Public Working Draft 15 January 2015 document might be useful here.

 

​​​​​

 

 

 

* katie *

 

Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 |  <https://twitter.com/Ryladog> @ryladog

 

From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Tuesday, November 22, 2016 3:47 PM
To: James Nurthen <james.nurthen@oracle.com>; w3c-wai-gl@w3.org
Subject: RE: DPUB Set of Web Pages

 

 

 

From: James Nurthen [mailto:james.nurthen@oracle.com] 
Sent: Tuesday, November 22, 2016 3:32 PM

I wonder if WCAG2ICT could be useful in this

https://www.w3.org/TR/wcag2ict/#keyterms

[Jason] It’s addressing the same problem, which is not specifically related to digital publishing. Suppose that someone creates a compressed archive file containing WCAG 2.0 and associated Techniques documents, then uploads it to the W3C Web server. It now has a single URI, and it isn’t entirely clear whether it meets the definition of “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”.

 

Of course, if ftp or some other distribution mechanism were used instead of HTTP, then the archive file clearly fails to meet the definition.

 

This problem is no doubt familiar to the Mobile Accessibility Task Force participants in connection with Web-based content (HTML/CSS/JavaScript) distributed as mobile applications. I think there is a need to consider broadening the definition, but I don’t have a good proposal yet.

 

 

  _____  

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

 

Thank you for your compliance.

  _____  

Received on Tuesday, 22 November 2016 21:18:16 UTC