You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: