W3C

Site Navigation

Nearby

Results of Questionnaire EOWG Publication Approval – Selecting Evaluation Tools Changes

The results of this questionnaire are available to anybody. In addition, answers are sent to the following email address: shawn@w3.org

This questionnaire was open from 2017-12-13 to 2017-12-20.

13 answers have been received.

Jump to results for question:

  1. Selecting Evaluation Tools Changes Approval

1. Selecting Evaluation Tools Changes Approval

summary | by responder | by choice

The resource has been updated, as detailed below. Please review the changes to confirm your satisfaction with the changes, and to approve its publication.

Due to the upcoming holidays, the time for review is shorter. Please feel free to ask for more time if you need it.

Summary

ChoiceAll responders
Results
I agree with the changes and approve publication. 9
I'm OK with publication as is; please consider my suggestions in GitHub (or below) for Editors' discretion. 2
I will approve publication only after my suggestions in GitHub (or below) are addressed. 1
I need more time, and will complete the review by the date in the Comments field below.
I abstain and accept the decision of the group. 1
fyi, I added some suggestions in GitHub (or below) to consider for later iterations. 1

Skip to view by choice.

View by responder

Details

Responder Selecting Evaluation Tools Changes ApprovalComments
Shadi Abou-Zahra
  • I agree with the changes and approve publication.
Norah Sinclair
  • I'm OK with publication as is; please consider my suggestions in GitHub (or below) for Editors' discretion.
 I very much agree with the changes and approve publication. I just noticed the style of the descriptions under these two bullet points are written in fragments, whereas, all of the other descriptions are full sentences:

Automatically Checks
The scope of what the evaluation tool can automatically test. Sometimes a single page. Other times entire groups of related pages. Some can also access password-restricted content.

License
Which licenses the evaluation tool offers, such as Open Source, Commercial, Enterprise, etc.

Suggest revising those descriptions to fit the style of the others:

Automatically Checks
The scope of what the evaluation tool can automatically test varies depending on the tool. Some tools check a single page, while others check entire groups of related pages. Some can also access password-restricted content.

License
Evaluation tools are available under a variety of license types, such as Open Source, Commercial, Enterprise, etc.

(Added an issue in github)
Sharron Rush
  • I agree with the changes and approve publication.
Brent Bakken
  • I agree with the changes and approve publication.
Nicolas Steenhout
  • I agree with the changes and approve publication.
Chris O'Brien
  • I agree with the changes and approve publication.
Eric Eggert
  • I agree with the changes and approve publication.
 Good work, I agree with Norah.
Robert Jolly
  • I agree with the changes and approve publication.
Vicki Menezes Miller
  • I agree with the changes and approve publication.
Jes Pulido
  • I'm OK with publication as is; please consider my suggestions in GitHub (or below) for Editors' discretion.
 The only thing I noticed -- and this may have been an intentional decision, so I'll let the editors decide -- is that the word "judgment" is spelled as "judgement." But then again, I'm accustomed to America-centric ways of spelling things.
Sylvie Duchateau
  • I abstain and accept the decision of the group.
Kris Anne Kinney
  • I agree with the changes and approve publication.
Shawn Lawton Henry Great to get this updated!

Edit Pull Requests:
* typo, grammar, & punctuation fixes (and I think all-agreeable copyedits) https://github.com/w3c/wai-selecting-eval-tools/pull/14/files
* [!!] Heading: What to Expect -> Can and Can't Do https://github.com/w3c/wai-selecting-eval-tools/pull/16
* [!!] Accuracy for credibility https://github.com/w3c/wai-selecting-eval-tools/pull/18
* lowercase anchors https://github.com/w3c/wai-selecting-eval-tools/pull/17

Issues:
* [!!] First sentence https://github.com/w3c/wai-selecting-eval-tools/issues/15
* [!!] Accessibility Information https://github.com/w3c/wai-selecting-eval-tools/issues/19

[done] Fixed spelling https://github.com/w3c/wai-selecting-eval-tools/commit/5014f90a491938db0975192b2a3689b654c82c2e#diff-d680e8a854a7cbad6d490c445cba2eba

