See also: IRC log
SM: send comment by mail
... rewrite ok, more or less the same thing but changed the order
... concerned if the abstract includes tools that are out of scope
"Similarly, a web quality assurance tool might not check for accessibility criteria but might provide other functionality, such as for managing quality assurance processes and reporting evaluation results, that may be useful for web accessibility evaluation."
SAZ: think they are in scope - any reason not to have them in scope?
SM: no, not opposing but we currently don't have matching features
SAZ: would it be a problem to keep the scope broader for this first publication?
CV: can't write features for that
SAZ: actually relates to section 2.2.2
... suggest we not limit the scope in this version
... and see what feedback we get
CV: ok with me
... "fully-automated, semi-automated, and manual web accessibility evaluation"
is introducing a different categorization
[[It applies to tools that are specifically designed to evaluate the accessibility of web content and to general purpose web quality assurance tools, as well as to accessibility checking functionality built into web authoring tools, plug-ins for web browsers, and many other types of tools used throughout the design, development, and maintenance of websites.]]
SM: when can we expect publication?
SAZ: first public working draft needs several approvals, probably not beffore june 12
RESOLUTION: approval for publication as first publication working draft