Section 2.1 - Non-HTTP resources (Michael Cooper)

[darthcav]

Reference

http://lists.w3.org/Archives/Public/public-wai-ert-tools/2014Aug/0008

Original Comment

The doc should talk about the limitations and benefits of evaluating content not sent over http(s). In addition to not having some of the http environment information, such content may be composed largely of scripts or templates that are hard to analyze with tools. However, a tool well integrated with a particular system could deliver more useful reports.

Another challenge of trying to evaluate over http(s) is there could be a large number of relevant environment permutations that it is impractical to test comprehensively. While that problem is maybe referred to the evaluation methodology it should be acknowledged here.

[nitedog]

Resolution

Partial - WCAG2 defines "web pages", thus "web content", as that delivered via HTTP(S). We briefly could mention other delivery protocols but I think they are (as main content delivery), less widely used. We also have some mention of platform integration in section 2.4.1, so we should only cross reference rather than repeat this here.

[ysmartin]

I favour considering local content retrieval, it is useful for contents not to be distributed through http, but distributed as a bundle (e.g. local help packages, local hypertext/hypermedia apps, widgets). I understand nonetheless the need to align to WCAG 2 definition.