w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire EOWG Weekly Survey - 29 June 2015
The results of this questionnaire are available to anybody. In addition, answers are sent to the following email addresses: shawn@w3.org,shadi@w3.org,kevin@w3.org
This questionnaire was open from 2015-06-30 to 2015-07-17.
17 answers have been received.
Jump to results for question:
- Showcase Task Force Work Statement
- Tips on Designing for Web Accessibility - Intro
- Tips - Examples
- Tips - EOWG questions in GitHub
- Tips on Designing for Web Accessibility - Right tips???
- Tips on Designing for Web Accessibility - Thorough Review
1. Showcase Task Force Work Statement
As we discussed in the 26 June EOWG teleconference, we would like to set up a Task Force to develop the Showcase Examples with Videos. Please read (or at least skim) the [Draft] Showcase Examples with Videos Task Force (Showcase TF) Work Statement and complete below:
Summary
| Choice | All responders |
|---|---|
| Results | |
| I approve the Work Statement as is. | 14 |
| I approve the Work Statement; however, I suggest the changes in the comments section below (for facilitator's discretion). | 3 |
| I approve the Work Statement only with the changes in the comment section below. | |
| I do not support the Work Statement, because of the comments in the comments section below. | |
| I abstain (not vote) |
Details
| Responder | Showcase Task Force Work Statement | Comments |
|---|---|---|
| Kevin White | I approve the Work Statement; however, I suggest the changes in the comments section below (for facilitator's discretion). | I wonder whether there is a need to indicate what the review points are. That is, should there be a section that indicates interim deliverables that will be reviewed? Minor edit: might 'performers' be better than 'protagonist', as protagonist suggests the leading character but there may be other roles? |
| Melody Ma | I approve the Work Statement as is. | |
| Shadi Abou-Zahra | I approve the Work Statement as is. | |
| Brent Bakken | I approve the Work Statement; however, I suggest the changes in the comments section below (for facilitator's discretion). | In the Approach section, it sounds like the Task Force members are the ones that will be taking raw footage, processing, editing, rendering final video. Will we have that skill set on the Task Force Team? If not, should this be reworded that the Task Force will be pulling in resources to do that part of the work? In the Communication Section it states, "Show-Ex communications are publicly visible. Communication mechanisms for Show-Ex include:". Need to change both instances of "Show-Ex" to "Showcase TF." |
| Vicki Menezes Miller | I approve the Work Statement as is. | |
| Eric Eggert | I approve the Work Statement as is. | Concise, focused. I like it. |
| Sharron Rush | I approve the Work Statement as is. | |
| Paul Schantz | I approve the Work Statement as is. | |
| Sylvie Duchateau | I approve the Work Statement as is. | |
| Lydia Harkey | I approve the Work Statement; however, I suggest the changes in the comments section below (for facilitator's discretion). | Approach section: Casting for performers/actors/characters, etc may be a better description if there will be multiple characters in the video versus using the word 'protagonist', as protagonist suggest one person will be the lead or central figure. |
| Wayne Dick | I approve the Work Statement as is. | |
| Andrew Arch | I approve the Work Statement as is. | Only comment is "should the materials be released progressively as completed?" |
| Shawn Lawton Henry | I approve the Work Statement as is. | |
| Howard Kramer | I approve the Work Statement as is. | |
| Emmanuelle Gutiérrez y Restrepo | I approve the Work Statement as is. | |
| Reinaldo Ferraz | I approve the Work Statement as is. | |
| Jonathan Metz | I approve the Work Statement as is. |
2. Tips - Examples
UPDATE 3 July: You can skip this question now. We already made initial decisions, which Kevin will implement and they we'll look at it again.
Please review the perspectives on making the images less overwhelming in the 26 June EOWG Minutes and in GitHub issue 30. Please add your thoughts to the GitHub issue (or, if you're not comfortable with GitHub, you can put them in the comments here).
Summary
| Choice | All responders |
|---|---|
| Results | |
| I reviewed the perspectives and put my comments in GitHub. | 7 |
| I reviewed the perspectives and put my comments below. | 1 |
| I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | 1 |
| I'm not going to be able to get to this, and I will pass on commenting on it — now and in the future. | 2 |
Details
| Responder | Tips - Examples | Comments |
|---|---|---|
| Kevin White | ||
| Melody Ma | I reviewed the perspectives and put my comments below. | They look fine. Supports the content well. If someone is serious about accessibility, they'll review the text. |
| Shadi Abou-Zahra | I reviewed the perspectives and put my comments in GitHub. | |
| Brent Bakken | I reviewed the perspectives and put my comments in GitHub. | |
| Vicki Menezes Miller | I reviewed the perspectives and put my comments in GitHub. | |
| Eric Eggert | I reviewed the perspectives and put my comments in GitHub. | |
| Sharron Rush | I reviewed the perspectives and put my comments in GitHub. | Personally I have no problems with the examples being overwhelming. However if it is still an issue for several people (which seems to be the case) it should be further addressed. |
| Paul Schantz | ||
| Sylvie Duchateau | I'm not going to be able to get to this, and I will pass on commenting on it — now and in the future. | |
| Lydia Harkey | ||
| Wayne Dick | I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | |
| Andrew Arch | ||
| Shawn Lawton Henry | I reviewed the perspectives and put my comments in GitHub. | |
| Howard Kramer | I reviewed the perspectives and put my comments in GitHub. | |
| Emmanuelle Gutiérrez y Restrepo | ||
| Reinaldo Ferraz | ||
| Jonathan Metz | I'm not going to be able to get to this, and I will pass on commenting on it — now and in the future. | Per the Update 3 July. |
3. Tips - EOWG questions in GitHub
UPDATE 3 July: You can skip this question now. We already made initial decisions, which Kevin will implement and they we'll look at it again.
Please look at the other questions in GitHub and add your thoughts. Please add your thoughts in GitHub if you are comfortable; otherwise, you can put them here.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I read the questions and put my comments in GitHub. | 9 |
| I read the questions and put my comments below. | |
| I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | 1 |
| I'm not going to be able to get to this at all, and I will pass on commenting on it — now and in the future. | 2 |
Details
| Responder | Tips - EOWG questions in GitHub | Comments |
|---|---|---|
| Kevin White | ||
| Melody Ma | I read the questions and put my comments in GitHub. | |
| Shadi Abou-Zahra | I read the questions and put my comments in GitHub. | |
| Brent Bakken | I read the questions and put my comments in GitHub. | |
| Vicki Menezes Miller | I read the questions and put my comments in GitHub. | |
| Eric Eggert | I read the questions and put my comments in GitHub. | |
| Sharron Rush | I read the questions and put my comments in GitHub. | |
| Paul Schantz | ||
| Sylvie Duchateau | I'm not going to be able to get to this at all, and I will pass on commenting on it — now and in the future. | |
| Lydia Harkey | ||
| Wayne Dick | I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | |
| Andrew Arch | ||
| Shawn Lawton Henry | I read the questions and put my comments in GitHub. | |
| Howard Kramer | I read the questions and put my comments in GitHub. | |
| Emmanuelle Gutiérrez y Restrepo | I read the questions and put my comments in GitHub. | |
| Reinaldo Ferraz | ||
| Jonathan Metz | I'm not going to be able to get to this at all, and I will pass on commenting on it — now and in the future. | Per the Update 3 July. |
4. Tips on Designing for Web Accessibility - Right tips???
Please think carefully about the Tips themselves.
- Are these the most essential tips for designers who are new to web accessibility?
- Are there other Tips we should include?
- Should any of these Tips not be included?
If so, please add a GitHub issue. (If you're not comfortable with GitHub, you can put comments in this survey.)
Summary
| Choice | All responders |
|---|---|
| Results | |
| I thought about it carefully and added issues(s) in GitHub. | 4 |
| I thought about it carefully and added issues(s) in comments below. | 5 |
| I thought about it carefully and think these are the right Tips. | 4 |
| I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | 1 |
| I'm not going to be able to get to this at all, and I will pass on commenting on it — now and in the future. | 1 |
Details
| Responder | Tips on Designing for Web Accessibility - Right tips??? | Comments |
|---|---|---|
| Kevin White | ||
| Melody Ma | I thought about it carefully and added issues(s) in comments below. | Tips regarding icon usage and text size could be useful. |
| Shadi Abou-Zahra | I thought about it carefully and added issues(s) in GitHub. | |
| Brent Bakken | I thought about it carefully and added issues(s) in comments below. | What about a tip for SC 2.4.3 Focus Order. Some pages can get pretty complex and if sequential navigation is not provided correctly confusion can ensue fairly quickly. It is important that focus order helps provide understanding for both meaning and operation. |
| Vicki Menezes Miller | I thought about it carefully and added issues(s) in comments below. | - I think we need a tip on alternative text for images - possibly, the tip on visible audio controls might be too much for this audience |
| Eric Eggert | I thought about it carefully and added issues(s) in GitHub. | (I think I have added this in the comments on other topics above, so no new issues :-D) |
| Sharron Rush | I thought about it carefully and added issues(s) in GitHub. | |
| Paul Schantz | ||
| Sylvie Duchateau | I'm not going to be able to get to this at all, and I will pass on commenting on it — now and in the future. | |
| Lydia Harkey | I thought about it carefully and added issues(s) in comments below. | suggest adding 'Remember Line Length' May not be relevant but some designers tend to be too wordy or not too wordy. |
| Wayne Dick | I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | |
| Andrew Arch | I thought about it carefully and think these are the right Tips. | |
| Shawn Lawton Henry | I thought about it carefully and added issues(s) in GitHub. | ... oops, I didn't think about the order until now. I'll raise that as a separate issue. |
| Howard Kramer | I thought about it carefully and think these are the right Tips. | These look fine to me. Nothing pops out as not belonging or missing. |
| Emmanuelle Gutiérrez y Restrepo | I thought about it carefully and think these are the right Tips. | |
| Reinaldo Ferraz | I thought about it carefully and added issues(s) in comments below. | Nothing more to contribute. This tips are great. |
| Jonathan Metz | I thought about it carefully and think these are the right Tips. |
5. Tips on Designing for Web Accessibility - Thorough Review
Please read thoroughly Tips on Designing for Web Accessibility and put comments in GitHub — either add a GitHub issue or fork and make edit suggestions. (If you're not comfortable with GitHub, you can put comments in this survey.)
Please indicate if you feel strongly or mildly about each comment.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I reviewed it thoroughly and put my comments in GitHub. | 9 |
| I reviewed it thoroughly and put my comments below. | 4 |
| I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | 1 |
| I'm not going to be able to get to this at all, and I will pass on commenting on it — now and in the future. | 1 |
Details
| Responder | Tips on Designing for Web Accessibility - Thorough Review | Comments |
|---|---|---|
| Kevin White | ||
| Melody Ma | I reviewed it thoroughly and put my comments below. | No additional comments. |
| Shadi Abou-Zahra | I reviewed it thoroughly and put my comments in GitHub. | |
| Brent Bakken | I reviewed it thoroughly and put my comments in GitHub. | The Tips on Designing is coming along nicely. Great Work!!! |
| Vicki Menezes Miller | I reviewed it thoroughly and put my comments in GitHub. | Just a note: This is "WOW" - well done! |
| Eric Eggert | I reviewed it thoroughly and put my comments in GitHub. | https://github.com/w3c/wai-quick-start/pull/55 https://github.com/w3c/wai-quick-start/pull/56 https://github.com/w3c/wai-quick-start/pull/57 https://github.com/w3c/wai-quick-start/issues/58 https://github.com/w3c/wai-quick-start/pull/59 |
| Sharron Rush | I reviewed it thoroughly and put my comments in GitHub. | |
| Paul Schantz | ||
| Sylvie Duchateau | I'm not going to be able to get to this at all, and I will pass on commenting on it — now and in the future. | |
| Lydia Harkey | I reviewed it thoroughly and put my comments below. | Great work! |
| Wayne Dick | I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | |
| Andrew Arch | I reviewed it thoroughly and put my comments below. | Excellent work - looking really great now :) 1. Grammar - when multiple stories available the bullet should really read "User Stories" 2. Spelling - Page needs a through check for typos (e.g. 'tutotial' is used with Form Elements 3. Colour Alone - let's be sure the number on the triangles have sufficient contrast 4. Navigation - should we mention a 'menu' as a form of navigation (it may not be obvious to everyone) 5. Headings - while the Learn More links go to places that talk about heading markup and structure, I wonder if this should be explicit in the tip text too 6. Alt Text - for snow, I'd change the to "snow vista" with a comment to the tip reader that it is included to 'Used to evoke a sense of desire in snowboarders' (just my considered opinion) Apologies for not using Github - temporary lack of access as our work system is switched to new Dept. |
| Shawn Lawton Henry | I reviewed it thoroughly and put my comments in GitHub. | I did *not* yet look at "Create designs for different viewport sizes" since that might be changing. |
| Howard Kramer | I reviewed it thoroughly and put my comments in GitHub. | |
| Emmanuelle Gutiérrez y Restrepo | I reviewed it thoroughly and put my comments in GitHub. | |
| Reinaldo Ferraz | I reviewed it thoroughly and put my comments below. | I'm not sure if alt text should be part of designing, as discussed last teleconf. Probably not. It is already in writing sesion. |
| Jonathan Metz | I reviewed it thoroughly and put my comments in GitHub. | My comments are included in the Week of Friday 17 July response. |
More details on responses
- Kevin White: last responded on 1, July 2015 at 14:39 (UTC)
- Melody Ma: last responded on 2, July 2015 at 02:20 (UTC)
- Shadi Abou-Zahra: last responded on 2, July 2015 at 06:48 (UTC)
- Brent Bakken: last responded on 2, July 2015 at 18:56 (UTC)
- Vicki Menezes Miller: last responded on 2, July 2015 at 20:13 (UTC)
- Eric Eggert: last responded on 3, July 2015 at 10:56 (UTC)
- Sharron Rush: last responded on 6, July 2015 at 17:43 (UTC)
- Paul Schantz: last responded on 7, July 2015 at 00:26 (UTC)
- Sylvie Duchateau: last responded on 7, July 2015 at 13:34 (UTC)
- Lydia Harkey: last responded on 8, July 2015 at 01:32 (UTC)
- Wayne Dick: last responded on 9, July 2015 at 20:14 (UTC)
- Andrew Arch: last responded on 9, July 2015 at 22:48 (UTC)
- Shawn Lawton Henry: last responded on 10, July 2015 at 01:36 (UTC)
- Howard Kramer: last responded on 10, July 2015 at 04:57 (UTC)
- Emmanuelle Gutiérrez y Restrepo: last responded on 10, July 2015 at 09:42 (UTC)
- Reinaldo Ferraz: last responded on 11, July 2015 at 12:12 (UTC)
- Jonathan Metz: last responded on 17, July 2015 at 04:11 (UTC)
Non-responders
The following persons have not answered the questionnaire:
- Eric Velleman
- Kazuhito Kidachi
- Jedi Lin
- David Sloan
- Mary Jo Mueller
- Bill Kasdorf
- Cristina Mussinelli
- Kevin Rydberg
- Adina Halter
- Denis Boudreau
- Laura Keen
- Sarah Pulis
- Bill Tyler
- Gregorio Pellegrino
- Ruoxi Ran
- Jennifer Chadwick
- Sean Kelly
- Muhammad Saleem
- Sarah Lewthwaite
- Daniel Montalvo
- Mark Palmer
- 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