w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire EOWG Review & Publication Approval – Carousel Tutorial
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,ee+eowgsurvey@w3.org
This questionnaire was open from 2017-01-10 to 2017-01-17.
11 answers have been received.
Jump to results for question:
- About this survey
- Carousel Concepts
- Structure Page
- Functionality Page
- Carousel Animations
- Carousel Styling
- Working Example
- Complete Code
1. About this survey
This survey form collects responses to the EOWG review and publication approval of Carousel Tutorial
For comparison, here are all pages from the carousels tutorial, the previous versions and a version highlighting differences:
- Carousel Concepts: Proposal | Previous version | Differences
- Structure: Proposal | Previous version | Differences
- Functionality: Proposal | Previous version | Differences
- Animations: Proposal | Previous version | Differences
- Styling: Proposal | No Previous version | No Differences
- Working Example: Proposal | No Previous version | No Differences
- Complete Code: Proposal | Previous version Differences
For each page below, there is a summary of "What changed".
Details
| Responder | Overall comments |
|---|---|
| Adina Halter | |
| James Green | |
| Laura Keen | |
| Andrew Arch | |
| Shadi Abou-Zahra | This is really great work! The styling page now contains really useful information and it rounds the rest of the pages very nicely. I have a few light edits and comments here and there, which I put in GitHub. In addition, I think that an overall copy-edit pass would be important to firm up the language (also grammatically in some areas). |
| Sylvie Duchateau | |
| Caleb Watson | |
| Sharron Rush | Excellent progress overall. Good work, Eric! |
| Kris Anne Kinney | I'm happy to see the pages were simplified. I think they are much clearer and straight forward. |
| Robert Jolly | |
| Brent Bakken |
2. Carousel Concepts
summary | by responder | by choice
What changed: Improved clarity, added pointers to new pages.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I support the changes and publishing the “Carousel Concepts” page as is | 5 |
| I support the changes and publishing the “Carousel Concepts” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). | 6 |
| I support the changes and publishing the “Carousel Concepts” page only with the comments provided as GitHub issues or in the comments section below | |
| I do not support publishing the “Carousel Concepts” page because of the comments provided as GitHub issues or in the comments section below |
Skip to view by choice.
View by responder
Details
| Responder | Carousel Concepts | Comments |
|---|---|---|
| Adina Halter |
|
Coming in late to this I want to say: 1) I love this. 2) The one difference I would suggest is that when I request a next or previous panel using the arrow buttons I then go to the panel I just requested. |
| James Green |
|
|
| Laura Keen |
|
|
| Andrew Arch |
|
https://github.com/w3c/wai-tutorials/issues/389 |
| Shadi Abou-Zahra |
|
|
| Sylvie Duchateau |
|
|
| Caleb Watson |
|
|
| Sharron Rush |
|
|
| Kris Anne Kinney |
|
The heading What are the key points? isn't sitting right with me to describe what is being outlined in that section. But I'm hitting a mental block on something better. But |
| Robert Jolly |
|
|
| Brent Bakken |
|
View by choice
| Choice | Responders |
|---|---|
| I support the changes and publishing the “Carousel Concepts” page as is |
|
| I support the changes and publishing the “Carousel Concepts” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). |
|
| I support the changes and publishing the “Carousel Concepts” page only with the comments provided as GitHub issues or in the comments section below | |
| I do not support publishing the “Carousel Concepts” page because of the comments provided as GitHub issues or in the comments section below |
3. Structure Page
summary | by responder | by choice
What changed: Improved clarity, added better structure. Moved styling to separate page.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I support the changes and publishing the “Carousel Structure” page as is | 6 |
| I support the changes and publishing the “Carousel Structure” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). | 3 |
| I support the changes and publishing the “Carousel Structure” page only with the comments provided as GitHub issues or in the comments section below | 1 |
| I do not support publishing the “Carousel Structure” page because of the comments provided as GitHub issues or in the comments section below |
(1 response didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | Structure Page | Comments |
|---|---|---|
| Adina Halter | ||
| James Green |
|
|
| Laura Keen |
|
|
| Andrew Arch |
|
|
| Shadi Abou-Zahra |
|
|
| Sylvie Duchateau |
|
This new version is much clearer. Good to have separated styling. |
| Caleb Watson |
|
|
| Sharron Rush |
|
|
| Kris Anne Kinney |
|
|
| Robert Jolly |
|
|
| Brent Bakken |
|
Added comments to GitHub. |
View by choice
| Choice | Responders |
|---|---|
| I support the changes and publishing the “Carousel Structure” page as is |
|
| I support the changes and publishing the “Carousel Structure” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). |
|
| I support the changes and publishing the “Carousel Structure” page only with the comments provided as GitHub issues or in the comments section below |
|
| I do not support publishing the “Carousel Structure” page because of the comments provided as GitHub issues or in the comments section below |
4. Functionality Page
summary | by responder | by choice
What changed: Improved clarity and overall structure of the page. Added links to ARIA documentation. Removed superfluous code examples.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I support the changes and publishing the “Carousel Functionality” page as is | 4 |
| I support the changes and publishing the “Carousel Functionality” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). | 5 |
| I support the changes and publishing the “Carousel Functionality” page only with the comments provided as GitHub issues or in the comments section below | 1 |
| I do not support publishing the “Carousel Functionality” page because of the comments provided as GitHub issues or in the comments section below |
(1 response didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | Functionality Page | Comments |
|---|---|---|
| Adina Halter | ||
| James Green |
|
|
| Laura Keen |
|
|
| Andrew Arch |
|
edits suggested for editor's discretion via Github |
| Shadi Abou-Zahra |
|
|
| Sylvie Duchateau |
|
In section "Indicate items and provide access", in the example, it is not clear to me if selecting a button should work or not, or if the example only shows that button 1 is selected. I tried to select button 2 but nothing happens. Is it normal? If yes, may be add a note indicating that for the demo button selection is not working. |
| Caleb Watson |
|
|
| Sharron Rush |
|
|
| Kris Anne Kinney |
|
|
| Robert Jolly |
|
|
| Brent Bakken |
|
Edits in GitHub. |
View by choice
| Choice | Responders |
|---|---|
| I support the changes and publishing the “Carousel Functionality” page as is |
|
| I support the changes and publishing the “Carousel Functionality” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). |
|
| I support the changes and publishing the “Carousel Functionality” page only with the comments provided as GitHub issues or in the comments section below |
|
| I do not support publishing the “Carousel Functionality” page because of the comments provided as GitHub issues or in the comments section below |
5. Carousel Animations
summary | by responder | by choice
What changed: Better tailored to accessibility, moved styling information to a separate page. Clearer language.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I support the changes and publishing the “Carousel Animations” page as is | 5 |
| I support the changes and publishing the “Carousel Animations” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). | 4 |
| I support the changes and publishing the “Carousel Animations” page only with the comments provided as GitHub issues or in the comments section below | 1 |
| I do not support publishing the “Carousel Animations” page because of the comments provided as GitHub issues or in the comments section below |
(1 response didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | Carousel Animations | Comments |
|---|---|---|
| Adina Halter | ||
| James Green |
|
|
| Laura Keen |
|
|
| Andrew Arch |
|
just wonder if the 'animation' page - with "play/stop" - should appear before the functionality page? |
| Shadi Abou-Zahra |
|
|
| Sylvie Duchateau |
|
|
| Caleb Watson |
|
|
| Sharron Rush |
|
|
| Kris Anne Kinney |
|
|
| Robert Jolly |
|
|
| Brent Bakken |
|
Edits in GitHub. |
View by choice
| Choice | Responders |
|---|---|
| I support the changes and publishing the “Carousel Animations” page as is |
|
| I support the changes and publishing the “Carousel Animations” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). |
|
| I support the changes and publishing the “Carousel Animations” page only with the comments provided as GitHub issues or in the comments section below |
|
| I do not support publishing the “Carousel Animations” page because of the comments provided as GitHub issues or in the comments section below |
6. Carousel Styling
summary | by responder | by choice
What changed: Added this page with general information on styling in regard to the carousel.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I support the changes and publishing the “Carousel Styling” page as is | 7 |
| I support the changes and publishing the “Carousel Styling” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). | 2 |
| I support the changes and publishing the “Carousel Styling” page only with the comments provided as GitHub issues or in the comments section below | 1 |
| I do not support publishing the “Carousel Styling” page because of the comments provided as GitHub issues or in the comments section below |
(1 response didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | Carousel Styling | Comments |
|---|---|---|
| Adina Halter | ||
| James Green |
|
|
| Laura Keen |
|
|
| Andrew Arch |
|
minor editorial suggestion via github |
| Shadi Abou-Zahra |
|
I think this one still needs some more work and possibly also some copy-editing to make it shine like the others. |
| Sylvie Duchateau |
|
|
| Caleb Watson |
|
|
| Sharron Rush |
|
|
| Kris Anne Kinney |
|
|
| Robert Jolly |
|
|
| Brent Bakken |
|
Added comments to GitHub. |
View by choice
| Choice | Responders |
|---|---|
| I support the changes and publishing the “Carousel Styling” page as is |
|
| I support the changes and publishing the “Carousel Styling” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). |
|
| I support the changes and publishing the “Carousel Styling” page only with the comments provided as GitHub issues or in the comments section below |
|
| I do not support publishing the “Carousel Styling” page because of the comments provided as GitHub issues or in the comments section below |
7. Working Example
summary | by responder | by choice
What changed: Added this page with the complete working example.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I support the changes and publishing the “Working Example” page as is | 8 |
| I support the changes and publishing the “Working Example” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). | 2 |
| I support the changes and publishing the “Working Example” page only with the comments provided as GitHub issues or in the comments section below | |
| I do not support publishing the “Working Example” page because of the comments provided as GitHub issues or in the comments section below |
(1 response didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | Working Example | Comments |
|---|---|---|
| Adina Halter | ||
| James Green |
|
|
| Laura Keen |
|
|
| Andrew Arch |
|
|
| Shadi Abou-Zahra |
|
|
| Sylvie Duchateau |
|
My comment is not from an accessibility but from a suability perspective. When coming on the carroussel with a screen reader, you can see the news moving. I do not how to stop this movement, may be it only works when moving focus on it with the tab key? What is also confusing, is the location of the stop/start button, because you first read the previous and next buttons, then the stop button and at last the different buttons to select the news. From a usability point of view, it would be easier to have the stop/start button as first control, may be at the beginning of the carroussel. At editor's discretion. |
| Caleb Watson |
|
|
| Sharron Rush |
|
yep, nicely done! |
| Kris Anne Kinney |
|
|
| Robert Jolly |
|
|
| Brent Bakken |
|
Okay with it for now, but would like to see a change in the content of the example in the future. See comment in GitHub. |
View by choice
| Choice | Responders |
|---|---|
| I support the changes and publishing the “Working Example” page as is |
|
| I support the changes and publishing the “Working Example” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). |
|
| I support the changes and publishing the “Working Example” page only with the comments provided as GitHub issues or in the comments section below | |
| I do not support publishing the “Working Example” page because of the comments provided as GitHub issues or in the comments section below |
8. Complete Code
summary | by responder | by choice
What changed: Reflect changes in the tutorial.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I support the changes and publishing the “Complete Code” page as is | 10 |
| I support the changes and publishing the “Complete Code” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). | |
| I support the changes and publishing the “Complete Code” page only with the comments provided as GitHub issues or in the comments section below | |
| I do not support publishing the “Complete Code” page because of the comments provided as GitHub issues or in the comments section below |
(1 response didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | Complete Code | Comments |
|---|---|---|
| Adina Halter | ||
| James Green |
|
|
| Laura Keen |
|
|
| Andrew Arch |
|
|
| Shadi Abou-Zahra |
|
|
| Sylvie Duchateau |
|
|
| Caleb Watson |
|
|
| Sharron Rush |
|
|
| Kris Anne Kinney |
|
|
| Robert Jolly |
|
|
| Brent Bakken |
|
Not a developer. Hard for me to find anything wrong with the code. |
View by choice
| Choice | Responders |
|---|---|
| I support the changes and publishing the “Complete Code” page as is |
|
| I support the changes and publishing the “Complete Code” page; however, I suggest the comments provided as GitHub issues or in the comments section below (for editors’ discretion). | |
| I support the changes and publishing the “Complete Code” page only with the comments provided as GitHub issues or in the comments section below | |
| I do not support publishing the “Complete Code” page because of the comments provided as GitHub issues or in the comments section below |
More details on responses
- Adina Halter: last responded on 11, January 2017 at 15:53 (UTC)
- James Green: last responded on 11, January 2017 at 19:46 (UTC)
- Laura Keen: last responded on 11, January 2017 at 20:29 (UTC)
- Andrew Arch: last responded on 16, January 2017 at 02:08 (UTC)
- Shadi Abou-Zahra: last responded on 16, January 2017 at 18:00 (UTC)
- Sylvie Duchateau: last responded on 17, January 2017 at 10:46 (UTC)
- Caleb Watson: last responded on 17, January 2017 at 16:00 (UTC)
- Sharron Rush: last responded on 17, January 2017 at 21:14 (UTC)
- Kris Anne Kinney: last responded on 17, January 2017 at 21:20 (UTC)
- Robert Jolly: last responded on 17, January 2017 at 23:14 (UTC)
- Brent Bakken: last responded on 17, January 2017 at 23:34 (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
- Vicki Menezes Miller
- Reinaldo Ferraz
- Bill Kasdorf
- Cristina Mussinelli
- Kevin White
- Kevin Rydberg
- Ahmath Bamba MBACKE
- Denis Boudreau
- 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