See also: IRC log
No change - we would like to keep the scope of the document applicable to managing web accessibility. Other comments received may add to the current list of features to better address this aspect.
Refer to Issue #31 about changing the document title
<scribe> ACTION: shadi to contact Annika and ask if she has examples for features related to "managing accessibility" [recorded in http://www.w3.org/2014/08/27-er-minutes.html#action01]
<trackbot> Created ACTION-139 - Contact annika and ask if she has examples for features related to "managing accessibility" [on Shadi Abou-Zahra - due 2014-09-03].
http://www.w3.org/WAI/eval/selectingtools
Think it is an interesting idea. Want to think about making this document less focused on developers, and cross link to the "selecting tools" document which should be an intro on eval tools in more layman terms
SAZ: would like to suggest this idea to EO
CV: open to the idea
SM: document should address the "creation" of
tools rather than the audience "developers"
... "content authors" and other audiences she mentions are not part of the
agreed target audience, though
[[This document describes features that web authoring and quality assurance tools can incorporate, so that they support the evaluation of accessibility requirements, such as those defined by the Web Content Accessibility Guidelines (WCAG) 2.0. The main purpose of this document is to promote awareness of such tool features and to provide introductory guidance for tool developers on what kind of features they could provide in future implementations of their tools.]]
<scribe> ACTION: shadi to discuss with EOWG the idea of removing "developers" from the title and aligning WAET with "Selecting Tools" document [recorded in http://www.w3.org/2014/08/27-er-minutes.html#action02]
<trackbot> Created ACTION-140 - Discuss with eowg the idea of removing "developers" from the title and aligning waet with "selecting tools" document [on Shadi Abou-Zahra - due 2014-09-03].
<scribe> ACTION: velasc to check Issue #47 before publication [recorded in http://www.w3.org/2014/08/27-er-minutes.html#action03]
<trackbot> Error finding 'velasc'. You can review and register nicknames at <http://www.w3.org/WAI/ER/tracker/users>.
<scribe> ACTION: cvelasc to check Issue #47 before publication [recorded in http://www.w3.org/2014/08/27-er-minutes.html#action04]
<trackbot> Error finding 'cvelasc'. You can review and register nicknames at <http://www.w3.org/WAI/ER/tracker/users>.
<scribe> ACTION: carlosv to check Issue #47 before publication [recorded in http://www.w3.org/2014/08/27-er-minutes.html#action05]
<trackbot> Created ACTION-141 - Check issue #47 before publication [on Carlos A. Velasco - due 2014-09-03].
http://w3c.github.io/wai-eval-tools/
No change - We are aware that the current tools list is outdated and are actively working on an updated version, that we expect will be available before the next publication, as already stated.
<scribe> Closed - This document does not prescribe the use of any of the features it contains. It only lists such features. Whether readers consider EARL to be irrelevant is outside the scope of the document. The working group considers that pointing to existing languages, such as EARL could be of benefit to the reader. Furthermore, the document mentions other alternatives to reporting results, such as CSV or JSON. We will review the mentions of EARL and consider toning it do
wn where necessary. See also Issue #13 and #23 for more specific actions.
<scribe> ACTION: carlosv to check Issue #7 before publication [recorded in http://www.w3.org/2014/08/27-er-minutes.html#action06]
<trackbot> Created ACTION-142 - Check issue #7 before publication [on Carlos A. Velasco - due 2014-09-03].