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 2016-11-04 to 2016-11-09.
10 answers have been received.
Jump to results for question:
summary | by responder | by choice
Please read the 4 November 2016 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 2016 Minutes wiki page.
Choice | All responders |
---|---|
Results | |
I was in the teleconference and I'm OK with them! | 8 |
I have reviewed the minutes and agree to the Resolutions passed. | 1 |
I have reviewed the minutes but have concerns with the Resolutions, and I explain them below. | 1 |
I have not read the minutes yet, and have put the date for my review into the comments box. |
Skip to view by choice.
Responder | Resolutions of 4 November 2016 | Comments |
---|---|---|
James Green |
|
|
Shawn Lawton Henry |
|
+1 to publishing the Planning and Managing pages +1 to Easy Checks - one check. From the minutes: "RESOLUTION: The Easy Checks will be published (no longer a draft) with the addition of the Moving, Flashing or Blinking check as one check." ... "Caleb: We have some work to do on illustrations and then will be ready to go." I thought we were just agreeing to this one check this week and the final publication approval would come later, after the illustration work and any other clean up was done. *However*, I think all that is very minor and probably doesn't change the content much at all -- so EOWG really doesn't need to review it (and probably doesn't want to :). Therefore, I'm fine with the resolution to publish when other cleanup is done - yet I'm thinking it would be good to do an fyi e-mail to EOWG when it's all done and before it goes out -- not a "we're waiting for replies before publishing" (since got approval in this telecon and people had chance to review in this survey) but a "speak up if any concerns" (since some minor things will have changed). |
Shadi Abou-Zahra |
|
|
Kris Anne Kinney |
|
|
Laura Keen |
|
|
Robert Jolly |
|
|
Caleb Watson |
|
|
Sharron Rush |
|
|
Brent Bakken |
|
|
Andrew Arch |
|
Choice | Responders |
---|---|
I was in the teleconference and I'm OK with them! |
|
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
Please skim the Carousels tutorial overall to re-familiarize yourself with how the topics are presented.
Note that some sections are still in an editor’s draft and will change. Where applicable, considerations and issues on GitHub are mentioned.
If you have any comments, please submit them to this Pull Request (preferred) or in the comments box below.
For comparison, here are all pages from the carousels tutorial, the previous versions and an version highlighting differences:
Choice | All responders |
---|---|
Results | |
I have looked at it, and I have the following comments. | 6 |
I have looked at it, and I have no comments. | 2 |
I didn’t get to it by the closing date of the survey but promise to be prepared for the F2F. :-) |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | Carousels Tutorial Review | Comments |
---|---|---|
James Green | ||
Shawn Lawton Henry | I am focusing my time on the other topics for the F2F. | |
Shadi Abou-Zahra |
|
Provided some suggestions in GitHub |
Kris Anne Kinney |
|
Carousel Concepts - under Why is it important? 2nd Paragraph, functionality spelled incorrectly - and i think they're trying to use the word functionality. I don't like the structure of the Functionality page, very code heavy - prefer the idea of a carousel styling page to break it up into 2 pages. |
Laura Keen |
|
I've added my comments to github. |
Robert Jolly |
|
|
Caleb Watson |
|
Very clear and well done! |
Sharron Rush |
|
|
Brent Bakken |
|
Added comments to the pull request. |
Andrew Arch |
|
on https://w3c.github.io/wai-tutorials/carousels/animations/ the play/stop button should be visible so that visual users distracted by movement can toggle |
Choice | Responders |
---|---|
I have looked at it, and I have the following comments. |
|
I have looked at it, and I have no comments. |
|
I didn’t get to it by the closing date of the survey but promise to be prepared for the F2F. :-) |
summary | by responder | by choice
Please skim the Page Structure tutorial overall to re-familiarize yourself with how the topics are presented.
Note that some sections are still in an editor’s draft and will change. Where applicable, considerations and issues on GitHub are mentioned.
If you have any comments, please submit them to this Pull Request (preferred) or in the comments box below.
For comparison, here are all pages from the page structure tutorial, the previous versions and an version highlighting differences:
Choice | All responders |
---|---|
Results | |
I have looked at it, and I have the following comments. | 8 |
I have looked at it, and I have no comments. | 1 |
I didn’t get to it by the closing date of the survey but promise to be prepared for the F2F. :-) |
(1 response didn't contain an answer to this question)
Skip to view by choice.
Responder | Page Structure Tutorial Review | Comments |
---|---|---|
James Green |
|
content looks good, I would add an image - something along the lines of https://www.paciellogroup.com/wp-content/uploads/2011/07/rotor.gif or http://accessibleculture.org/research-files/ozewai2011/images/html5AriaTestCase.png |
Shawn Lawton Henry | I am focusing my time on the other topics for the F2F. | |
Shadi Abou-Zahra |
|
Sent some thoughts to Eric |
Kris Anne Kinney |
|
Page Structure opening page - why is it important - cognitive is spelled wrong. Agree with editor notes that are marked. |
Laura Keen |
|
I've added comments to github. |
Robert Jolly |
|
|
Caleb Watson |
|
I think you should leave the role=search in this Page Regions since it is such a common component of websites and apps (and it usually persists across layouts). |
Sharron Rush |
|
in GitHUb |
Brent Bakken |
|
Added comments to pull request. The structure of this tutorial looks good as well. Understand that more content is coming later. |
Andrew Arch |
|
agree with idea of moving " HTML5 algorithm" note out of main content on Headings page Good stuff on Styling page Overall - looking like a great resource |
Choice | Responders |
---|---|
I have looked at it, and I have the following comments. |
|
I have looked at it, and I have no comments. |
|
I didn’t get to it by the closing date of the survey but promise to be prepared for the F2F. :-) |
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)
Choice | All responders |
---|---|
Results | |
yes | |
no | 8 |
(2 responses didn't contain an answer to this question)
Responder | Resource Managers: Do you want to bring anything to the next Thursday Planning or Friday EOWG meeting? | Comments |
---|---|---|
James Green | no | |
Shawn Lawton Henry | no | |
Shadi Abou-Zahra | no | |
Kris Anne Kinney | no | |
Laura Keen | no | |
Robert Jolly | ||
Caleb Watson | no | |
Sharron Rush | no | |
Brent Bakken | no | |
Andrew Arch |
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
.