W3C

Site Navigation

Nearby

Results of Questionnaire EOWG Web Accessibility Perspectives Review - April 2016

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-04-19 to 2016-04-27.

11 answers have been received.

Jump to results for question:

  1. Overall Comments
  2. Keyboard Compatibility - Video
  3. Keyboard Compatibility - Text
  4. Colors With Good Contrast - Video
  5. Colors With Good Contrast - Text
  6. Clear Layout and Design - Video
  7. Clear Layout and Design - Text
  8. Large Select Areas - Video
  9. Large Select Areas - Text
  10. Video Captions - Video
  11. Video Captions - Text
  12. Customizable Text - Video
  13. Customizable Text - Text
  14. Text to Speech - Video
  15. Text to Speech - Text
  16. Voice Recognition - Video
  17. Voice Recognition - Text
  18. Understandable Content - Video
  19. Understandable Content - Text
  20. Notifications and Feedback - Video
  21. Notifications and Feedback - Text
  22. Learn More about Web Accessibility

1. Overall Comments

Please provide overall comments on the videos and resource page. Later questions will ask you for feedback on each individually. Consider the following:

  • How is the overall structure and organization of the resource page (within the boundaries of the WAI website design)?
  • The Task Force has given thought to and ordered the sections on the page. Do you have any preferred order for the sections?
  • Are there issues that are common across several videos or sections?

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Details

Responder Overall Comments
Laura Keen
Denis Boudreau Overall comment is these videos are GREAT. I really like the short format, and the fact that we were able to draw from every day life metaphors to illustrate some of the points we're trying to make. I'm not commenting on the lack of captions just yet, but I'm assuming we're already on top of that.
Sharron Rush Bravo - videos are really well conceived and executed. The test is verbose however and not especially engaging.

I expected each section to include links to materials specific to the issue, not to the generic link about web accessibility in general.
Eric Eggert I think they turned out really good. The page however broke my Firefox browser (Developer Edition). I guess there is something weird going on with all the embedded videos.

Also, do we want to have all videos on one page? If so, what’s the loading policy?

Where will the videos be hosted? On W3.org? I think we should use Youtube and encourage sharing and embedding as it is about outreach.

I am not 100% fond on the closing screens. The current page has little tips and information on it, it is more a summary of the video and general links on the bottom. What about:

Find out more:
w3.org/WAI/perspectives

I don’t know why the text on the closing screen is starting at 1/3rd in (well, I know, golden ratio and stuff) – I think we could just display the web address larger.

I am also not too fond of the saying “forward slash” instead of just “slash”. I think it’s unnecessarily complicated.

I think the music fits really well (but could be a nudge less loud in some videos) and I also like the narrators, they sound relatively diverse. I think having some UK accented voices really shows how broad the W3C is (hint: world wide ;-) and we can add more videos with other even more diverse accents later.

I’d like to have the W3C and WAI logos closer together (like on our website), and centered.

The copyright notice should be centered and way on the bottom. It is too prominent.

<del>Poster images need to be the title screens of the video or another deliberate still. Most were weird when I opened the page.</del> – What I hear from shadi is that appropriate stills are provided.

[Are there plans/possibilities to make some of the raw material available? I can see a benefit in doing that. Also will those videos be under a CC license? I hope that we can publish them as CC-BY.]
Susan Hewitt What's the reasoning for the current order of the videos? They're listed neither
alphabetically nor by WCAG SC.

The resource link in each paragraph needs to be to more specific, relevant resource or removed altogether. Details
in "Overall" on Git Hub.
Brent Bakken For each text section, I would like to see links added to support pages. Would we want to link directly to specific parts of resources, list out specific Success Criteria or specific techniques? Not sure how in depth this resource should go.

I agree with Eric that we don't need the VO voice at the end to say "forward slash", I thing "slash" is fine.

"esential" spelled wrong throughout. Other spelling as well.
James Green I think they're great! in the text, the word essential is spelled incorrectly as esential in many places. I also think most people won't read the text but It will help with SEO.
Howard Kramer I thought the overall structure was fine but the paragraphs under each video are too wide.
Andrew Arch looking good - I want to share now :)

Logos are obvious in some videos. What's the story WRT product placement/endorsement?
Shawn Lawton Henry Wow, wow, wow! These are great. Totally professional. Very impressive!
(much better & simpler than the previous cut)

I did informal usability testing with a captive audience of 1. :) It was helpful to get reactions from someone who has not been involved in their development.

* [Overall] Slower, clearer, longer https://github.com/w3c/wai-showcase-examples/issues/141
* [Overall] title & web accessibility context [medium] https://github.com/w3c/wai-showcase-examples/issues/159
* [Overall] order https://github.com/w3c/wai-showcase-examples/issues/160

Agree with:
+1 W3C and WAI logos closer together (like on our website) [HIGH]
+1 "forward slash" -> "slash" [medium-HIGH]
+1 "Visit w3.org/WAI/perspectives for tips and information" -> "Find out more: w3.org/WAI/perspectives" [low-MEDIUM]

Accents:
I'm fine with the accents. I think better to have UK accents than American accents. Would be nice if they were a bit milder, but I do not think it is a priority at all.

---
(I only had time to comment on the videos themselves – which took me a long time. And I was off last week. I need more time to comment on web page. It would be much easier and faster for me to do by phone. Maybe best if I join the next TF telecon?)
Judy Brewer Overall, great to see the progress on these, and the quality of the work!

2. Keyboard Compatibility - Video

summary | by responder | by choice

Please review the video for Keyboard Compatibility (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 8
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 1
I do not accept this video unless the comments in GitHub or the Comments section below are addressed. 3
I abstain.

Skip to view by choice.

View by responder

Details

Responder Keyboard Compatibility - VideoComments
Laura Keen
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
Denis Boudreau
  • I accept this video as it is.
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Thumbs up!
Sharron Rush
  • I accept this video as it is.
 I like this video quite a bit, including the voice, accent and music. However the supporting text needs work and I have put suggestions for those in GitHub
Eric Eggert
  • I accept this video as it is.
Susan Hewitt
  • I accept this video as it is.
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
Brent Bakken
  • I accept this video as it is.
 Music is good.
James Green
  • I accept this video as it is.
Howard Kramer
  • I accept this video as it is.
 Excellent video.
Andrew Arch
  • I accept this video as it is.
Shawn Lawton Henry * Narration and visuals are out of synch. https://github.com/w3c/wai-showcase-examples/issues/142
* Longer scene w/o narration https://github.com/w3c/wai-showcase-examples/issues/143
Judy Brewer
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 - Background music in video is very bouncy/staccato and varied in pitch, making it distracting and difficult to follow the voice-over.
- Voice-over sounds very clipped British English; if doing further voice-artist work, could be helpful to have a less less regionally distinctive accent.

*new comment on april 27* Are there sufficient decibels of differentiation between the background music and the voice-over narration, per https://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-noaudio ? Or is there a way to stop the background music from playing? While this is a AAA success criteria, I thought it would be one way to quantify the difficulty that some people may have listening to the voice-over narrative when played with the current background music. It would be better if the background music could either be turned off (it is not essential to the message); or reduced a lot in volume; or only played as a branding lead-in and wrap-up, i.g. at the beginning and the end, but not continuously throughout the narrative.

View by choice

ChoiceResponders
I accept this video as it is.
  • Denis Boudreau
  • Sharron Rush
  • Eric Eggert
  • Susan Hewitt
  • Brent Bakken
  • James Green
  • Howard Kramer
  • Andrew Arch
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Denis Boudreau
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
  • Laura Keen
  • Susan Hewitt
  • Judy Brewer
I abstain.

3. Keyboard Compatibility - Text

summary | by responder | by choice

Please review the text for Keyboard Compatibility (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 3
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 2
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 3
I abstain. 2

(1 response didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Keyboard Compatibility - TextComments
Laura Keen
  • I accept this text as it is.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Comments in GitHub
Eric Eggert
  • I accept this text as it is.
Susan Hewitt
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 See my specific suggestion re: editing the text in github.
Brent Bakken
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Change wording:
"It is also useful in many other circumstances, such as for people with injuries like a broken arm or repetitive stress injuries (RSI)."

"It also allows websites to be usable with screen readers, on public terminals (kiosks) without a mouse, or when the mouse simply breaks.
James Green
  • I abstain.
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 [This allows them to be usable by people using on-screen (touch), ergonomic, and specialized keyboards, as well as by voice recognition] should maybe include some mention of regular keyboard tabbing, whether by hand, stick/wand, eye-tracking, or other.
Shawn Lawton Henry
Judy Brewer
  • I abstain.

View by choice

ChoiceResponders
I accept this text as it is.
  • Laura Keen
  • Eric Eggert
  • Howard Kramer
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Brent Bakken
  • Andrew Arch
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
I abstain.
  • James Green
  • Judy Brewer

4. Colors With Good Contrast - Video

summary | by responder | by choice

Please review the video for Colors With Good Contrast (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 7
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 3
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
I abstain.

(1 response didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Colors With Good Contrast - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I accept this video as it is.
 Thumbs up!
Sharron Rush
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 This video is muddled, the point is not clear. The guy on the couch seems to have nothing to do with story being told, maybe just stick with the person finding her way on the street.

Comments about supporting text in GitHub
Eric Eggert
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 I don’t really understand the scene with the notification (0:36–0:47), I don’t really know what that has to do with good contrasts… That he is able to see the notification? If so, that is very subtle. However I think the shot leaves good breathing room for the narration, so that I’m totally ok with (me not understanding) it.
Susan Hewitt
  • I accept this video as it is.
Brent Bakken
  • I accept this video as it is.
 Music is good.
James Green
  • I accept this video as it is.
Howard Kramer
  • I accept this video as it is.
Andrew Arch
  • I accept this video as it is.
Shawn Lawton Henry * Simplify beginning & contrast more clear (pun intended) [low-medium] https://github.com/w3c/wai-showcase-examples/issues/146
* Clearer with narration & visuals [low-medium] https://github.com/w3c/wai-showcase-examples/issues/147
Judy Brewer
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 - I didn't understand before reading the text explanation that this was a demo of color contrast and glare inside and outside; I thought it was a demo of two people using a messaging app to communicate their location; so the accessibility point of the video was difficult to figure out. The text on the website took care of that, but others might have the same misunderstanding. Perhaps the order of the video shots could be re-arranged, so that it is more clearly two distinct stories -- one outside, then one inside.

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Denis Boudreau
  • Susan Hewitt
  • Brent Bakken
  • James Green
  • Howard Kramer
  • Andrew Arch
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Sharron Rush
  • Eric Eggert
  • Judy Brewer
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
I abstain.

5. Colors With Good Contrast - Text

summary | by responder | by choice

Please review the text for Colors With Good Contrast (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 1
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 2
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 5
I abstain. 1

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Colors With Good Contrast - TextComments
Laura Keen
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Comments in GitHub
Eric Eggert
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 s/glar/glare/ (I think :-)
Susan Hewitt
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 "Many people have difficulty distinguishing [between] certain colors,..."
James Green
  • I abstain.
 typo: Glar should be glare. re: changing lighting conditions and glar, especially
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 I think we should specifically call out 'colour blindness' as this is the common term used for protanopia etc
Shawn Lawton Henry
Judy Brewer glare is misspelled as glar

View by choice

ChoiceResponders
I accept this text as it is.
  • Howard Kramer
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Brent Bakken
  • Andrew Arch
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Laura Keen
  • Denis Boudreau
  • Sharron Rush
  • Eric Eggert
  • Susan Hewitt
I abstain.
  • James Green

6. Clear Layout and Design - Video

summary | by responder | by choice

Please review the video for Clear Layout and Design (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 3
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 3
I do not accept this video unless the comments in GitHub or the Comments section below are addressed. 3
I abstain.

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Clear Layout and Design - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 While the title of the video reads "Clear layout and design", the narrator only announces "Layout and design". I would prefer that the full title of the video be announced, for consistency. Other than that, the video is great. I feel like the metaphor of the cupboard in this one is a little weaker than the metaphors of the other videos, but it's still really good.
Sharron Rush
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Seems to be trying to say an awful lot here. I think it is probably OK but not sure what happens to solve the bad site, does the woman just point him to a different pizza delivery web site?
Eric Eggert
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Visually there is _a lot_ going on in the kitchen, which underlines the point the video is making, but I wonder if that might be confusing for people. I wonder if the clean-up scene would make more sense after the problem is described.

Really, really, really minor: BENQ logo clearly visible. Guy using Mac OS on his Toshiba laptop freaks me out ;-)

Really, really, minor continuity: Detail Shots of the front of the laptop show a Mac, kitchen scene has a PC. I don’t think anyone notices. The cup next to laptop scene shows a black laptop (cover), the computer that is used is actually white.

Pizza-a-wai is great. Kudos to Kevin! :-D
Susan Hewitt
  • I accept this video as it is.
Brent Bakken
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 Music is okay, not the best, but no change needed.

At beginning, VO voice needs to say the title correctly, include the word "clear."
James Green
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 The narrator missed the word "clear" at the very beginning when reading the video title.
Howard Kramer
  • I accept this video as it is.
Andrew Arch
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 voice over should reflect the full title (clear layout and design)
Shawn Lawton Henry "Pizza-a-wai" he, he – also like the person with disability eating pizza at the end. :-)
UT participant: "didn't get the main point"
* misc [low-medium-high] #148 https://github.com/w3c/wai-showcase-examples/issues/148
Judy Brewer - The kitchen organization and pizza delivery metaphors work nicely in this video.
- Would still advise using a less regionally distinctive accent.

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Susan Hewitt
  • Howard Kramer
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Sharron Rush
  • Eric Eggert
  • Andrew Arch
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Brent Bakken
  • James Green
I abstain.

7. Clear Layout and Design - Text

summary | by responder | by choice

Please review the text for Clear Layout and Design (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 2
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 2
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 4
I abstain. 1

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Clear Layout and Design - TextComments
Laura Keen
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Comment is general to all supporting text. I would like to have specific, focused resources to help those who want to do so to take the next steps in understanding and applying what they are learning.
Eric Eggert
  • I accept this text as it is.
Susan Hewitt
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Rework suggestion:
Having clear layout and design helps people navigate the web and find content more easily. Website forms and applications can easily get complex and confusing. Using clear layout and design is essential for people with low vision who may only be seeing a small portion of the screen at a time, and for people with cognitive and learning disabilities who often need clarity and consistency to orient themselves on a website. It is also useful for people who may be viewing the website on a small computer screen, such as on a mobile device, or may be in a hurry to find the right information. Learn more about web accessibility - essential for some, useful for all.
James Green
  • I abstain.
 typo: cognitive
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 editorial suggestions in Github - https://github.com/w3c/wai-showcase-examples/pull/125
Shawn Lawton Henry
Judy Brewer

View by choice

ChoiceResponders
I accept this text as it is.
  • Eric Eggert
  • Howard Kramer
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Brent Bakken
  • Andrew Arch
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Laura Keen
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
I abstain.
  • James Green

8. Large Select Areas - Video

summary | by responder | by choice

Please review the video for Large Select Areas (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 8
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 1
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
I abstain.

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Large Select Areas - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I accept this video as it is.
 Thumbs up!
Sharron Rush
  • I accept this video as it is.
 Good! Point comes through clearly and stays focused.
Eric Eggert
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Minor comment: Yes, large tap areas help when moving around, but they are quite useless when you carry an electric kettle ;-)
Susan Hewitt
  • I accept this video as it is.
Brent Bakken
  • I accept this video as it is.
 Music is good on this video
James Green
  • I accept this video as it is.
Howard Kramer
  • I accept this video as it is.
Andrew Arch
  • I accept this video as it is.
Shawn Lawton Henry * Large Select Areas -> Large Click Targets [high] https://github.com/w3c/wai-showcase-examples/issues/149
Judy Brewer Didn't know what "select areas" meant in this context until watched video and realized it was "target areas." How widely is the term "select areas" used?

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
  • Brent Bakken
  • James Green
  • Howard Kramer
  • Andrew Arch
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Eric Eggert
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
I abstain.

9. Large Select Areas - Text

summary | by responder | by choice

Please review the text for Large Select Areas (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 3
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 1
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 4
I abstain. 1

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Large Select Areas - TextComments
Laura Keen
  • I accept this text as it is.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Comment is general to all supporting text. I would like to have specific, focused resources to help those who want to do so to take the next steps in understanding and applying what they are learning.
Eric Eggert
  • I accept this text as it is.
Susan Hewitt
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Not sure about the word sufficient in this sentence (plus spelling is wrong): "Providing sufficent select areas is essential for people with reduced dexterity, such as physical disabilities and tremors due to age."

Maybe, "Providing adequately sized select areas..."
James Green
  • I abstain.
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 editorial suggestions - https://github.com/w3c/wai-showcase-examples/pull/126
Shawn Lawton Henry
Judy Brewer - typo at "essential"
- please spell-check

View by choice

ChoiceResponders
I accept this text as it is.
  • Laura Keen
  • Eric Eggert
  • Howard Kramer
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Andrew Arch
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
  • Brent Bakken
I abstain.
  • James Green

10. Video Captions - Video

summary | by responder | by choice

Please review the video for Video Captions (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 5
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 2
I do not accept this video unless the comments in GitHub or the Comments section below are addressed. 2
I abstain.

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Video Captions - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 It felt as though the background music was a little louder one this one than the other videos. As such, I found the music to be a little disturbing on this one. Maybe we could lower it a bit more. I also didn't like the question at the beginning "annoying, isn't it?). I felt as though it wasn't punchy enough. I think we could re-frame it to have more impact.
Sharron Rush
  • I accept this video as it is.
 Yep, well done. I like the cheerfulness and clarity of message.
Eric Eggert
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 I think the pause after “if I stopped talking” is either too short or too long. I don’t feel the frustration yet. Also the video only shows a video of a woman talking, and even if the narrator says something, he probably wouldn’t say what the woman is saying, so the example is a bit weird.

I think it could be beneficial if there wasn’t a pause at all and the following sentence was different.

I really like how the rest of the video turned out (including Shadi’s Hitchcock moment ;-).
Susan Hewitt
  • I accept this video as it is.
Brent Bakken
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 Music is too bouncy and distracting. It is also a touch too loud and takes away from the VO.

Seconds 23 through 26 the VO speeds up. This needs to be slowed down again by adding more footage maybe.
James Green
  • I accept this video as it is.
Howard Kramer
  • I accept this video as it is.
Andrew Arch
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Is the music louder / more prominent in this video? Seemed to be - I found it distracting compared with the others.
Shawn Lawton Henry * Not cancer [HIGH – HIVE] https://github.com/w3c/wai-showcase-examples/issues/150
* Beginning stop not work [high] https://github.com/w3c/wai-showcase-examples/issues/153
* zoom to captions not visible [very low] https://github.com/w3c/wai-showcase-examples/issues/152
* Main point in visuals and narration [medium] https://github.com/w3c/wai-showcase-examples/issues/151
Judy Brewer Background music is much too loud, too bouncy, and too varied in pitch. Very difficult to follow the voice-over. Please switch the music.

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Sharron Rush
  • Susan Hewitt
  • James Green
  • Howard Kramer
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Eric Eggert
  • Andrew Arch
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Brent Bakken
I abstain.

11. Video Captions - Text

summary | by responder | by choice

Please review the text for Video Captions (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 3
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 1
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 4
I abstain. 1

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Video Captions - TextComments
Laura Keen
  • I accept this text as it is.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Previous comments apply to all supporting text. Need follow-on info that is more specific to topic.
Eric Eggert
  • I accept this text as it is.
Susan Hewitt
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Is the following statement true: "Captions are useful for people who are not fluent in the language," This is only true if captions are provided in the native language that is different than the language used in the video. If not provided, then captions are not "more" useful than the narration to a non-fluent user. Don't know if this phrase should be dropped or reworked somehow.

Wording Change: "They also [improve] search-engine indexing..."
James Green
  • I abstain.
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 editorial suggestions - https://github.com/w3c/wai-showcase-examples/pull/127

I didn't know search engines now index caption files.
Shawn Lawton Henry
Judy Brewer

View by choice

ChoiceResponders
I accept this text as it is.
  • Laura Keen
  • Eric Eggert
  • Howard Kramer
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Andrew Arch
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
  • Brent Bakken
I abstain.
  • James Green

12. Customizable Text - Video

summary | by responder | by choice

Please review the video for Customizable Text (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 8
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 1
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
I abstain.

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Customizable Text - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I accept this video as it is.
 Thumbs up!
Sharron Rush
  • I accept this video as it is.
 Hey, the toast worked out as a metaphor...good!
Eric Eggert
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 I like how it turned out, but I think the narration reinforces the view that websites need text formatting widgets. Instead of “allow the text to be customized”, I think about about something like “allow users to use their preferred text size, font and colors, for example”.
Susan Hewitt
  • I accept this video as it is.
 We covered this in earlier drafts of scripts and I understand it's too late to change but I
still don't think the toast metaphor makes sense. The older man has dark toast in the
first and the last scene. It isn't clear how any adjustments have helped him. Not jarring,
just visuals that don't seem to add anything.
Brent Bakken
  • I accept this video as it is.
 Good music
James Green
  • I accept this video as it is.
Howard Kramer
  • I accept this video as it is.
Andrew Arch
  • I accept this video as it is.
Shawn Lawton Henry UT participant: "too fast – I didn't get it"
* Narration distracts from visuals & vice versa [Medium] https://github.com/w3c/wai-showcase-examples/issues/145
* Toast & 2 guys doing what? [low] https://github.com/w3c/wai-showcase-examples/issues/144
Judy Brewer Music seems somewhat distracting on this one.

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
  • Brent Bakken
  • James Green
  • Howard Kramer
  • Andrew Arch
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Eric Eggert
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
I abstain.

13. Customizable Text - Text

summary | by responder | by choice

Please review the text for Customizable Text (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 3
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 2
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 2
I abstain. 1

(3 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Customizable Text - TextComments
Laura Keen
  • I accept this text as it is.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Previous comments apply to all supporting text. Need follow-on info that is more specific to topic.
Eric Eggert
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 It would be good if we could link to best practices on text customization (in the future).
Susan Hewitt See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Rework the second half of the text... example: "...Being able to customize text allows the user to control the content reflow better on different window and screen sizes, which makes it more usable across different devices. Text customization functionality requires support by both the website and the web browser."
James Green
  • I abstain.
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text as it is.
Shawn Lawton Henry
Judy Brewer

View by choice

ChoiceResponders
I accept this text as it is.
  • Laura Keen
  • Howard Kramer
  • Andrew Arch
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Eric Eggert
  • Brent Bakken
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Sharron Rush
I abstain.
  • James Green

14. Text to Speech - Video

summary | by responder | by choice

Please review the video for Text to Speech (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 6
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 3
I do not accept this video unless the comments in GitHub or the Comments section below are addressed. 1
I abstain.

(1 response didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Text to Speech - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 The title of that video does not get announced as the video starts. This is the only one where it had been forgotten. I wold expect the video to start with the narrator announcing "Text to speech" (before we start hearing the synthesized voice). Other than that, I think it's great.
Sharron Rush
  • I accept this video as it is.
Eric Eggert
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Totally not critical: Music on this one is a nudge to loud imo, at least at the end of the video.
Susan Hewitt
  • I accept this video as it is.
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 The volume of the background music makes it difficult to hear the speech output of the
devices.
Brent Bakken
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Music is good, but it is too loud throughout and should be even lower during TTS audio sections. it is currently fighting with the VO.
James Green
  • I accept this video as it is.
Howard Kramer
  • I accept this video as it is.
Andrew Arch
  • I accept this video as it is.
Shawn Lawton Henry * Visual disabilities -> blind [high; hive] https://github.com/w3c/wai-showcase-examples/issues/154
Judy Brewer

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Sharron Rush
  • Susan Hewitt
  • James Green
  • Howard Kramer
  • Andrew Arch
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Eric Eggert
  • Susan Hewitt
  • Brent Bakken
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
I abstain.

15. Text to Speech - Text

summary | by responder | by choice

Please review the text for Text to Speech (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 2
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 3
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 3
I abstain. 1

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Text to Speech - TextComments
Laura Keen
  • I accept this text as it is.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Previous comments apply to all supporting text. Need follow-on info that is more specific to topic.
Eric Eggert
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 “It is also used by people with cognitive and learning disabilities, such as some forms of dyslexia, to see and hear the content to better understand it.”

That sentence doesn’t work for me, I read the “such as” to be connected to people and my brain tells me there are “people such as some forms of dyslexia”.

Maybe: ”It is also used by people with cognitive and learning disabilities, like with some forms of dyslexia, to see and hear the content to better understand it.“
Susan Hewitt
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Reword in brackets: "[Having what is on the screen be read aloud] is an essential function for people with visual disabilities. [Text to Speech] is also used by people with cognitive and learning disabilities, such as some forms of dyslexia, to see and hear the content to better understand it. [If properly developed], this functionality is available for everyone on most computers and mobile devices. It is useful for people who prefer to listen rather than read, who cannot look at the screen, or [who prefer] to multi-task. Learn more about web accessibility - esential for some, useful for all."
James Green
  • I abstain.
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 editorial suggestion - https://github.com/w3c/wai-showcase-examples/pull/129
Shawn Lawton Henry
Judy Brewer

View by choice

ChoiceResponders
I accept this text as it is.
  • Laura Keen
  • Howard Kramer
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Eric Eggert
  • Brent Bakken
  • Andrew Arch
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
I abstain.
  • James Green

16. Voice Recognition - Video

summary | by responder | by choice

Please review the video for Voice Recognition (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 8
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 1
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
I abstain.

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Voice Recognition - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I accept this video as it is.
 Thumbs up!
Sharron Rush
  • I accept this video as it is.
Eric Eggert
  • I accept this video as it is.
 [Clearly visible Apple logo]
Susan Hewitt
  • I accept this video as it is.
Brent Bakken
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Music is okay. Need to increase the volume of the VO voice on this video.
James Green
  • I accept this video as it is.
Howard Kramer
  • I accept this video as it is.
Andrew Arch
  • I accept this video as it is.
Shawn Lawton Henry * misc [medium] https://github.com/w3c/wai-showcase-examples/issues/155
Judy Brewer - whistling in background is nice but too loud

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Denis Boudreau
  • Sharron Rush
  • Eric Eggert
  • Susan Hewitt
  • James Green
  • Howard Kramer
  • Andrew Arch
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Brent Bakken
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
I abstain.

17. Voice Recognition - Text

summary | by responder | by choice

Please review the text for Voice Recognition (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 4
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 3
I abstain. 1

(3 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Voice Recognition - TextComments
Laura Keen
  • I accept this text as it is.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Previous comments apply to all supporting text. Need follow-on info that is more specific to topic.
Eric Eggert
  • I accept this text as it is.
Susan Hewitt See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Word addition: "Today most computers and mobile devices can be used through voice [input/command], rather than by typing and clicking."

Word change & spelling: "Voice recognition technology is essential for people with physical [disabilities] who [cannot use] the keyboard and mouse."
James Green
  • I abstain.
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text as it is.
Shawn Lawton Henry
Judy Brewer typo at "esential" -- should be "essential" (please check all)

View by choice

ChoiceResponders
I accept this text as it is.
  • Laura Keen
  • Eric Eggert
  • Howard Kramer
  • Andrew Arch
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Sharron Rush
  • Brent Bakken
I abstain.
  • James Green

18. Understandable Content - Video

summary | by responder | by choice

Please review the video for Understandable Content (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 5
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 3
I do not accept this video unless the comments in GitHub or the Comments section below are addressed. 1
I abstain.

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Understandable Content - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Great video, however, I struggled with understand what the narrator said at the beginning. It's probably intended to be that way, but it was annoying to have to restart the video 4-5 times to get a feel of what was said.
Sharron Rush
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Need a bit more context or something to understand why they are making such a mess of the cake. Not realistic that they would not look for an easier recipe earlier on.
Eric Eggert
  • I accept this video as it is.
 Great! I like this one a lot.
Susan Hewitt
  • I accept this video as it is.
Brent Bakken
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Music is good.

See my previous edit for the VO about the word "lack" sounding too much like "like" and the suggestion for the following sentence.
James Green
  • I accept this video as it is.
Howard Kramer
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 This was the only video that I didn't think worked. It just wasn't clear what was meant by understandable content as it was relayed by the action on the screen.
Andrew Arch
  • I accept this video as it is.
Shawn Lawton Henry * Clarity [low] https://github.com/w3c/wai-showcase-examples/issues/157
* Narration and visuals competing for attention [medium] https://github.com/w3c/wai-showcase-examples/issues/156
Judy Brewer Cooperative cooking scenario with difficult recipe seems to work well as a metaphor for understandable content

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Eric Eggert
  • Susan Hewitt
  • James Green
  • Andrew Arch
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Denis Boudreau
  • Sharron Rush
  • Brent Bakken
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
  • Howard Kramer
I abstain.

19. Understandable Content - Text

summary | by responder | by choice

Please review the text for Understandable Content (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 3
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 1
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 4
I abstain. 1

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Understandable Content - TextComments
Laura Keen
  • I accept this text as it is.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Previous comments apply to all supporting text. Need follow-on info that is more specific to topic.
Eric Eggert
  • I accept this text as it is.
Susan Hewitt
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Reword first sentence: "Avoiding overly complex language, jargon, and acronyms, and providing [structure like] using headings, lists, and separation is a fundamental aspect of making content understandable.

Not sure about the phrase "...people with lower literacy." at the end for the paragraph. Just does not sound correct. Maybe add the word "skills" at the end.
James Green
  • I abstain.
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 [... lists, and separation ...] - separation of what? paragraphs with white space?
Shawn Lawton Henry
Judy Brewer The complicated vocabulary at the start of the script seems too confusing to make the point well; it is just plain confusing.

View by choice

ChoiceResponders
I accept this text as it is.
  • Laura Keen
  • Eric Eggert
  • Howard Kramer
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Andrew Arch
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
  • Brent Bakken
I abstain.
  • James Green

20. Notifications and Feedback - Video

summary | by responder | by choice

Please review the video for Notifications and Feedback (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this video as it is. 6
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 1
I do not accept this video unless the comments in GitHub or the Comments section below are addressed. 2
I abstain.

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Notifications and Feedback - VideoComments
Laura Keen
  • I accept this video as it is.
Denis Boudreau
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 I don't like that title, I find the the use of the word "notifications" makes it unnecessarily complex and confusing. I would much rather prefer we use the word "instructions" instead. The video itself is great, but I would advocate for changing the title.
Sharron Rush
  • I accept this video as it is.
Eric Eggert
  • I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 I don’t think we can change that, but I find it unfortunate that it is two times the same error.

Really, really minor: I think the initial cuckoo shot could use some more time, especially zooming out from the hands to reveal the door where nothing is happening.
Susan Hewitt
  • I accept this video as it is.
Brent Bakken
  • I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
 Music is good.

Don't use the image of the coo-coo bird as the thumbnail for the video. Just the clock without the bird showing. Takes away from the anticipation being built at the beginning if they see it before the video starts.
James Green
  • I accept this video as it is.
Howard Kramer
  • I accept this video as it is.
Andrew Arch
  • I accept this video as it is.
Shawn Lawton Henry * Make important visuals understandable ;-) [medium-high] https://github.com/w3c/wai-showcase-examples/issues/158
Judy Brewer - The cuckoo clock doesn't seem to help tell the story on this one -- it even seems a bit annoying, though I'm not sure why; whereas the other visual examples seem to work well. Not a big issue, but it was the only part of the videos that I found vaguely annoying.
- Again I advise using a less regionally distinctive accent if possible.

View by choice

ChoiceResponders
I accept this video as it is.
  • Laura Keen
  • Sharron Rush
  • Susan Hewitt
  • James Green
  • Howard Kramer
  • Andrew Arch
I accept this video; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Eric Eggert
I do not accept this video unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Brent Bakken
I abstain.

21. Notifications and Feedback - Text

summary | by responder | by choice

Please review the text for Notifications and Feedback (note the review questions in the introduction of this survey).

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this text as it is. 3
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 2
I do not accept this text unless the comments in GitHub or the Comments section below are addressed. 3
I abstain. 1

(2 responses didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Notifications and Feedback - TextComments
Laura Keen
  • I accept this text as it is.
Denis Boudreau
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 I would prefer that the text that goes with the video be a direct transcript of what is being said in the audio track. There's also a typo in that paragraph for the word "esential".
Sharron Rush
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 Previous comments apply to all supporting text. Need follow-on info that is more specific to topic.
Eric Eggert
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 I don’t think we need the word “particularly” in the first sentence.
Susan Hewitt
  • I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
 See my suggestion re: editing the text in github and re: improving inks.
Brent Bakken
  • I accept this text as it is.
James Green
  • I abstain.
Howard Kramer
  • I accept this text as it is.
Andrew Arch
  • I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 editorial suggestions - https://github.com/w3c/wai-showcase-examples/pull/130
Shawn Lawton Henry
Judy Brewer

View by choice

ChoiceResponders
I accept this text as it is.
  • Laura Keen
  • Brent Bakken
  • Howard Kramer
I accept this text; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Eric Eggert
  • Andrew Arch
I do not accept this text unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Sharron Rush
  • Susan Hewitt
I abstain.
  • James Green

22. Learn More about Web Accessibility

summary | by responder | by choice

Please review the section Learn More about Web Accessibility.

Please add any comments in GitHub as new issues or pull requests. If you are not comfortable with GitHub, please add your comments below.

Summary

ChoiceAll responders
Results
I accept this section as it is. 5
I accept this section; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion. 3
I do not accept this section unless the comments in GitHub or the Comments section below are addressed. 2
I abstain.

(1 response didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Learn More about Web AccessibilityComments
Laura Keen
  • I accept this section as it is.
Denis Boudreau
  • I do not accept this section unless the comments in GitHub or the Comments section below are addressed.
 I don't like the way that content is currently presented. I would prefer if we presented it in a way where esch bulleted item would begin with a link, followed by a short description of the resource. Such as:

* [link - Introduction to Web Accessibility]
Short description of the resource
* [link - How People with Disabilities Use the Web]
Short description of the resource
* [link - Tips for Getting Started with Web Accessibility]
Short description of the resource
* [link - Developing a Web Accessibility Business Case for Your Organization]
Short description of the resource
Sharron Rush
  • I accept this section as it is.
  • I accept this section; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 The section is fine as is however as noted, the previous sections need more specific links to support materials for each topic.
Eric Eggert
  • I accept this section; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Is that all we’re planning to point people to? If so, we should add more concrete advice to the individual videos asap. I think each video section should (not now but in the future) answer the question “What can I do about it?”
Susan Hewitt
  • I do not accept this section unless the comments in GitHub or the Comments section below are addressed.
Brent Bakken
  • I accept this section; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
 Reword second sentence: "The following list provides you with the basics to help you get started:"
James Green
  • I accept this section as it is.
Howard Kramer
  • I accept this section as it is.
Andrew Arch
  • I accept this section as it is.
Shawn Lawton Henry
Judy Brewer It seems a bit odd to click the link for "learn more about..." and just end up on the bottom of a page.

View by choice

ChoiceResponders
I accept this section as it is.
  • Laura Keen
  • Sharron Rush
  • James Green
  • Howard Kramer
  • Andrew Arch
I accept this section; however, I suggest the changes in GitHhub or in the Comments section below - for editors' discretion.
  • Sharron Rush
  • Eric Eggert
  • Brent Bakken
I do not accept this section unless the comments in GitHub or the Comments section below are addressed.
  • Denis Boudreau
  • Susan Hewitt
I abstain.

More details on responses

  • Laura Keen: last responded on 21, April 2016 at 15:51 (UTC)
  • Denis Boudreau: last responded on 23, April 2016 at 00:30 (UTC)
  • Sharron Rush: last responded on 23, April 2016 at 20:25 (UTC)
  • Eric Eggert: last responded on 27, April 2016 at 08:04 (UTC)
  • Susan Hewitt: last responded on 27, April 2016 at 14:48 (UTC)
  • Brent Bakken: last responded on 27, April 2016 at 22:12 (UTC)
  • James Green: last responded on 28, April 2016 at 03:52 (UTC)
  • Howard Kramer: last responded on 28, April 2016 at 04:57 (UTC)
  • Andrew Arch: last responded on 28, April 2016 at 07:15 (UTC)
  • Shawn Lawton Henry: last responded on 28, April 2016 at 15:29 (UTC)
  • Judy Brewer: last responded on 29, April 2016 at 02:59 (UTC)

Non-responders

The following persons have not answered the questionnaire:

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