w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire EOWG Weekly Survey - 14 April 2017
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 2017-04-13 to 2017-04-21.
11 answers have been received.
Jump to results for question:
- Resolutions of 14 April 2017
- Next Charter Deliverables - Remove or Add?
- Next Charter Deliverables - Order
- Policies Relating to Web Accessibility - Introduction
- Policies Relating to Web Accessibility - Country Data
- Updated ARIA Introduction for Developers
- Updated Tutorial Outline on Accessible Media
- Updated Mobile Intro for Developers
- EOWG 19 & 20 May Face-to-Face (AccessU)
- EOWG November Face-to-Face Date Preference (TPAC)
1. Resolutions of 14 April 2017
summary | by responder | by choice
Please read the 14 April 2017 EOWG teleconference meeting minutes. Indicate your approval or concerns with the resolution(s) passed at that meeting. The summary and the link to the full minutes is on the 2017 Minutes wiki page.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I was in the teleconference and I don't have any comments on the Resolutions or minutes. | 8 |
| I have reviewed the minutes and agree to the Resolutions passed. | 2 |
| I have reviewed the minutes but have concerns with the 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.
View by responder
Details
| Responder | Resolutions of 14 April 2017 | Comments |
|---|---|---|
| Sylvie Duchateau |
|
|
| Brent Bakken |
|
|
| Shawn Lawton Henry |
|
|
| Howard Kramer |
|
|
| Sharron Rush |
|
|
| Denis Boudreau |
|
|
| Robert Jolly |
|
|
| Kris Anne Kinney |
|
|
| Norah Sinclair |
|
|
| Adina Halter | ||
| Shadi Abou-Zahra |
|
View by choice
| 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 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. |
2. Next Charter Deliverables - Remove or Add?
summary | by responder | by choice
2017 Charter Work is a list of potential deliverables for EOWG in the next charter period starting September 2017. 14 April minutes includes some input.
- Do we want to do everything that's listed (or do we want to delete something from this work list)?
- Is there anything else we want to do that's not listed?
Summary
| Choice | All responders |
|---|---|
| Results | |
| I added comments below. (or in the 14 April teleconference) | 2 |
| I'm OK with what's there. | 9 |
Skip to view by choice.
View by responder
Details
| Responder | Next Charter Deliverables - Remove or Add? | Comments |
|---|---|---|
| Sylvie Duchateau |
|
|
| Brent Bakken |
|
|
| Shawn Lawton Henry |
|
|
| Howard Kramer |
|
|
| Sharron Rush |
|
I need more time for review, will comment by Monday April 24 |
| Denis Boudreau |
|
I don't know how it was captured that we would get "Tips Getting Started: Procuring, Managing, Directing, Evaluating" completed before the 2017 charter, but that's just not going to happen. :/ Robert and I are currently working on the planning topic, which we will break down in two parts, but that's all we think we can get in (as a draft to review) before the end of the current charter. Judy also wants to work on some other tips for Procurement and maybe Policy, based on a recent discussion with her. |
| Robert Jolly |
|
|
| Kris Anne Kinney |
|
|
| Norah Sinclair |
|
|
| Adina Halter |
|
|
| Shadi Abou-Zahra |
|
View by choice
| Choice | Responders |
|---|---|
| I added comments below. (or in the 14 April teleconference) |
|
| I'm OK with what's there. |
|
3. Next Charter Deliverables - Order
summary | by responder | by choice
In 2017 Charter Work there is an initial order that we might approach the work. We will refine this throughout the charter period based on current priorities, editor availability, etc. 14 April minutes includes some input.
Although we continually do smaller outreach tasks and efforts, in this new charter we would like to also focus on a big Outreach push of our new fresh WAI web site and updated resources. It makes good sense for us to complete some of our proposed deliverables before this big outreach push. Currently in the list you will see some deliverables prioritized before (listed above) the Outreach, while others are prioritized after (listed below) the Outreach.
- What needs to be done before outreach push?
- Any strong opinions on things that should move way up or way down in the order?
Summary
| Choice | All responders |
|---|---|
| Results | |
| I added comments below. (or in the 14 April teleconference) | 3 |
| I'm OK with order in general. (knowing that we will refine it as we go) | 9 |
Skip to view by choice.
View by responder
Details
| Responder | Next Charter Deliverables - Order | Comments |
|---|---|---|
| Sylvie Duchateau |
|
|
| Brent Bakken |
|
Out of this following list: * Mobile * Older Users * Better Web Browsing * Business Case * Selecting Authoring Tools * Selecting Eval Tools * Eval Resources I would like to know if any of these are close enough to be reworked, redone, or retired in a short enough time that they could be moved above the Outreach push. Some may take more time and I understand they should be scheduled after the outreach push. Any that could be done in a reasonably quick amount of time, it would be nice to complete them and include them in the new WAI design before the outreach push starts. I just do not know the estimated effort on these. |
| Shawn Lawton Henry |
|
I support getting the new design in place asap. I am aware of how long it will likely take to update all the resources that we want to update. I would prefer not to wait to do any significant outreach until after we have all resources updated. I wonder if a phased approach would work? For example, instead of revising all documents before doing any outreach, what about batching things by topic -- updating resources for Topic 1, then outreach on Topic 1; updating resources on Topic 2, then outreach on Topic 2, etc. ? We can prioritize based on the work needed to update the resources and the timeliness of the topic. Maybe mobile accessibility is near the top, whereas updating those eval resources may be near the bottom? |
| Howard Kramer |
|
|
| Sharron Rush |
|
|
| Denis Boudreau |
|
I'd like the work on role-based accessibility to be added to the next charter. I still have to come up with the project scope definition, but I haven't gotten to it yet. |
| Robert Jolly |
|
|
| Kris Anne Kinney |
|
|
| Norah Sinclair |
|
|
| Adina Halter |
|
I'd like to consider putting "How PWDs use Web" before outreach. It will be able to create empathy and impact that will propel people to go deeper into our content. |
| Shadi Abou-Zahra |
|
View by choice
| Choice | Responders |
|---|---|
| I added comments below. (or in the 14 April teleconference) |
|
| I'm OK with order in general. (knowing that we will refine it as we go) |
|
4. Policies Relating to Web Accessibility - Introduction
summary | by responder | by choice
The Policies prototype has gone through a few more revisions. Please review and provide your feedback on the updated Introduction section of the policies prototype page. This section has been condensed based on discussion in the weekly meetings and in GitHub Issue #13.
For each of your comments, please clearly indicate:
- priority: [mild/medium/strong suggestion for editors' discretion]
- current wording:
- suggested revision:
- rationale:
Summary
| Choice | All responders |
|---|---|
| Results | |
| I reviewed the introduction and am OK with the wording. | 4 |
| I reviewed the introduction text and have added suggestions on these changes in GitHub Issue #13 or in the Comments field below | 5 |
| [option of last resort, to be used infrequently] I didn't get to it; I will pass on commenting on it and accept the decisions of the Group. | 1 |
(1 response didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | Policies Relating to Web Accessibility - Introduction | Comments |
|---|---|---|
| Sylvie Duchateau |
|
|
| Brent Bakken |
|
Comment in GitHub issue #13 |
| Shawn Lawton Henry |
|
|
| Howard Kramer |
|
Looks great! |
| Sharron Rush |
|
|
| Denis Boudreau |
|
|
| Robert Jolly |
|
|
| Kris Anne Kinney |
|
|
| Norah Sinclair |
|
|
| Adina Halter |
|
I would mention something about WCAG 2.1 and its upcoming impact |
| Shadi Abou-Zahra |
View by choice
| Choice | Responders |
|---|---|
| I reviewed the introduction and am OK with the wording. |
|
| I reviewed the introduction text and have added suggestions on these changes in GitHub Issue #13 or in the Comments field below |
|
| [option of last resort, to be used infrequently] I didn't get to it; I will pass on commenting on it and accept the decisions of the Group. |
|
5. Policies Relating to Web Accessibility - Country Data
summary | by responder | by choice
The current version of the prototype has all of the countries and their policies listed below the summary table. However, the table is very large and will continue to grow.
Countries also have separate pages with policy details (currently linked to by country name in headings below the summary table).
Recommendation by the Editors is to remove the country data under/after the table, shortening the page and keeping those details on the individual country pages. Editors are seeking feedback. Should country details be listed on the main page and on separate country pages?
Please review the discussion in GitHub Issue #56 and provide feedback in GitHub or in the comments field below.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I reviewed the prototype and GitHub Issue #56 and have added comments in GitHub or in the Comments field below. | 6 |
| I reviewed the prototype and GitHub Issue #56 and have no other comments. | 1 |
| [option of last resort, to be used infrequently] I didn't get to it; I will pass on commenting on it and accept the decisions of the Group. | 2 |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | Policies Relating to Web Accessibility - Country Data | Comments |
|---|---|---|
| Sylvie Duchateau |
|
|
| Brent Bakken |
|
Added Comment in GitHub Issue #56 |
| Shawn Lawton Henry |
|
|
| Howard Kramer |
|
I'm fine with the way it is now. But I can go with the consensus. |
| Sharron Rush |
|
|
| Denis Boudreau |
|
|
| Robert Jolly | ||
| Kris Anne Kinney |
|
|
| Norah Sinclair |
|
|
| Adina Halter |
|
Also, the filter doesn't seem to work. I checked some checkboxes but found no submit button to run the filter. And just checking the checkboxes didn't do anything automatically (although I wouldn't suggest the checkbox auto-update approach anyway because it's an accessibility challenge to know if anything changed or not) |
| Shadi Abou-Zahra |
View by choice
| Choice | Responders |
|---|---|
| I reviewed the prototype and GitHub Issue #56 and have added comments in GitHub or in the Comments field below. |
|
| I reviewed the prototype and GitHub Issue #56 and have no other comments. |
|
| [option of last resort, to be used infrequently] I didn't get to it; I will pass on commenting on it and accept the decisions of the Group. |
|
6. Updated ARIA Introduction for Developers
summary | by responder | by choice
We've updated the approach for the Tutorial Outline: ARIA and Sliders, renaming it to "ARIA Introduction for Developers"; adding details on concepts to introduce; and changing the reference examples from sliders to checkbox.
Please let us know what you think about the updated approach, and whether you have other comments or suggestions.
Please review the discussion in GitHub Issues #469 & #476 and provide feedback in GitHub or in the comments field below.
Select all that apply:
Summary
| Choice | All responders |
|---|---|
| Results | |
| I reviewed the updated tutorial (now a developers' intro) GitHub Issues #469 & #476 and have added comments in GitHub or in the Comments field below. | 2 |
| I'm OK with the new title ("ARIA Introduction for Developers"), or otherwise have made a comment below. | 5 |
| The sequence of ARIA concepts looks OK, or else I've made a comment below. | 3 |
| Building this around one example (checkbox) should work fine, or else I've made suggestions below. | 1 |
Skip to view by choice.
View by responder
Details
| Responder | Updated ARIA Introduction for Developers | Comments |
|---|---|---|
| Sylvie Duchateau | I had no time to review this for now and cannot comment. | |
| Brent Bakken |
|
Added comment to GitHub Issue #476 |
| Shawn Lawton Henry | (haven't gotten to this yet :( | |
| Howard Kramer |
|
|
| Sharron Rush |
|
|
| Denis Boudreau |
|
|
| Robert Jolly |
|
|
| Kris Anne Kinney |
|
Thank you for adding a simplified example (the check box). I think basic examples are important. |
| Norah Sinclair |
|
|
| Adina Halter | You definitely need an ARIA introduction before jumping into aria and sliders. But this could be done by linking from the tutorial to the ARIA introduction. So if someone is familiar with ARIA they can consume the slider pattern. If they don't they can click a link to take them to an ARIA intro to learn more first. | |
| Shadi Abou-Zahra |
View by choice
| Choice | Responders |
|---|---|
| I reviewed the updated tutorial (now a developers' intro) GitHub Issues #469 & #476 and have added comments in GitHub or in the Comments field below. |
|
| I'm OK with the new title ("ARIA Introduction for Developers"), or otherwise have made a comment below. |
|
| The sequence of ARIA concepts looks OK, or else I've made a comment below. |
|
| Building this around one example (checkbox) should work fine, or else I've made suggestions below. |
|
7. Updated Tutorial Outline on Accessible Media
summary | by responder | by choice
We've updated the approach for the Tutorial Outline: Captions, renaming it to "Tutorial on Accessible Media"; expanding detail in the tutorial outline.
Please let us know what you think about the updated approach, and whether you have other comments or suggestions.
Please review the discussion in GitHub Issues #478 & #482 with the label "captions" and provide feedback in GitHub or in the comments field below.
Select all that apply:
Summary
| Choice | All responders |
|---|---|
| Results | |
| I reviewed the updated "Tutorial on Accessible Media" and discussion in GitHub Issues #478 & #482, and have added comments in GitHub or in the Comments field below. | 2 |
| I'm OK with the new title "Tutorial on Accessible Media", or otherwise have made a comment below. | 7 |
| The updated outline and coverage of issues in accessible media look fine, or else I've made a comment below. | 3 |
| I think the scope of this tutorial is appropriate, or else I've made a suggestion below about how to adjust the scope. | 3 |
Skip to view by choice.
View by responder
Details
| Responder | Updated Tutorial Outline on Accessible Media | Comments |
|---|---|---|
| Sylvie Duchateau | Same as previous question. | |
| Brent Bakken |
|
Good overview for this tutorial. Have added issues previously that I would like some feedback on. Also added new GitHub issue #499. |
| Shawn Lawton Henry | (haven't gotten to this yet :( | |
| Howard Kramer |
|
|
| Sharron Rush |
|
|
| Denis Boudreau |
|
|
| Robert Jolly |
|
|
| Kris Anne Kinney |
|
|
| Norah Sinclair |
|
|
| Adina Halter |
|
I wouldn't use "tutorial". I would use "guidelines" I am a web developer so I consider a tutorial something that I would follow along with step by step, following all development steps to create my own version of whatever the tutorial is teaching. Like Lynda.com or something like that. That would be the meaning of a tutorial to me. Also, I would make a clear distinction between the media itself that you are discussing in this page and media players. Have a link on this page to read more about accessible media players. |
| Shadi Abou-Zahra |
View by choice
| Choice | Responders |
|---|---|
| I reviewed the updated "Tutorial on Accessible Media" and discussion in GitHub Issues #478 & #482, and have added comments in GitHub or in the Comments field below. |
|
| I'm OK with the new title "Tutorial on Accessible Media", or otherwise have made a comment below. |
|
| The updated outline and coverage of issues in accessible media look fine, or else I've made a comment below. |
|
| I think the scope of this tutorial is appropriate, or else I've made a suggestion below about how to adjust the scope. |
|
8. Updated Mobile Intro for Developers
summary | by responder | by choice
We've updated the approach for the "Tutorial Outline: Mobile Overview"; renaming it to "Mobile Introduction for Developers"; revising the conceptual introduction; and revising the walk-through of concepts to keep in mind while using existing tutorials.
We've also proposed an approach of inserting mobile examples throughout the existing tutorials.
Please let us know what you think about the updated approach, and whether you have other comments or suggestions.
Please review the discussion in GitHub Issues #475 & #479 with the label "mobile" and provide feedback in GitHub or in the comments field below.
Select all that apply:
Summary
| Choice | All responders |
|---|---|
| Results | |
| I reviewed the updated "Mobile Introduction for Developers" and discussion in GitHub Issues #475 & #479, and have added comments in GitHub or in the Comments field below. | 2 |
| I'm OK with the new title "Mobile Introduction for Developers", or otherwise have made a comment below. | 6 |
| The updated approach of a conceptual page highlighting similarities and differences between mobile and desktop, then a walk-through of how to use the existing tutorial examples with mobile in mind; or otherwise I've made a comment below. | 3 |
| I would support integrating some mobile examples into the existing tutorials, or otherwise have made a comment below. | 4 |
Skip to view by choice.
View by responder
Details
| Responder | Updated Mobile Intro for Developers | Comments |
|---|---|---|
| Sylvie Duchateau | I had no time to review this yet. | |
| Brent Bakken |
|
|
| Shawn Lawton Henry | (haven't gotten to this yet :( | |
| Howard Kramer |
|
|
| Sharron Rush |
|
|
| Denis Boudreau |
|
|
| Robert Jolly |
|
|
| Kris Anne Kinney |
|
|
| Norah Sinclair |
|
|
| Adina Halter |
|
|
| Shadi Abou-Zahra |
View by choice
| Choice | Responders |
|---|---|
| I reviewed the updated "Mobile Introduction for Developers" and discussion in GitHub Issues #475 & #479, and have added comments in GitHub or in the Comments field below. |
|
| I'm OK with the new title "Mobile Introduction for Developers", or otherwise have made a comment below. |
|
| The updated approach of a conceptual page highlighting similarities and differences between mobile and desktop, then a walk-through of how to use the existing tutorial examples with mobile in mind; or otherwise I've made a comment below. |
|
| I would support integrating some mobile examples into the existing tutorials, or otherwise have made a comment below. |
|
9. EOWG 19 & 20 May Face-to-Face (AccessU)
Have you added your Participation Availability for the EOWG 19 & 20 May Face-to-Face Meeting? (If not, please do so now. Thank you!)
Summary
| Choice | All responders |
|---|---|
| Results | |
| yes | 8 |
| no | 3 |
Details
| Responder | EOWG 19 & 20 May Face-to-Face (AccessU) |
|---|---|
| Sylvie Duchateau | yes |
| Brent Bakken | yes |
| Shawn Lawton Henry | yes |
| Howard Kramer | yes |
| Sharron Rush | yes |
| Denis Boudreau | yes |
| Robert Jolly | yes |
| Kris Anne Kinney | no |
| Norah Sinclair | no |
| Adina Halter | no |
| Shadi Abou-Zahra | yes |
10. EOWG November Face-to-Face Date Preference (TPAC)
Have you completed the survey to indicate your Preference for days to meet at TPAC 2017 EOWG F2F ? (If not, please do so now. Thank you!)
Summary
| Choice | All responders |
|---|---|
| Results | |
| yes | 10 |
| no | 1 |
Details
| Responder | EOWG November Face-to-Face Date Preference (TPAC) |
|---|---|
| Sylvie Duchateau | yes |
| Brent Bakken | yes |
| Shawn Lawton Henry | yes |
| Howard Kramer | yes |
| Sharron Rush | yes |
| Denis Boudreau | yes |
| Robert Jolly | yes |
| Kris Anne Kinney | yes |
| Norah Sinclair | yes |
| Adina Halter | no |
| Shadi Abou-Zahra | yes |
More details on responses
- Sylvie Duchateau: last responded on 19, April 2017 at 09:28 (UTC)
- Brent Bakken: last responded on 19, April 2017 at 21:23 (UTC)
- Shawn Lawton Henry: last responded on 19, April 2017 at 22:21 (UTC)
- Howard Kramer: last responded on 20, April 2017 at 05:00 (UTC)
- Sharron Rush: last responded on 20, April 2017 at 14:04 (UTC)
- Denis Boudreau: last responded on 20, April 2017 at 14:45 (UTC)
- Robert Jolly: last responded on 20, April 2017 at 14:47 (UTC)
- Kris Anne Kinney: last responded on 20, April 2017 at 14:54 (UTC)
- Norah Sinclair: last responded on 20, April 2017 at 19:24 (UTC)
- Adina Halter: last responded on 20, April 2017 at 20:56 (UTC)
- Shadi Abou-Zahra: last responded on 21, April 2017 at 13:56 (UTC)
Non-responders
The following persons have not answered the questionnaire:
- Eric Velleman
- Andrew Arch
- Kazuhito Kidachi
- Jedi Lin
- David Sloan
- Mary Jo Mueller
- Vicki Menezes Miller
- Reinaldo Ferraz
- Bill Kasdorf
- Cristina Mussinelli
- Kevin White
- Kevin Rydberg
- Ahmath Bamba MBACKE
- 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
- 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