w3c/wbs-design
or
by mail to sysreq
.
The results of this questionnaire are available to anybody. In addition, answers are sent to the following email addresses: shawn@w3.org,shadi+EOsurvey@w3.org
This questionnaire was open from 2017-03-24 to 2017-04-04.
11 answers have been received.
Jump to results for question:
summary | by responder | by choice
Please read the 24 March 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.
Choice | All responders |
---|---|
Results | |
I was in the teleconference and I don't have any comments on the Resolutions or minutes. | 6 |
I have reviewed the minutes and agree to the Resolutions passed. | 4 |
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.
Responder | Minutes of 24 March 2017 | Comments |
---|---|---|
Sylvie Duchateau |
|
|
Shadi Abou-Zahra |
|
|
Judy Brewer | ||
Laura Keen |
|
|
Kris Anne Kinney |
|
But I couldn't find any resolutions in the summary at the bottom. |
Eric Eggert |
|
|
Sharron Rush |
|
|
Norah Sinclair |
|
|
Sarah Pulis |
|
|
Howard Kramer |
|
I don't see any resolutions listed in the minutes btw. |
Brent Bakken |
|
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. |
summary | by responder | by choice
We have editor resources to develop more Tutorials. Here is a Requirements Analysis doc for the proposed new tutorials:
March 2017 Tutorials Requirements Analysis.
(fyi, here is the previous/old requirements analysis.)
Let us know if you have any comments on the requirements overview, but note that you may need to look at the four linked outlines to clarify what the brief blurbs in the requirements overview mean.
Please put any general comments or questions on the Requirements Analysis as GitHub issues with the label "March_2017_requirements".
(Later questions in this survey ask about the content and outlines of the specific tutorials.)
Choice | All responders |
---|---|
Results | |
Requirements Analysis looks fine, I don't have any comments or questions. | 6 |
I put comments in GitHub issues with the label "March_2017_requirements" (or, I don't use GitHub, so put Comments below) | 2 |
I haven't gotten to this yet, and will by the date in the comments field below: | 1 |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | New Tutorials - Requirements | Comments |
---|---|---|
Sylvie Duchateau |
|
|
Shadi Abou-Zahra | ||
Judy Brewer | ||
Laura Keen |
|
|
Kris Anne Kinney |
|
|
Eric Eggert |
|
End of survey. |
Sharron Rush |
|
|
Norah Sinclair |
|
|
Sarah Pulis |
|
|
Howard Kramer |
|
|
Brent Bakken |
|
Nothing further to add outside of the discussions in planning meeting and the EO Friday call. Really looking to keep the tutorials ask crisp, specific "How To" documents that people feel guided through a specific aspect of making content or applications accessible. Hoping that these don't become broad resources. I think we are on the right track with datepicker and captions. |
Choice | Responders |
---|---|
Requirements Analysis looks fine, I don't have any comments or questions. |
|
I put comments in GitHub issues with the label "March_2017_requirements" (or, I don't use GitHub, so put Comments below) |
|
I haven't gotten to this yet, and will by the date in the comments field below: |
|
summary | by responder | by choice
Here is a draft outline for a new Mobile Overview Tutorial
One question to consider: Do you think that a overview approach might help draw in some audiences that are specifically looking for accessibility resources labeled "mobile"?
Any other comments, questions or concerns?
Please put any comments or questions as GitHub issues with the label "mobile-overview".
Choice | All responders |
---|---|
Results | |
Outline looks fine, I don't have any comments or questions. | 4 |
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) | 5 |
I haven't gotten to this yet, and will by the date in the comments field below: |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | Tutorial Outline - Mobile Overview | Comments |
---|---|---|
Sylvie Duchateau |
|
|
Shadi Abou-Zahra | ||
Judy Brewer | ||
Laura Keen |
|
|
Kris Anne Kinney |
|
|
Eric Eggert |
|
https://github.com/w3c/wai-tutorials/issues/475 |
Sharron Rush |
|
Summary: Mobile Accessibility seems like a very broad topic for a tutorial. Perhaps we should create a Mobile Authoring Guide, similar to the ARIA authoring guide and then take a similar "How to use the Guide" approach in the tutorials. |
Norah Sinclair |
|
Can Tips and Tricks be renamed Tips and Techniques? Should Responsive Design be added as a topic in Concepts of Mobile Accessibility Section? |
Sarah Pulis |
|
General topics such as mobile environment as a continuum between Web and native and why this is important should be reflected in Mobile Accessibility page [https://www.w3.org/WAI/mobile/Overview]. I don't think everything would search for this information in the tutorials. |
Howard Kramer |
|
|
Brent Bakken |
|
I do like some of the key areas of the Mobile outline. Specifically, the introduction to developers unfamiliar with WCAG 2.0, similarities/differences in coding approach for an accessible website vs an accessible app, the Parallel principles of accessibility in the mobile environment section, and the Mobile specific considerations. |
Choice | Responders |
---|---|
Outline looks fine, I don't have any comments or questions. |
|
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) |
|
I haven't gotten to this yet, and will by the date in the comments field below: |
summary | by responder | by choice
Here is a draft outline for a new Tutorial on ARIA Concepts with Sliders Example.
Question to consider: Do you think that it would be useful to have a conceptual intro to ARIA that serves as a bridge to the other tutorial-like resources emerging in the ARIA Authoring Practices document?
Any other comments, questions or concerns?
Please put any comments or questions as GitHub issues with the label "aria-concepts-with-sliders".
Choice | All responders |
---|---|
Results | |
Outline looks fine, I don't have any comments or questions. | 2 |
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) | 7 |
I haven't gotten to this yet, and will by the date in the comments field below: |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | Tutorial Outline - ARIA Concepts | Comments |
---|---|---|
Sylvie Duchateau |
|
If I understand correctly, this tutorial only gives one example: slider. May be it could be useful to explain that this slider is only one example of what can be done with ARIA. Otherwise, people would think that ARIA is only similar to slider. |
Shadi Abou-Zahra | ||
Judy Brewer | ||
Laura Keen |
|
|
Kris Anne Kinney |
|
I managed to put it in Github!!! Hopefully I did it right. LOL |
Eric Eggert |
|
https://github.com/w3c/wai-tutorials/issues/476 |
Sharron Rush |
|
Summary: Maybe what would be most useful is a tutorial on "How to Use the ARIA Authoring Guide" with more than one example of building out components. |
Norah Sinclair |
|
This suggestion applies to each of the tutorials, would suggest removing the word "tricks" from Tips and Tricks and possibly replace with "Techniques" |
Sarah Pulis |
|
I would add section on the importance of testing with different assistive technologies to ensure ARIA widgets works as expected on desktop and mobile. |
Howard Kramer |
|
|
Brent Bakken |
|
Choice | Responders |
---|---|
Outline looks fine, I don't have any comments or questions. |
|
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) |
|
I haven't gotten to this yet, and will by the date in the comments field below: |
summary | by responder | by choice
Here is a draft outline for a new Tutorial on Date Pickers.
Question to consider: Do you think that it would be useful to have a tutorial that serves partly as a gateway to the UI components library, that could be made available once that is ready in the future?
Any other comments, questions or concerns?
Please put any comments or questions as GitHub issues with the label "datepicker".
Choice | All responders |
---|---|
Results | |
Outline looks fine, I don't have any comments or questions. | 3 |
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) | 4 |
I haven't gotten to this yet, and will by the date in the comments field below: | 1 |
(3 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | Tutorial Outline - Date Pickers | Comments |
---|---|---|
Sylvie Duchateau |
|
|
Shadi Abou-Zahra | ||
Judy Brewer | ||
Laura Keen |
|
This page returns a 404. |
Kris Anne Kinney |
|
|
Eric Eggert |
|
https://github.com/w3c/wai-tutorials/issues/477 |
Sharron Rush |
|
same point. if UI components list can be stabilized, use tutorial as How To Use instruction |
Norah Sinclair |
|
|
Sarah Pulis |
|
Reliance on UI Components Library being available. |
Howard Kramer | ||
Brent Bakken |
|
Choice | Responders |
---|---|
Outline looks fine, I don't have any comments or questions. |
|
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) |
|
I haven't gotten to this yet, and will by the date in the comments field below: |
|
summary | by responder | by choice
Here is a draft outline for a new Tutorial on Captions.
Question to consider: Do you have thoughts about what would be the best scope and focus of this tutorial?
Any other comments, questions or concerns?
Please put any comments or questions as GitHub issues with the label "captions".
Choice | All responders |
---|---|
Results | |
Outline looks fine, I don't have any comments or questions. | 2 |
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) | 5 |
I haven't gotten to this yet, and will by the date in the comments field below: | 1 |
(3 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | Tutorial Outline - Captions | Comments |
---|---|---|
Sylvie Duchateau |
|
The link to outline does not work |
Shadi Abou-Zahra | ||
Judy Brewer | Link to outline for this tutorial has been fixed. | |
Laura Keen |
|
This page returns a 404. |
Kris Anne Kinney |
|
Happy Comment - Love this tutorial. I know a lot of people it will help! |
Eric Eggert |
|
https://github.com/w3c/wai-tutorials/issues/478 |
Sharron Rush |
|
+1 to broaden scope to accessible media |
Norah Sinclair |
|
I wonder if the idea behind this statement could be presented in a different way: "when quality may matter a lot" ? I'm thinking someone who cannot access the audio, may have the opinion that quality should matter in all situations. |
Sarah Pulis |
|
|
Howard Kramer | ||
Brent Bakken |
|
Choice | Responders |
---|---|
Outline looks fine, I don't have any comments or questions. |
|
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) |
|
I haven't gotten to this yet, and will by the date in the comments field below: |
|
summary | by responder | by choice
We have editor resources to develop a resource on using the Before and After Demo (BAD) in training, and for starting to update BAD. Here is a Requirements Analysis doc for the proposed new work: BAD Update Requirements Analysis.
Comments at this high level welcome, but this is mainly the context for the next question, on using the BAD Demo as Curriculum.
Please put any comments or questions on the Requirements Analysis as a new issue in the GitHub BAD demo repository.
Choice | All responders |
---|---|
Results | |
Requirements Analysis looks fine, I don't have any comments or questions. | 4 |
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) | 3 |
I haven't gotten to this yet, and will by the date in the comments field below: | 1 |
(3 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | BAD Update and Guidance | Comments |
---|---|---|
Sylvie Duchateau |
|
|
Shadi Abou-Zahra | ||
Judy Brewer | ||
Laura Keen |
|
|
Kris Anne Kinney |
|
|
Eric Eggert |
|
https://github.com/w3c/wai-bad-demo/issues/4 |
Sharron Rush |
|
|
Norah Sinclair |
|
|
Sarah Pulis |
|
3 April 2017 |
Howard Kramer | ||
Brent Bakken |
|
Choice | Responders |
---|---|
Requirements Analysis looks fine, I don't have any comments or questions. |
|
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) |
|
I haven't gotten to this yet, and will by the date in the comments field below: |
|
summary | by responder | by choice
Here is a draft outline on the proposed new resource on Using BAD for Curriculum
Do you have thoughts about what would be the best scope, focus, and format for this material?
Please add any comments or questions to GitHub Issue #1 - BAD_Curric.
Choice | All responders |
---|---|
Results | |
Looks fine, I don't have any comments or questions. | 2 |
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) | 5 |
I haven't gotten to this yet, and will by the date in the comments field below: | 1 |
(3 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | Using BAD for Curriculum - Outline | Comments |
---|---|---|
Sylvie Duchateau |
|
|
Shadi Abou-Zahra | ||
Judy Brewer | ||
Laura Keen |
|
|
Kris Anne Kinney |
|
I +1 to Laura's comment about the Issue of the responsive design site. |
Eric Eggert |
|
https://github.com/w3c/wai-bad-demo/issues/5 |
Sharron Rush |
|
|
Norah Sinclair |
|
I would like to take another look at this after the meeting Friday March 30. Some initial thoughts: A series of guided questions to facilitate exploration could be helpful. Also a video demonstration(s) of user of assistive technology encountering the accessibility barriers and discussing them can be helpful for understanding with second video showing improved access with the more accessible site. |
Sarah Pulis |
|
3 April 2017 |
Howard Kramer | ||
Brent Bakken |
|
Choice | Responders |
---|---|
Looks fine, I don't have any comments or questions. |
|
I put comments as GitHub issues (or, I don't use GitHub, so put Comments below) |
|
I haven't gotten to this yet, and will by the date in the comments field below: |
|
The following persons have not answered the questionnaire:
Send an email to all the non-responders.
Compact view of the results / list of email addresses of the responders
WBS home / Questionnaires / WG questionnaires / Answer this questionnaire
w3c/wbs-design
or
by mail to sysreq
.