w3c/wbs-design
or
by mail to sysreq
.
The results of this questionnaire are available to anybody. In addition, answers are sent to the following email addresses: shawn@w3.org,shadi+EOsurvey@w3.org
This questionnaire was open from 2016-02-27 to 2016-03-02.
9 answers have been received.
Jump to results for question:
summary | by responder | by choice
Please read the 26 Feb EOWG teleconference meeting minutes or summary. Indicate your approval or concerns with the resolution(s) passed at that meeting.
Choice | All responders |
---|---|
Results | |
I was in the teleconference and I'm OK with it! | 7 |
I have reviewed the minutes and agree to the Resolution as passed. | 2 |
I have reviewed the minutes but have concerns with the Resolution and I explain them below. | |
I have not read the minutes yet, and have put the date for my review into the comments box. |
Skip to view by choice.
Responder | Resolution of 26 February 2016 | Comments |
---|---|---|
Eric Eggert |
|
|
George Heake |
|
|
Vivienne Conway |
|
|
Brent Bakken |
|
|
James Green |
|
|
Andrew Arch |
|
|
Susan Hewitt |
|
|
Sharron Rush |
|
|
Howard Kramer |
|
Choice | Responders |
---|---|
I was in the teleconference and I'm OK with it! |
|
I have reviewed the minutes and agree to the Resolution as passed. |
|
I have reviewed the minutes but have concerns with the Resolution and I explain them below. | |
I have not read the minutes yet, and have put the date for my review into the comments box. |
The Showcase Task Force has outlined some key considerations to think about while finalizing the official name for this resources. Resource Wiki
Please consider the following:
The current recommended name for the resource is "Impact and Benefits of Web Accessibility."
View the visual mock-up of the resource overview page with the recommended name in place.
Please use the comment field below to express your initial reactions to this recommended name for the resource. The next question will guide you through suggesting other resource name ideas.
Responder | Resource Title for [Showcase Examples with Videos]: Task Force Recommendation |
---|---|
Eric Eggert | The name is very descriptive but not catchy at all. I think “Web Accessibility: Impact and Benefits” could work better, but it is still very unemotional. With the videos being not dead serious I am hoping that we find a more casual title. (Also, I guess the overview page will be <del>beefed</del><ins>tofued</ins> up a bit, for example with a grid of video previews.) |
George Heake | Simple and clean design |
Vivienne Conway | While I'm not thrilled with the recommended name, I can't really say why. I guess it sounds a bit dry and not catchy enough? |
Brent Bakken | No Comment - Task Force Member |
James Green | It is fine, but these videos kind of deserve a more interesting/engaging title in my opinion. |
Andrew Arch | Works for me (without seeing the final productions) |
Susan Hewitt | It's not very attention grabbing. It also seems a bit generic as in could be applied to many other resources on the site. |
Sharron Rush | Too dull. The videos are meant to be engaging and entertaining - the name should be too. |
Howard Kramer | Would go for simply "Benefits of Web Accessibility" |
Based on the input you provided for the privious question, can you provide other suggestions for the official name of the Showcase Examples with Videos resource?
To help get your started, here are other resources names brainstormed by the Task Force:
If you have other ideas and suggestions for a title, please list them in the additional space(s) provided below.
If you prefer any of the names above from the Task Force, please indicate your preference in the Comments field at the bottom.
Responder | Name Suggestion 1 | Name Suggestion 2 | Name Suggestion 3 | Comments |
---|---|---|---|---|
Eric Eggert | Web Accessibility: Everyone benefits | Web Accessibility Pays Off! | ||
George Heake | Web Accessibility: What's the Impact is my pick. I did like Features and Benefits of Web Accessibility. Using the word Impact just seems stronger and notifies the reader (perhaps:)) hey I should be we aware of any impact versus whether I am interested in a feature or benefit. | |||
Vivienne Conway | Web Accessibility: Everyone Wins | Designing web sites with accessibility Web Accessibility: Why does it Matter? or "Who does it Affect" | ||
Brent Bakken | ||||
James Green | First Hand Web Accessibility: Video Vignettes | |||
Andrew Arch | Web Accessibility: What's the Impact | Web Accessibility: Who benefits | I like 'benefits' in the title | |
Susan Hewitt | Take a Look at Web Accessibility | Ones I like from TF list: -Web Accessibility: A View to What You Can Do (Suggest changing to ..."A View to What It Can Do") -Web Accessibility: See for Yourself | ||
Sharron Rush | My Accessible World Video Series | Wake Up! - the web accessibility series | Choose Web Accessibility - the why and how | I like "See for Yourself," also "Making the Web More Accessible - the video series |
Howard Kramer | Benefits of Making the Web Accessible |
Please take the time to go through each of the remaining open issues or "questions" for the Showcase Examples with Video resource. There are questions around topics such as a catch phrase, title and end screens, relation to WCAG, etc.
View the current Showcase Open Issues.
Please add your thoughts to the GitHub issue. If you are not comfortable with GitHub you may add your comments in the space provided below.
Choice | All responders |
---|---|
Results | |
I reviewed the current Showcase Examples with Videos open issues in GitHub and have no comments. | 1 |
I reviewed the current Showcase Examples with Videos open issues and have added comments in GitHub or below. | 7 |
I did not get to these issues and will pass on this question and go with the decisions of the group. | 1 |
Responder | Current Open Issue Review: [Showcase Examples with Videos] | Comments |
---|---|---|
Eric Eggert | I reviewed the current Showcase Examples with Videos open issues and have added comments in GitHub or below. | |
George Heake | I reviewed the current Showcase Examples with Videos open issues and have added comments in GitHub or below. | |
Vivienne Conway | I reviewed the current Showcase Examples with Videos open issues in GitHub and have no comments. | |
Brent Bakken | I reviewed the current Showcase Examples with Videos open issues and have added comments in GitHub or below. | Commented in GitHub |
James Green | I reviewed the current Showcase Examples with Videos open issues and have added comments in GitHub or below. | |
Andrew Arch | I reviewed the current Showcase Examples with Videos open issues and have added comments in GitHub or below. | |
Susan Hewitt | I reviewed the current Showcase Examples with Videos open issues and have added comments in GitHub or below. | Only one comment on catch phrase thread. |
Sharron Rush | I reviewed the current Showcase Examples with Videos open issues and have added comments in GitHub or below. | The repetitive catch phrase at the end of each video is necessary to tie them together and bring back the topic of web accessibility. Should be something like "[Insert short phrase specific to each] is part of web accessibility, it is necessary for people with disabilities and improves the web for everyone." |
Howard Kramer | I did not get to these issues and will pass on this question and go with the decisions of the group. |
I completed the Showcase Video, final script approval: Scripts 6 - 10 survey.
Choice | All responders |
---|---|
Results | |
yes | 8 |
no |
(1 response didn't contain an answer to this question)
Responder | Scripts 6-10 Approval: Showcase Examples with Videos |
---|---|
Eric Eggert | |
George Heake | yes |
Vivienne Conway | yes |
Brent Bakken | yes |
James Green | yes |
Andrew Arch | yes |
Susan Hewitt | yes |
Sharron Rush | yes |
Howard Kramer | yes |
The following persons have not answered the questionnaire:
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
w3c/wbs-design
or
by mail to sysreq
.