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 address: shawn@w3.org
This questionnaire was open from 2017-07-07 to 2017-07-21.
15 answers have been received.
Jump to results for question:
summary | by responder | by choice
Please read or skim the 7 July 2017 EOWG teleconference meeting minutes. Indicate your approval or concerns with the minutes and resolution(s) passed at that meeting. The summary and the link to the full minutes is on the 2017 Minutes wiki page.
If you missed the teleconference, please indicate on the wiki page that you read the minutes — after [done], add your name and date.
Choice | All responders |
---|---|
Results | |
I was in the teleconference and I don't have any comments on the Resolutions or minutes. | 11 |
I have reviewed the minutes and agree to the Resolutions passed. | 3 |
I have reviewed the minutes but have concerns with the minutes or Resolutions, and I explain them below. | |
I have not read the minutes yet, and have put the date for my review into the comments box. |
(1 response didn't contain an answer to this question)
Skip to view by choice.
Responder | Minutes and Resolutions of 7 July 2017 | Comments |
---|---|---|
Eric Eggert | ||
Vivienne Conway |
|
|
Amanda Mace |
|
|
Laura Keen |
|
|
Sylvie Duchateau |
|
|
Howard Kramer |
|
|
Brent Bakken |
|
|
Norah Sinclair |
|
|
James Green |
|
|
Shawn Lawton Henry |
|
|
Robert Jolly |
|
|
Kris Anne Kinney |
|
|
Sharron Rush |
|
|
Denis Boudreau |
|
|
Shadi Abou-Zahra |
|
Choice | Responders |
---|---|
I was in the teleconference and I don't have any comments on the Resolutions or minutes. |
|
I have reviewed the minutes and agree to the Resolutions passed. |
|
I have reviewed the minutes but have concerns with the minutes or Resolutions, and I explain them below. | |
I have not read the minutes yet, and have put the date for my review into the comments box. |
As discussed in the 7 July telecon, we are trying an approach where we have Editor/Lead Teams (2 people), and Review Teams (3+ people) to help as the resource/project develops. (All EOWG participants will continue to review and approve EOWG Resources before they are published.)
We have some work to wrap up the current charter work, and a major focus of the next charter is updating EOWG Resources along with the WAI site redesign. In order to achieve this in a timely manner, we are asking all participants to step up and lead in the effort.
Please see the Resources and Projects along with links and notes on type of work, effort, and timing in these two tables:
These are generally in priority/timing order, although we can tweak the order.
13 July update: See the results and note where we need additional contributors. Several people expressed interest in being a co-editor for multiple resources (thanks!), yet will only do one at a time — so even some that have 2+ editors listed in the survey results, will still another person to cover it. Please sign up for all that you are interested in/willing to help with.
Responder | Comments |
---|---|
Eric Eggert | |
Vivienne Conway | |
Amanda Mace | |
Laura Keen | |
Sylvie Duchateau | |
Howard Kramer | |
Brent Bakken | |
Norah Sinclair | |
James Green | |
Shawn Lawton Henry | |
Robert Jolly | |
Kris Anne Kinney | |
Sharron Rush | |
Denis Boudreau | |
Shadi Abou-Zahra |
summary | by responder | by choice
From the following list, please select all of the resources that you would be interested in serving on the editor/lead team (team of 2 people). Include in Comments your top preferences, availability notes, etc. (Work that is not listed does not need additional editors at this time.)
Note: By selecting multiple resources it will be easier to make editor assignments. Also, when one resource is complete, we can assign you to the next highest priority resource. You will only be assigned to editor/lead on one resource at a time.
13 July update: Removed Tips and BAD that do not need co-editor.
Choice | All responders |
---|---|
Results | |
Web Accessibility Laws and Policies | 1 |
Understanding WCAG 2.1 | 5 |
Intro to Accessibility | 4 |
UI Components List | 1 |
Mobile Accessibility Resources | |
Older User resources | 1 |
Developing Presentations and Training | 5 |
Presentations - update existing | 5 |
Easy Checks | 3 |
How People with Disability Use the Web | 3 |
Translations | 3 |
Presentations - develop new | 4 |
Outreach campaigns | 3 |
Developing a Web Accessibility Business Case for Your Organization | 3 |
Selecting Web Accessibility Evaluation Tools | 4 |
Evaluation resources: - Evaluation Approaches for Specific Contexts - Using Combined Expertise to Evaluate Web Accessibility - Template for Accessibility Evaluation Reports | 4 |
Selecting and Using Authoring Tools for Web Accessibility | 1 |
Skip to view by choice.
Responder | Resource Editor / Project Lead Teams | Comments |
---|---|---|
Eric Eggert |
|
also Tutorials, and helping with other resources Translations – German |
Vivienne Conway |
|
I've ticked quite a few, but thankfully you way I'd only be on one at a time. My expertise is in digital accessibility evaluation, presentations and training, and working with business. So I'm happy to work on any that relate to this (one at a time of course :) |
Amanda Mace | ||
Laura Keen |
|
|
Sylvie Duchateau |
|
these are all documents I am interested in contributing. But I am not sure feeling confortable in editing them alone. |
Howard Kramer |
|
As per our previous charter discussions, I'm most interested in Curriculum/Training/Teaching material since that aligns with my grant. Not sure if that falls under Presentations - develop new or is considered a completely separate area. |
Brent Bakken |
|
Don't know that I need to facilitate the Understandings Task Force (Happy to do so if needed) but definitely want to be on the Task Force. |
Norah Sinclair |
|
|
James Green |
|
|
Shawn Lawton Henry | Will work out my priorities with Co-Chairs and other W3C Staff. | |
Robert Jolly |
|
|
Kris Anne Kinney |
|
|
Sharron Rush |
|
|
Denis Boudreau |
|
|
Shadi Abou-Zahra |
|
Also "Better Web Browsing". Order of priority/availability: - Evaluation resources - Better Web Browsing - How people use web |
Choice | Responders |
---|---|
Web Accessibility Laws and Policies |
|
Understanding WCAG 2.1 |
|
Intro to Accessibility |
|
UI Components List |
|
Mobile Accessibility Resources | |
Older User resources |
|
Developing Presentations and Training |
|
Presentations - update existing |
|
Easy Checks |
|
How People with Disability Use the Web |
|
Translations |
|
Presentations - develop new |
|
Outreach campaigns |
|
Developing a Web Accessibility Business Case for Your Organization |
|
Selecting Web Accessibility Evaluation Tools |
|
Evaluation resources: - Evaluation Approaches for Specific Contexts - Using Combined Expertise to Evaluate Web Accessibility - Template for Accessibility Evaluation Reports |
|
Selecting and Using Authoring Tools for Web Accessibility |
|
summary | by responder | by choice
From the following list, please select all of the resources that you would be interested in serving on the reviewer team (team of three or more).
Note: You may be assigned to up to three review teams at a time.
13 July update: Added Tips for Procuring.
Choice | All responders |
---|---|
Results | |
Web Accessibility Laws and Policies | 4 |
Editorial guidelines | 3 |
Accessible Media Tutorial | 3 |
Mobile Accessibility Developers Intro | 5 |
ARIA Developers Intro | 4 |
Tips for Evaluating | 9 |
Tips for Advocating | 7 |
Tips for Procuring | 4 |
BAD update | 8 |
BAD instructions | 8 |
Understanding WCAG 2.1 | 6 |
Intro to Accessibility | 8 |
UI Components List | 2 |
Mobile Accessibility Resources | 4 |
Older User resources | 4 |
Developing Presentations and Training | 8 |
Presentations - update existing | 5 |
Easy Checks | 7 |
How People with Disability Use the Web | 5 |
Translations | 3 |
Presentations - develop new | 6 |
Outreach campaigns | 2 |
Developing a Web Accessibility Business Case for Your Organization | 5 |
Selecting Web Accessibility Evaluation Tools | 6 |
Evaluation resources: - Evaluation Approaches for Specific Contexts - Using Combined Expertise to Evaluate Web Accessibility - Template for Accessibility Evaluation Reports | 6 |
Selecting and Using Authoring Tools for Web Accessibility | 3 |
Skip to view by choice.
Responder | Review Teams | Comments |
---|---|---|
Eric Eggert |
|
Translations – German |
Vivienne Conway |
|
|
Amanda Mace |
|
|
Laura Keen |
|
|
Sylvie Duchateau |
|
|
Howard Kramer |
|
|
Brent Bakken |
|
|
Norah Sinclair |
|
|
James Green |
|
|
Shawn Lawton Henry | Will work out my priorities with Co-Chairs and other W3C Staff. | |
Robert Jolly |
|
My assumption is that all of these won't be happening simultaneously. :) |
Kris Anne Kinney |
|
|
Sharron Rush |
|
|
Denis Boudreau |
|
|
Shadi Abou-Zahra |
|
Choice | Responders |
---|---|
Web Accessibility Laws and Policies |
|
Editorial guidelines |
|
Accessible Media Tutorial |
|
Mobile Accessibility Developers Intro |
|
ARIA Developers Intro |
|
Tips for Evaluating |
|
Tips for Advocating |
|
Tips for Procuring |
|
BAD update |
|
BAD instructions |
|
Understanding WCAG 2.1 |
|
Intro to Accessibility |
|
UI Components List |
|
Mobile Accessibility Resources |
|
Older User resources |
|
Developing Presentations and Training |
|
Presentations - update existing |
|
Easy Checks |
|
How People with Disability Use the Web |
|
Translations |
|
Presentations - develop new |
|
Outreach campaigns |
|
Developing a Web Accessibility Business Case for Your Organization |
|
Selecting Web Accessibility Evaluation Tools |
|
Evaluation resources: - Evaluation Approaches for Specific Contexts - Using Combined Expertise to Evaluate Web Accessibility - Template for Accessibility Evaluation Reports |
|
Selecting and Using Authoring Tools for Web Accessibility |
|
In order to be more consistent with the content (especially with multiple editors), we are expanding the WAI Style Guide for Editors to adhere to when editing existing or creating new content.
Please look over the draft Style Guide and suggest additions, edits, or clarification that you feel should be included.
Please send comments to wai-eo-editors@w3.org with subject: [style guide]..., or list your comments in the comments field below.
Choice | All responders |
---|---|
Results | |
I have sent comments to wai-eo-editors@w3.org or added them to the comment field below. | 5 |
I have no additions or edits at this time. | 10 |
Responder | WAI Site Style Guide | Comments |
---|---|---|
Eric Eggert | I have sent comments to wai-eo-editors@w3.org or added them to the comment field below. | I might send more by the time the survey ends. |
Vivienne Conway | I have no additions or edits at this time. | |
Amanda Mace | I have no additions or edits at this time. | |
Laura Keen | I have no additions or edits at this time. | |
Sylvie Duchateau | I have no additions or edits at this time. | |
Howard Kramer | I have no additions or edits at this time. | |
Brent Bakken | I have no additions or edits at this time. | I have not had a chance to review thoroughly, but will do so in the next week. |
Norah Sinclair | I have sent comments to wai-eo-editors@w3.org or added them to the comment field below. | I like the style guide very much. It is one of the most to the point and helpful such guides I have seen. One suggestion: email is becoming more the standard than e-mail: http://grammarist.com/style/e-mail-email/ |
James Green | I have sent comments to wai-eo-editors@w3.org or added them to the comment field below. | [I feel strongly about the following] I think the style guide needs to add strong preference for brevity and use of bullets over paragraphs along with adding some visual content as appropriate. This needs to be mentioned specifically in a new section so editors are clear that their primary job is to try to cut half of the sentences and half of the words while adding some visual content to create visual anchors and break things up more. (Remember the 3 issues this project is tackling are the out-of-date visual design, findability, and the **wall-of-text effect**.) The style guide itself, much like many of our resources, tends to try to explain things with many examples, leading to long, wordy, complex, rambling, unnecessarily verbose sentences. From the style guide: "From Technical Reports and Publications to How-To guides for implementation to documents that help human beings make sense of complex technical specifications, the tone of the presentations may vary considerably. In general WAI documents will have a tone that is welcoming, encouraging, and even inspiring around web accessibility. Materials should educate people without patronizing or confusing them and should be as plain spoken, jargon-free, and straight forward as possible." I applaud the obvious goal of comprehensiveness and clarity, but each of those sentences has a set of 3 comma separated examples. The last sentence has a second set of 3 things for a reader to parse. Less is more when writing for the web. As an example of what I think the style guide needs to communicate about the editing tasks ahead of us, I would rewrite the section to say "Given the various types of documents, tone may vary; however in general, WAI documents will have a tone that is welcoming, encouraging, and inspiring. Materials should be straight-forward, and educate without patronizing, using plain language with a reading level on average of 10th grade." and even use that rewrite as an example of what we want people to do. If we can pull maybe 5 sentences from existing resource and do that to them and include that in the new section, it would help a lot. |
Shawn Lawton Henry | I have no additions or edits at this time. | Happy for it to be a "living resource" that addresses issues as they come up -- and it not clutter it with unnecessary info (now or later). |
Robert Jolly | I have no additions or edits at this time. | |
Kris Anne Kinney | I have no additions or edits at this time. | |
Sharron Rush | I have sent comments to wai-eo-editors@w3.org or added them to the comment field below. | |
Denis Boudreau | I have sent comments to wai-eo-editors@w3.org or added them to the comment field below. | Add something on passive vs active voice as mentioned on the call. Some resource: https://owl.english.purdue.edu/owl/resource/539/02/. |
Shadi Abou-Zahra | I have no additions or edits at this time. | See minutes for some comments on the version at the time. |
Feel free to put here things such as:
(Note that the results of this survey are available publicly, so what you put here can be seen by all. :)
Work for upcoming EOWG teleconferences: If you have upcoming work, please describe what you want to bring to the group in the comment field below. Send any draft material to team-eo-plan@w3.org by Tuesday if possible.
Please plan to join the EO-Planning meeting to prepare for Friday EOWG meeting:
Thursday - 8am CT / 9am ET / 3pm CET
WebEx Link or Audio connection: +1-617-324-0000 US Toll Number, Meeting number: 314 241 816 Passcode: (same as main EOWG teleconference)
Responder | Other Information to Share |
---|---|
Eric Eggert | |
Vivienne Conway | |
Amanda Mace | |
Laura Keen | I'm also willing to help migrate content or pick up front end development work. |
Sylvie Duchateau | |
Howard Kramer | |
Brent Bakken | |
Norah Sinclair | |
James Green | I'm on PTO this week so i'm not attending meetings but I'm tracking along with minutes and surveys. |
Shawn Lawton Henry | getting charter through hoops to AC Review! |
Robert Jolly | I worked on updates to Policies (review, edit, and commit changes in GitHub). Additional updates to Policies will be made this week (today and tomorrow) and then looking forward to additional team members to help with editing and reviewing the policies resource. |
Kris Anne Kinney | |
Sharron Rush | |
Denis Boudreau | |
Shadi Abou-Zahra |
Everybody has responded to this questionnaire.
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
.