w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire Scripts for Evaluation Intro Videos (Updated)
The results of this questionnaire are available to anybody. In addition, answers are sent to the following email address: shadi+EOsurvey@w3.org
This questionnaire was open from 2019-09-09 to 2019-09-12.
13 answers have been received.
Jump to results for question:
- Introduction
- Video 1: Evaluation Overview
- Video 2: Preliminary Evaluation
- Video 3: Selecting and Using Tools
- Video 4: Comprehensive Evaluation
- Video 5: Involving Users
- Other Comments
1. Introduction
This survey is to collect input from EOWG on the updated scripts for the evaluation intro videos. Please provide your input in this form and do not edit the wiki directly to avoid confusion.
This is a detailed review, including of grammar, spelling, and wording preferences (especially for the spoken audio). For the visuals, please note further ideas you may have, which we will provide to the video production company as input.
Please enter in the comment field below by when you plan to complete this survey if you cannot complete it by the deadline of 12 September 2019.
Some of the major changes from the previous version of the scripts:
- Shorter intro video with more direct references to the WAI resources
- Tightened language in all videos, and tried to use more casual tone
- Full name of the referenced resources is read aloud by the narrator
Details
| Responder | |
|---|---|
| Vicki Menezes Miller | Very nice overall. |
| Brent Bakken | |
| Lewis Phillips | 11 September 2019 |
| Norah Sinclair | Can complete survey by Friday, September 13 |
| Sylvie Duchateau | |
| Eric Eggert | |
| Laura Keen | I reviewed the audio fully and have no substantive comments. My review of the visual content was not as thorough and it was difficult for me to comment. I guess my brain was not translating the text to a visual easily. :( |
| Kevin White | |
| Mark Palmer | |
| Estella Oncins | Excellent content. |
| Helen Burge | I do not have any additional comments on the scripts as looks like a great update to me. |
| Howard Kramer | |
| Shawn Lawton Henry | Really like this iteration! From my perspective, with a few minor changes, we can call them done. Note: Unless indicated otherwise, all comments below are low-medium-ish for editor's discretion. :-) |
2. Video 1: Evaluation Overview
Please carefully review the script for Video 1: Evaluation Overview.
Please indicate any comments you have on:
- The spoken audio
- The illustrative visuals
- The overall duration
- Anything missing?
- Anything to remove?
- Any other observations?
Details
| Responder | Video 1: Evaluation Overview |
|---|---|
| Vicki Menezes Miller | Very nice. Flows well. |
| Brent Bakken | Good overview. I like how it quickly goes through a list of resources available with the visuals of what they look like. No changes needed that I see. |
| Lewis Phillips | looks ok |
| Norah Sinclair | |
| Sylvie Duchateau | 1. Following sentence may be a bit complicated to understand, simplify? Actual text: "It is ideally carried out throughout the design and development process, to avoid costly repairs during later stages." Proposal: "Ideally, carry out throughout the design and development process, to avoid costly repairs during later stages." Rationale: active voice is easier to understand for some people. 2. Add a comma to make the sentence easier to follow. Actual text: "With these resources you can learn how to check your website for accessibility barriers and prioritize the issues you need to address first." Proposal: With these resources, you can learn how to check your website for accessibility barriers and prioritize the issues you need to address first." 3. Last sentence, what about writing it the other way around? Actual text: "Visit w3.org/WAI/evaluation for more information on evaluating web accessibility." Proposal: "for more information on evaluating web accessibility, visit w3.org/WAI/evaluation. |
| Eric Eggert | |
| Laura Keen | 11 82-95 To help you better understand how users experience your website and applications, W-A-I provides the resources "Involving Users in Web Projects for Better, Easier Accessibility". [remove period at the end of this line. the sentence continues in the next sequence] |
| Kevin White | 3: Would be good to mention something of the iterative aspect of the approach. Related to this on the visuals, I am not sure that Lego or Tetris conveys that iterative nature of integration. 7 - 12: Visuals have a lot of screen moving and zooming - couple of things; firstly, the moving could have the same distracting effect similar to parallax scrolling for some users, secondly, I am not sure how engaging this would look - can't think of an alternative for the latter and it is a niggle rather than a major concern. 14: Positive visual would be good, are there potential issues with a check-mark visual? Mild concern related to avoiding checklists |
| Mark Palmer | |
| Estella Oncins | Excellent work |
| Helen Burge | |
| Howard Kramer | I really liked the first 6 segments. Then the video branched out to other areas which I think is fine but it didn't seem to flow as well. I wonder if some type of two sentence comment prior to segment 2 might explain what is going to be covered in this video. Something like "This video will cover tools and other resources for evaluating your pages for accessibility. We will then cover these resources in more depth in subsequent videos." Also, maybe it would help to change segment 13 to "With these resources and guides you can learn how to check your website for accessibility barriers[, receive input from user testing,] and prioritize the issues you need to address first." [Added text in brackets] |
| Shawn Lawton Henry | 3: "It is ideally carried out throughout …" -> "Ideally you evaluate throughout …" Rationale: active voice. remove "carried out" (if leave sentence structure, change "carried out" to "done" – simpler wording) 3: "… throughout the design and development process, to avoid costly repairs during later stages." -> "… throughout design and development, to avoid costly repairs late in the process." or "… throughout the design and development process, to avoid costly repairs later." R: Are there stages than design and development process? 5: "For example, the resource "Easy Checks - A First Review of Web Accessibility" explains…" -> "The resource "Easy Checks - A First Review of Web Accessibility" explains…" R: remove unnecessary words 5: "… explains how you can carry out some checks yourself." -> "… explains how you can do some checks yourself." R: simpler wording 6: "Even if you are new to web accessibility and non-technical…" -> "Even if you are new to web accessibility and not technical…" Also, I wonder about "new to accessibility"? … so maybe: -> "Even if you don't know anything about web accessibility yet and you're not technical…" 6: "… get a rough impression of…" -> "… get a rough idea of…" 6: "… get a rough [idea] of how well you are doing." -> "… get a rough [idea] of the accessibility of a web page." R: We imagine that people use Easy Checks to check *other* pages besides their own. Note: You say the in the Easy Checks video. If you want to leave this one as is for flow, I'm totally fine with that. 7: "W-A-I also provides a list of web accessibility evaluation tools, which you can filter, to find the right tool for you." -> "W-A-I also provides a list of web accessibility evaluation tools, that you can filter to find the right tool for you." R: Technically, grammatically, better to have the sentence without commas at all. But probably want one here to indicate pause. 8: "… which provides guidance on what tools can and cannot do, to help you understand the tools." -> "… which provides guidance on what tools can and cannot do." or "… which helps you understand the different types of tools and what they can and cannot do." 13: "With these resources you can learn how to check…" 13: "With these resources, you can learn how to check…" |
3. Video 2: Preliminary Evaluation
Please carefully review the script for Video 2: Preliminary Evaluation.
Please indicate any comments you have on:
- The spoken audio
- The illustrative visuals
- The overall duration
- Anything missing?
- Anything to remove?
- Any other observations?
Details
| Responder | Video 2: Preliminary Evaluation |
|---|---|
| Vicki Menezes Miller | Good, minor comments below. - At Seq.5: Is there a way to replace "knowledgeable humans" with another term? Maybe "people with some expertise in accessibility" or something else, maybe simply "knowledgeable people". I somehow don't lean towards indicating "humans" (makes me wonder, are there robots around :) ... maybe soon:) - At Seq.9: Instead of "They address"... what about "Specific tools are designed for different audiences, " |
| Brent Bakken | [ED] Seq. 8 - Audio: Add word - "Just remember that even if you carry out all easy checks, it is not an evaluation of all accessibility aspects. More testing is needed for [a] more definitive assessment." |
| Lewis Phillips | looks ok |
| Norah Sinclair | |
| Sylvie Duchateau | 1. Word change suggestion in following sentence: Actual text: "The resource "Easy Checks - A First Review of Web Accessibility" gives you step-by-step guidance on how to check some aspects of accessibility. 2. IN "Some checks are as simple as looking at the web page to determine its page title." Although it is illustrate, I wonder if the audio text should explain where to llok at on the browser window, to find the page title. For example, "you can see the page title on the top of the browser window, just above the menu bar" or any other description that better fits. Proposal: The resource "Easy Checks - A First Review of Web Accessibility" gives you step-by-step guidance on checking some aspects of accessibility. 3. actual text: "For some checks it is easier to download an extension for your browser to help you." Proposal other way round: To help you with some checks, it is easier to download an extension for your browser. 4. Using active voice? Actual sentence: "More testing is needed for more definitive assessment." Proposal: You need more testing to assess a whole page." 5. Add a comma in: "The first step to accessibility is understanding where you are, and with Easy Checks you can get started right away." and, with easy checks, you can get started right away. 6. Same as in previous video, final sentence the other way round? Actual text: "Visit w3.org/WAI/evaluation for more information on easy checks for web accessibility." Proposal: "for more information on easy checks for web accessibility, visit w3.org/WAI/evaluation. |
| Eric Eggert | |
| Laura Keen | |
| Kevin White | 2: Text: 'a rough impression of the accessibility' -> 'a rough sense of the accessibility' - slightly easier wording? 2: Visuals: This might be a bit fastidious but I wonder if using a completely fictitious bug scattering might give the wrong impression of how the tools would work? I know it is not possible to use any particular tool but wonder if it would possible to use a visual that is more similar to the patterns used in the tools? |
| Mark Palmer | |
| Estella Oncins | Excellent work |
| Helen Burge | |
| Howard Kramer | This may have already been covered before and decided against but I wanted to see a demonstration of how you would apply Easy Checks, even if just for one area, such as alt text. This video shows us that the resources exists. I think it needs an example of how it would be used to draw in potential users. |
| Shawn Lawton Henry | 2: "Even if you are new to web accessibility and non-technical, you can do some easy checks to get a rough impression of the accessibility of any web page." [See comments on Overview video script] 3: "For example, a webpage from your own website, …" -> "For example, a web page from your own website, …" 5: "Some checks are as simple as looking at the web page to determine its page title." -> "Some checks are as simple as looking at the title of the web pages." R: since compare with other pages titles on the website or "Some checks are as simple as looking at the web page's title." 6: "For some checks it is easier to download an extension for your browser to help you." -> "For some checks it is easier to download an extension for your browser." 7: "Sometimes carrying out only a few checks …" -> "Sometimes doing only a few checks …" 7: "…can still give you a general idea of how well you are doing." -> "…can still give you a general idea of how well a page addresses accessibility." R: May be doing the checks on a vendor, competitor, or other site/ 8: "More testing is needed for more definitive assessment." -> "More testing is needed for a definitive and comprehensive evaluation." 9: "The first step to accessibility is understanding where you are" This not feeling tight For one thing, that assumes checking own website, whereas we're saying "webpage from your own website, from your competitor, or from vendors you might want to work with." Another point is we usually say get a basic understanding of accessibility first (ideally anyway) – e.g., https://www.w3.org/WAI/planning/interim-repairs/ says "If you are new to accessibility, it is often helpful to first get a basic understanding of accessibility:" True that then it goes into "Identify the Issues". |
4. Video 3: Selecting and Using Tools
Please carefully review the script for Video 3: Selecting and Using Tools.
Please indicate any comments you have on:
- The spoken audio
- The illustrative visuals
- The overall duration
- Anything missing?
- Anything to remove?
- Any other observations?
Details
| Responder | Video 3: Selecting and Using Tools |
|---|---|
| Vicki Menezes Miller | Fine. At Seq3: I don't think there is need to have "to use" at the end of the sentence. At Seq5: :) see my comment above on "knowledgable humans". At Seq8: "Tools can integrate", would suggest "Tools can be integrated" At Seq9: see comment above on "They address" |
| Brent Bakken | [Idea] Seq. 8&9 - Visuals: I have an idea for the visuals in these two sequences. Hard to type up the idea concept, happy to discuss on a quick call or at meeting. |
| Lewis Phillips | looks ok |
| Norah Sinclair | |
| Sylvie Duchateau | 1. Second sequence: Actual text: "to help you determine accessibility of your content." Proposal: that help you, or that can help you, determine if your content is accessible. 2. Like in previous video, other way around for last sentence? ACtual text: "Visit w3.org/WAI/evaluation for more information on tools for evaluating web accessibility." Proposal: For more information on tools for evaluating web accessibility, visit w3.org/WAI/evaluation. |
| Eric Eggert | |
| Laura Keen | |
| Kevin White | 2: Text: 'to help you determine accessibility of your content' -> 'to help you identify accessibility issues' - think this is a little bit more direct and simpler language 3: Is this a significant point? It seems a truism. 5: Text: 'require involvement of knowledgeable humans' -> 'require input from people with specialist knowledge'? The phrase 'knowledgeable humans' seems clunky and weird. 8: Visuals: Something like the Grammerly adverts where it shows an editor with a pop-up suggestion? Obviously without completely copying it :) 9: Visuals: Pop up representative icons as each discipline is mentioned? 10: Text: 'Yet beware that' -> 'Watch out because', 'You need to take care because': Something other than 'Yet beware that' 12: Text: 'tool results': Trying to think of a different way to say this, something like 'Also, avoid relying too much on what the tool tells you over what real users tell you.' |
| Mark Palmer | |
| Estella Oncins | Excellent work |
| Helen Burge | |
| Howard Kramer | Similar to video 2, I thought this was too abstract. I'd like to see some examples of tools. I know this is problematic but I think people need to see some examples of how these tools work. |
| Shawn Lawton Henry | 2: "Web accessibility evaluation tools are software programs or online services, to help you determine… " -> "Web accessibility evaluation tools are software programs or online services that help you determine… " 4: "Tools can save you lots of time and effort in evaluation, and can help you to prevent accessibility barriers from being introduced." -> "Tools can save you lots of time and effort on evaluation. And tools can help avoid creating new accessibility barriers." -> "Tools can save you lots of time and effort on evaluation. And tools can help prevent new accessibility barriers when you update your website." or "Tools can save you lots of time and effort on evaluation. And tools can help avoid new accessibility barriers with website updates." 9: "They address different audiences, such as content authors, code developers, designers, and product owners." -> "Different tools help with different tasks, such as designing, coding, developing content, and project management. [medium] "address different audiences" is not right for the target users/tasks of tools 10: "Yet beware that, at times, tools can provide inaccurate results." -> "Be aware that tools can provide inaccurate results." 11: "Also avoid relying too much on tool results over addressing the real-life experience of your website users." -> "Also, avoid relying too much on tool results over addressing the real-life experience of website users." R: probably need to take out "your" here to avoid the "we don't have users with disabilities" argument :-/ 14: "Equipped with the right tools and knowledge on how to use them, you are in good shape to find and remove accessibility barriers." ??? This makes it sound like you *need* tools to find and remove accessibility barriers. I'm not sure we want to say that. Also this makes it sound like there are "right tools" and wrong tools. (Also "find accessibility barriers" – OK ; "remove accessibility barriers" – not sure.) Possibly something more like: "Tools that work well in your environment and the knowledge to use them, can help you find accessibility barriers more efficiently so you can fix them." |
5. Video 4: Comprehensive Evaluation
Please carefully review the script for Video 4: Comprehensive Evaluation.
Please indicate any comments you have on:
- The spoken audio
- The illustrative visuals
- The overall duration
- Anything missing?
- Anything to remove?
- Any other observations?
Details
| Responder | Video 4: Comprehensive Evaluation |
|---|---|
| Vicki Menezes Miller | |
| Brent Bakken | Good. No comment here. |
| Lewis Phillips | looks ok |
| Norah Sinclair | |
| Sylvie Duchateau | 1. I don't understand what this sentence means: "and when getting started with accessibility, to get a list of accessibility issues that you need to address." Does this mean for people who are new to accessibility, or when you start implementing accessibility? This would be good to clarify. 2. May be something missing here, how to find real users? What to do with them? "One thing to note here: WCAG-EM recommends the involvement of real users with disability during evaluation, to help ensure you are addressing the real-life experience of your website users." 3. Like in the other videos, other way round: Actual text: "Visit w3.org/WAI/evaluation for more information on conformance evaluation of web accessibility." Proposal: For more information on conformance evaluation of web accessibility, visit w3.org/WAI/evaluation |
| Eric Eggert | |
| Laura Keen | |
| Kevin White | 5: Visuals:: Not sure on whether graduation cap universally symbolises expertise or experience. Also, not sure it is the right message? Suggestive that you need degree education in order to be able to do this? Not sure I have an alternative suggestion and happy to accept visualisation if there are no other concerns. 7: Text: Does WCAG-EM provide guidance to help you evaluate conformance or does it provide guidance on how to structure your evaluation? 9: Text: Might be something that is being worked on but does WCAG-EM report tool support 2.1? |
| Mark Palmer | |
| Estella Oncins | Excellent work |
| Helen Burge | |
| Howard Kramer | I liked this one better than the others - more detail. The user gets more of an idea of what this tool does. The effectiveness will be determined by what appears on the screen. Hopefully they can get some sense of the type of data to go into the report and what report will be output. |
| Shawn Lawton Henry | 1: "Conformance evaluation of web accessibility." -> "Web Accessibility Conformance Evaluation" 9: "The accompanying open source WCAG-EM Report Tool helps you follow the methodology, record the outcomes, and download a report of your outcomes, which you can further customize." -> "The open source WCAG-EM Report Tool helps you follow the methodology, record the outcomes, and download a report of your evaluation." Rationale: simplifying wording. "which you can further customize" not an important enough point in this context to complicate the sentence. 10: "…to help ensure you are addressing the real-life experience of your website users." -> "…to help ensure you are addressing the real-life experience of your website users." R: probably need to take out "your" here to avoid the "we don't have users with disabilities" argument :-/ |
6. Video 5: Involving Users
Please carefully review the script for Video 5: Involving Users.
Please indicate any comments you have on:
- The spoken audio
- The illustrative visuals
- The overall duration
- Anything missing?
- Anything to remove?
- Any other observations?
Details
| Responder | Video 5: Involving Users |
|---|---|
| Vicki Menezes Miller | Very nice. At Seq. 6: Instead of "The development", how about just "Development.." or "The development process..." At Seq.10: Instead of "Following these resources", why not simply "These resources" |
| Brent Bakken | Good. No comment here. |
| Lewis Phillips | looks ok |
| Norah Sinclair | |
| Sylvie Duchateau | 1. Simplify sentence, editor's discretion? Actual text: "Yet unfortunately projects often approach accessibility just as a checklist to meet accessibility standards. This risks missing the real purpose of accessibility - the user experience." Proposal: Unfortunately, projects often just treat accessibility as a checklist to meet accessibility standards. As a consequence, there is a risk that the user experience, the real purpose of accessibility be left behind. Or something similar 2. Following sentence is not clear: "Following these resources helps you ensure accessibility for your end-users rather than focus on technical requirements only." The part "rather than focus on technical requirements only." is not clear. HOw can the resource help this part? 3. Visit w3.org/WAI/evaluation for more information on involving users in web accessibility. Same comment as previous. Proposal: for more information on involving users in web accessibility, visit w3.org/WAI/evaluation. |
| Eric Eggert | |
| Laura Keen | |
| Kevin White | 2: Visuals: Is this not the point to have actual people instead of icons? I think this might be a general comment on this particular video and I appreciate that it might already have been discussed. If so, I am more than happy with the previous decisions. |
| Mark Palmer | Footage of actual research with users would be more impactful than info-graphics. |
| Estella Oncins | Excellent work |
| Helen Burge | |
| Howard Kramer | I think this particular video lacks something the "perspectives" videos had: visuals of actual people facing obstacles with inaccessible design. I don't think the use of "Pawns" captures this - it might even be insulting if you're talking about chess pawns. I'd like to see a real person sitting at a screen and giving feedback. Perhaps this is to ambitious. |
| Shawn Lawton Henry | 2. "Accessibility is about people; many of your customers, your clients, and your viewers have disabilities." [medium+] * "viewers" is not the right word. Possibly could change it out for "readers" or possibly "target audience"? Also seems like lot left out of this, e.g., students, constituents, employees, and more. Not totally comfortable with an "and others" or "etc" or something… * "Accessibility is about people" makes sense to those of us in the know. But I'm not sure it is sufficiently clear for people with different backgrounds, ideas, etc. I think we might need to say more (e.g., more along the lines of "Accessibility is about making products and services usable by people with disabilities." Or in this context: "Accessibility is about making your websites and applications usable by people with disabilities.") 3: "Yet unfortunately projects often approach accessibility just as a checklist to meet accessibility standards." * Note sure about "unfortunately" here? Generally, we wouldn't want to use such an adverb – but maybe it's needed here to make the statement clearly negative? 5: "the project team is more motivated, energized, and excited, now that accessibility has become more tangible and they better understand the user experiences;" * I have worked with a very few teams who got excited about accessibility… yet, I'm not sure if that's a good word here. . Maybe: ->"the project team is more motivated and energized when they understand how their work impacts real people's lives" (or s/lives/user experiences) 6: "the development is more efficient with innovative solutions that make your products work better…" -> "the development is more efficient, and create innovative solutions that make your products work better…" Rationale: Two important yet separate points. (Actually, I think a lot of the innovative solutions are more on around design – but I think OK not to take extra words to specify.) 6: "…make your products work better for more people, with or without disability;" -> "…make your products work better for more people, with and without disabilities;" 8: "The resource… provides guidance during the design and development process." -> "The resource… provides guidance starting in project planning and throughout design and development. Rationale: Important that it starts at planning, e.g., to budget time and money for it. https://www.w3.org/WAI/planning/involving-users/#range 9: "The companion resource "Involving Users in Evaluating Web Accessibility" provides guidance during the quality assurance phase of a project." [high] Rationale: QA phase is way too late for eval with real people. E.g., ideally it's done with early rough prototypes or even non-working mock-ups. Maybe: -> "The companion resource "Involving Users in Evaluating Web Accessibility" provides more specific guidance." 10: "Following these resources helps you ensure accessibility for your end-users rather than focus on technical requirements only." -> "Following these resources helps you improve accessibility for your end-users rather than focusing on technical requirements only." 11: "Web accessibility: essential for some, useful for all" * This is the one video where I think this phrase fits OK. :-) |
7. Other Comments
Please provide any further thoughts or comments you may have. For example:
Details
| Responder | Comments |
|---|---|
| Vicki Menezes Miller | |
| Brent Bakken | Very good progress on the scripts. |
| Lewis Phillips | The scripts and suggested visuals look good, but I'm sure I can really visualize what it how it will look/sound when implemented |
| Norah Sinclair | |
| Sylvie Duchateau | No other comments. All previous comments are at editor's discretion. |
| Eric Eggert | Unfortunately I could not complete this survey in time. I would have loved to, but no time. |
| Laura Keen | |
| Kevin White | |
| Mark Palmer | |
| Estella Oncins | Designs will be crucial to translate all this content into visuals. |
| Helen Burge | |
| Howard Kramer | These videos don't seem as effective as the "perspectives" videos. Those videos conveyed accessibility issues in almost a dramatic and human way. These are more technical, so I think they should show more examples of their use in order to make them effective. |
| Shawn Lawton Henry | Applies to all: * [med-high] end the URI -- e.g., * draft: Visit w3.org/WAI/evaluation for more information on easy checks for web accessibility. * suggest: For more information on easy checks for web accessibility, visit w3.org/WAI/evaluation * rationale: the URI is the thing you want viewers to see clearly and remember. (also kinda https://www.w3.org/WAI/EO/wiki/Style#Document_links_in_sentences ) * [low] I think good to go ahead and get the punctuation right so we can use these for the transcripts. (For example, no semi-colons at the end of lists https://www.w3.org/WAI/EO/wiki/Style#Lists ) I made a few comments on punctuation, but not all. * [ftr] Just going on record that I think the phrase "Web accessibility: essential for some, useful for all." does not fit in these videos and breaks the flow. (except for the involving users one) Yet I won't "object" over other EOWG participant's preference for it. |
More details on responses
- Vicki Menezes Miller: last responded on 10, September 2019 at 14:37 (UTC)
- Brent Bakken: last responded on 10, September 2019 at 22:21 (UTC)
- Lewis Phillips: last responded on 11, September 2019 at 16:10 (UTC)
- Norah Sinclair: last responded on 11, September 2019 at 20:11 (UTC)
- Sylvie Duchateau: last responded on 12, September 2019 at 09:28 (UTC)
- Eric Eggert: last responded on 12, September 2019 at 13:21 (UTC)
- Laura Keen: last responded on 12, September 2019 at 13:44 (UTC)
- Kevin White: last responded on 12, September 2019 at 14:40 (UTC)
- Mark Palmer: last responded on 12, September 2019 at 15:55 (UTC)
- Estella Oncins: last responded on 12, September 2019 at 21:23 (UTC)
- Helen Burge: last responded on 12, September 2019 at 21:30 (UTC)
- Howard Kramer: last responded on 12, September 2019 at 22:32 (UTC)
- Shawn Lawton Henry: last responded on 13, September 2019 at 01:24 (UTC)
Non-responders
The following persons have not answered the questionnaire:
- Eric Velleman
- Andrew Arch
- Shadi Abou-Zahra
- Kazuhito Kidachi
- Sharron Rush
- Jedi Lin
- David Sloan
- Mary Jo Mueller
- Reinaldo Ferraz
- Bill Kasdorf
- Cristina Mussinelli
- Kevin White
- Kevin Rydberg
- Adina Halter
- Denis Boudreau
- Sarah Pulis
- Bill Tyler
- Gregorio Pellegrino
- Ruoxi Ran
- Jennifer Chadwick
- Sean Kelly
- Muhammad Saleem
- Sarah Lewthwaite
- Daniel Montalvo
- Jade Matos Carew
- Sonsoles López Pernas
- Greta Krafsig
- Jason McKee
- Jayne Schurick
- Billie Johnston
- Michele Williams
- Shikha Nikhil Dwivedi
- Brian Elton
- Julianna Rowsell
- Tabitha Mahoney
- Fred Edora
- Rabab Gomaa
- Marcelo Paiva
- Eloisa Guerrero
- Leonard Beasley
- Frankie Wolf
- Supriya Makude
- Aleksandar Cindrikj
- 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