Skip to content
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.

Throughout - External resources (Michael Cooper) #53

Closed
darthcav opened this issue Aug 27, 2014 · 1 comment
Closed

Throughout - External resources (Michael Cooper) #53

darthcav opened this issue Aug 27, 2014 · 1 comment

Comments

@darthcav
Copy link

Reference

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

Original Comment

Some sections that refer to external resources should be fleshed out more. Although the external resource covers the topic, the point of this document is a one-stop shopping for this viewpoint of the issues, and the document should provide basic understandings and refer externally only for more details. The section on content encodings just says "pay attention to it", and doesn't even get into content language even though the heading implies it. The section on DOM seems to imply background knowledge and a parser / model builder that should be more explicit. Content negotiation can lead to many different but similar views, one of the gotchas of comprehensive evaluation. Session tracking support also can have big implications on how a tool plays with a site.

@nitedog nitedog changed the title External resources (Michael Cooper) Throughout - External resources (Michael Cooper) Sep 1, 2014
@nitedog
Copy link
Contributor

nitedog commented Sep 1, 2014

Resolution

Accept - but beware not to add even more basic background! the guidance should always be related to "how does this impact web accessibility evaluation". Section 2.1.2 does not clearly do that, as Michael points out.

All the sections have been reviewed from this perspective.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants