w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire EOWG Review: Training Resource Suite
The results of this questionnaire are available to anybody.
This questionnaire was open from 2012-10-18 to 2012-11-21.
10 answers have been received.
Jump to results for question:
- Support for publishing and announcing the pages as drafts for public review
- Overview page
- Topics page
- Presentation Outlines page
- Workshop Outline page
1. Support for publishing and announcing the pages as drafts for public review
Summary
| Choice | All responders |
|---|---|
| Results | |
| I support publishing these Training pages as they are | 8 |
| I support publishing these Training pages; however, I suggest the changes in the comments sections below (for editors' discretion) | 2 |
| I support publishing these Training pages only with the changes in the comments sections below | |
| I do not support publishing these Training pages, because of the comments in the comments sections below | |
| I abstain (not vote) |
Details
| Responder | Support for publishing and announcing the pages as drafts for public review |
|---|---|
| Sharron Rush | I support publishing these Training pages as they are |
| Andrew Arch | I support publishing these Training pages as they are |
| Wayne Dick | I support publishing these Training pages as they are |
| Suzette Keith | I support publishing these Training pages as they are |
| Jennifer Sutton | I support publishing these Training pages as they are |
| Shadi Abou-Zahra | I support publishing these Training pages; however, I suggest the changes in the comments sections below (for editors' discretion) |
| Ian Pouncey | I support publishing these Training pages as they are |
| Vicki Menezes Miller | I support publishing these Training pages as they are |
| Emmanuelle Gutiérrez y Restrepo | I support publishing these Training pages as they are |
| Sylvie Duchateau | I support publishing these Training pages; however, I suggest the changes in the comments sections below (for editors' discretion) |
2. Overview page
Overview
For each comment, remember to indicate if it is a suggestion for editor's discretion or if you feel it must be addressed before this version is published.
For each comment, remember to indicate if it is a suggestion for editor's discretion or if you feel it must be addressed before this version is published.
Details
| Responder | Overview page |
|---|---|
| Sharron Rush | |
| Andrew Arch | |
| Wayne Dick | It is excellent |
| Suzette Keith | Excellant |
| Jennifer Sutton | |
| Shadi Abou-Zahra | priority: important to be addressed before publication location: intro sentence current wording: WAI offers materials for speakers and trainers suggested revision: WAI offers materials for speakers, lecturers, educators, and other trainers rationale: we use the term "trainers" throughout the suite to reference all types of educators including university lecturers, college teachers, and other (non-commercial) educators who may not consider themselves to be trainers (side note: I wonder if the term "presenter" is better than "trainer"?) priority: important to be addressed before publication location: notes section current wording: We encourage you to share accessibility information suggested revision: rationale: love it! |
| Ian Pouncey | |
| Vicki Menezes Miller | |
| Emmanuelle Gutiérrez y Restrepo | |
| Sylvie Duchateau | If possible before publication, but at editor's discretion: Nearly last paragraph on the page. Rationale: links are not really clear as they are url. It would be clerer to indicate the name of the document rather than it's link, or add the url beside the link. Actual wording: "it's fine to say that you don't know the answer. That is a great opportunity to look for the answer on the http://www.w3.org/WAI/yourWAI with your audience, or say that you will find the answer later and ask the question on the http://www.w3.org/WAI/IG/#mailinglist." Proposal: it's fine to say that you don't know the answer. That is a great opportunity to look for the answer on the your wai page at: http://www.w3.org/WAI/yourWAI with your audience, or say that you will find the answer later and ask the question on the WAI-ig interest list at http://www.w3.org/WAI/IG/#mailinglist. |
3. Topics page
Topics
For each comment, remember to indicate if it is a suggestion for editor's discretion or if you feel it must be addressed before this version is published.
For each comment, remember to indicate if it is a suggestion for editor's discretion or if you feel it must be addressed before this version is published.
Details
| Responder | Topics page |
|---|---|
| Sharron Rush | |
| Andrew Arch | |
| Wayne Dick | |
| Suzette Keith | Excellant |
| Jennifer Sutton | |
| Shadi Abou-Zahra | priority: medium location: Introducing Web Accessibility current wording: WAI guidelines as the international standard for web accessibility suggested revision: WAI guidelines and [standards / resources / specifications] as the international standard for web accessibility rationale: broaden the scope from the guidelines only to include other WAI work, in particular WAI-ARIA and IndieUI (but also the very important EO resources!) - together they define web accessibility... (note: we use "WAI standards and guidelines" in "Components of Web Accessibility" section) priority: mild location: Introducing Web Accessibility current wording: Question: Ask attendees suggested revision: Example question: Ask attendees or Example activity: Ask attendees rationale: (1) highlight that this is only an example even though the section is called "suggestions for speakers", (2) it is really more of an activity or discussion rather than a question priority: medium location: Components of Web Accessibility current wording: authoring tools suggested revision: tools used by content authors rationale: authoring tools is kind of jargony? priority: medium location: Migrating to WCAG 2 current wording: Tip: Communicating migration suggested revision: Tip: Remind participants that communicating migration or Explain to participants ... rationale: it is really a tip for the participants rather than for the presenter priority: mild location: Accessibility and the Mobile Web current wording: suggested revision: Tip: Use Independent User Interfaces (IndieUI) to attract advanced web developers to leading edge accessibility work and how it is relevant to many others rationale: think IndieUI is often an attention-graber for geeky developers (at least currently) and raises their attention that accessibility is not only about alt-tags priority: strong location: Conformance Evaluation for Web Accessibility current wording: Conformance Evaluation of Web Sites for Accessibility (link) suggested revision: rationale: confirm that this title will remain - I suspect it may change very soon, at least to change "Web Sites" to "Websites"? |
| Ian Pouncey | I think this is a great general resource, not just for training. I can replace a lot of bookmarks with this one page! |
| Vicki Menezes Miller | |
| Emmanuelle Gutiérrez y Restrepo | |
| Sylvie Duchateau | fAt edditor's discretion, for future edit: In 14: "web accessibility and older users". Paragraph suggestion for speakers: may be showing videos may not be sufficcient. It could be helpful to show the audience some simulations of sight reduction, letting them use another pointing device, enlarging font size on a browser, letting them use the mouse with the other hand and so on... In 15, accessibility and the mobile web: paragraph audience. You have the word "audience twice". Before publication, delete one of the "audience:". |
4. Presentation Outlines page
Presentation Outlines
For each comment, remember to indicate if it is a suggestion for editor's discretion or if you feel it must be addressed before this version is published.
For each comment, remember to indicate if it is a suggestion for editor's discretion or if you feel it must be addressed before this version is published.
Details
| Responder | Presentation Outlines page |
|---|---|
| Sharron Rush | |
| Andrew Arch | |
| Wayne Dick | Excellent |
| Suzette Keith | Excellant |
| Jennifer Sutton | |
| Shadi Abou-Zahra | priority: strong location: Using an accessible web current wording: suggested revision: add Useful resource: Better Web Browsing: Tips for Customizing Your Computer rationale: think this resource is very relevant to this topic and should be referenced prominently (not only under the respective Topics as it may be missed) priority: mild location: Using an accessible web current wording: suggested revision: add a tip to reuse content from "Better Web Browsing: Tips for Customizing Your Computer" as handouts, course material, exercise material, or whatever rationale: think this resource can be used in many ways to support training on this topic, and presenters may not immediately make that connection priority: strong location: Accessible web design current wording: suggested revision: add "Involving Users" somewhere, probably as "Useful resource" and under "Designing accessible websites with WCAG 2", or maybe as a tip or note instead rationale: think this resource is very relevant to this topic and should be referenced prominently (not only under the respective Topics as it may be missed) |
| Ian Pouncey | |
| Vicki Menezes Miller | |
| Emmanuelle Gutiérrez y Restrepo | |
| Sylvie Duchateau |
5. Workshop Outline page
Workshop Outlines
For each comment, remember to indicate if it is a suggestion for editor's discretion or if you feel it must be addressed before this version is published.
For each comment, remember to indicate if it is a suggestion for editor's discretion or if you feel it must be addressed before this version is published.
Details
| Responder | Workshop Outline page |
|---|---|
| Sharron Rush | |
| Andrew Arch | |
| Wayne Dick | Excellent |
| Suzette Keith | Excellant |
| Jennifer Sutton | |
| Shadi Abou-Zahra | priority: for editors' discretion location: throughout current wording: suggested revision: consider adding the mobile topic, accessibility web design topic, and quick check topic? maybe for future wishlist? maybe can do a compromise rationale: think these topics are very important but it may be a significantly different scope than the current one. Quick Check and Mobile are mentioned but not very prominently (not visible from skimming the outline) and accessible web design isn't mentioned at all. |
| Ian Pouncey | |
| Vicki Menezes Miller | |
| Emmanuelle Gutiérrez y Restrepo | |
| Sylvie Duchateau |
More details on responses
- Sharron Rush: last responded on 19, October 2012 at 02:01 (UTC)
- Andrew Arch: last responded on 22, October 2012 at 09:58 (UTC)
- Wayne Dick: last responded on 26, October 2012 at 12:20 (UTC)
- Suzette Keith: last responded on 26, October 2012 at 14:23 (UTC)
- Jennifer Sutton: last responded on 27, October 2012 at 19:53 (UTC)
- Shadi Abou-Zahra: last responded on 2, November 2012 at 21:54 (UTC)
- Ian Pouncey: last responded on 20, November 2012 at 14:55 (UTC)
- Vicki Menezes Miller: last responded on 20, November 2012 at 16:04 (UTC)
- Emmanuelle Gutiérrez y Restrepo: last responded on 20, November 2012 at 16:11 (UTC)
- Sylvie Duchateau: last responded on 20, November 2012 at 16:11 (UTC)
Non-responders
The following persons have not answered the questionnaire:
- Eric Velleman
- Shawn Lawton Henry
- Kazuhito Kidachi
- Jedi Lin
- David Sloan
- Mary Jo Mueller
- Reinaldo Ferraz
- Bill Kasdorf
- Cristina Mussinelli
- Kevin White
- 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