---

<strong>Address in later revision</strong>:

I'm concerned that this revision requires a very high level of knowledge to make sense. I'm thinking of the people with no technical background who get named to lead their organization's Accessibility efforts. They are a target audience of this document, yet I think they will be lost in much of this revision. I think that in the chopping, some important explanation and some useful information and examples were cut. For example, most of the "Further Considerations" section seems not very helpful now. I put specific notes in an attachment to https://github.com/w3c/wai-selecting-eval-tools/issues/20

View by choice

ChoiceResponders
I agree with the changes and approve publication.
  • Shadi Abou-Zahra
  • Sharron Rush
  • Brent Bakken
  • Nicolas Steenhout
  • Chris O'Brien
  • Eric Eggert
  • Robert Jolly
  • Vicki Menezes Miller
  • Kris Anne Kinney
I'm OK with publication as is; please consider my suggestions in GitHub (or below) for Editors' discretion.
  • Norah Sinclair
  • Jes Pulido
I will approve publication only after my suggestions in GitHub (or below) are addressed.
  • Shawn Lawton Henry
I need more time, and will complete the review by the date in the Comments field below.
I abstain and accept the decision of the group.
  • Sylvie Duchateau
fyi, I added some suggestions in GitHub (or below) to consider for later iterations.
  • Shawn Lawton Henry

More details on responses

  • Shadi Abou-Zahra: last responded on 14, December 2017 at 19:52 (UTC)
  • Norah Sinclair: last responded on 15, December 2017 at 18:30 (UTC)
  • Sharron Rush: last responded on 18, December 2017 at 16:21 (UTC)
  • Brent Bakken: last responded on 19, December 2017 at 21:22 (UTC)
  • Nicolas Steenhout: last responded on 20, December 2017 at 15:07 (UTC)
  • Chris O'Brien: last responded on 20, December 2017 at 15:08 (UTC)
  • Eric Eggert: last responded on 20, December 2017 at 15:12 (UTC)
  • Robert Jolly: last responded on 20, December 2017 at 15:49 (UTC)
  • Vicki Menezes Miller: last responded on 20, December 2017 at 15:55 (UTC)
  • Jes Pulido: last responded on 20, December 2017 at 16:06 (UTC)
  • Sylvie Duchateau: last responded on 20, December 2017 at 16:34 (UTC)
  • Kris Anne Kinney: last responded on 20, December 2017 at 16:41 (UTC)
  • Shawn Lawton Henry: last responded on 21, December 2017 at 02:33 (UTC)

Non-responders

The following persons have not answered the questionnaire:

  1. Eric Velleman
  2. Andrew Arch
  3. Kazuhito Kidachi
  4. Jedi Lin
  5. David Sloan
  6. Mary Jo Mueller
  7. Reinaldo Ferraz
  8. Bill Kasdorf
  9. Cristina Mussinelli
  10. Kevin White
  11. Kevin Rydberg
  12. Adina Halter
  13. Denis Boudreau
  14. Laura Keen
  15. Sarah Pulis
  16. Bill Tyler
  17. Gregorio Pellegrino
  18. Ruoxi Ran
  19. Jennifer Chadwick
  20. Sean Kelly
  21. Muhammad Saleem
  22. Sarah Lewthwaite
  23. Daniel Montalvo
  24. Mark Palmer
  25. Jade Matos Carew
  26. Sonsoles López Pernas
  27. Greta Krafsig
  28. Jason McKee
  29. Jayne Schurick
  30. Billie Johnston
  31. Michele Williams
  32. Shikha Nikhil Dwivedi
  33. Brian Elton
  34. Julianna Rowsell
  35. Tabitha Mahoney
  36. Fred Edora
  37. Rabab Gomaa
  38. Marcelo Paiva
  39. Eloisa Guerrero
  40. Leonard Beasley
  41. Frankie Wolf
  42. Supriya Makude
  43. Aleksandar Cindrikj
  44. Angela Young

Send an email to all the non-responders.

Compact view of the results / list of email addresses of the responders

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire

Report issues on GitHub project w3c/wbs-design or by mail to sysreq.