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-03-18 to 2016-03-30.
11 answers have been received.
Jump to results for question:
summary | by responder | by choice
Please read the EOWG teleconference meeting minutes. Indicate your approval or concerns with the resolution(s) passed at that meeting.
Choice | All responders |
---|---|
Results | |
I was in the teleconference and I'm OK with them! | 9 |
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. | |
I have not read the minutes yet, and have put the date for my review into the comments box. | 1 |
Skip to view by choice.
Responder | Resolutions | Comments |
---|---|---|
Shadi Abou-Zahra |
|
|
James Green |
|
|
Eric Eggert |
|
|
Brent Bakken |
|
|
Andrew Arch |
|
https://www.w3.org/2016/03/18-eo-minutes.html |
Vicki Menezes Miller |
|
April |
Joy Relton |
|
|
Susan Hewitt |
|
|
Sharron Rush |
|
|
Howard Kramer |
|
|
Shawn Lawton Henry |
|
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
The following changes were made to Planning and Managing Web Accessibility based on feedback from the comprehensive review.Please review the changes and raise any comments in GithHub (or, if you're not comfortable with GitHub, you can put them in the comments here).
Choice | All responders |
---|---|
Results | |
I reviewed and accept the changes and have no comments to add. | 8 |
I reviewed the changes and put my comments in GitHub or below. | 1 |
I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | |
I'm not going to be able to get to this, and I will pass on commenting on it — now and in the future. | 1 |
(1 response didn't contain an answer to this question)
Skip to view by choice.
Responder | Planning and Managing Web Accessibility: Accept Changes | Comments |
---|---|---|
Shadi Abou-Zahra |
|
|
James Green |
|
|
Eric Eggert | ||
Brent Bakken |
|
|
Andrew Arch |
|
Thanks for considering my previous comments :) |
Vicki Menezes Miller |
|
|
Joy Relton |
|
|
Susan Hewitt |
|
|
Sharron Rush |
|
|
Howard Kramer |
|
|
Shawn Lawton Henry |
|
Choice | Responders |
---|---|
I reviewed and accept the changes and have no comments to add. |
|
I reviewed the changes and put my comments in GitHub or below. |
|
I have not gotten to this yet, and will do it by: [put in the Comment field the date by which you will get to it] | |
I'm not going to be able to get to this, and I will pass on commenting on it — now and in the future. |
|
summary | by responder | by choice
During the approval to publish phase, a suggestion was made to add a button to expand/collapse all techniques sections in the document. Take a look at the following four pages with the button on different locations and indicate your favorite below:
https://w3c.github.io/wai-wcag-quickref/button-1.html
https://w3c.github.io/wai-wcag-quickref/button-2.html
https://w3c.github.io/wai-wcag-quickref/button-3.html (Disregard the gray background)
https://w3c.github.io/wai-wcag-quickref/button-4.html (Disregard the gray background)
https://w3c.github.io/wai-wcag-quickref/button-5.html
Choice | All responders |
---|---|
Results | |
I like location 1 best. | 1 |
I like location 2 best. | 1 |
I like location 3 best. | |
I like location 4 best. | 3 |
I like location 5 best. | 5 |
I don’t like any of the options, but I have an idea for a better location (add to comments). | |
I don’t like any of the options, but I don’t have a better idea. |
(1 response didn't contain an answer to this question)
Skip to view by choice.
Responder | How to Meet WCAG 2.0 [Quickref]: Expand/Collapse all techniques | Comments |
---|---|---|
Shadi Abou-Zahra |
|
I also like 5 and 3 (in that order). Both 3, 4, and 5 put the button in the active area of the page, which is where I would tend to look first. I'm not sure which order I like most, though. 4 seems clearest as the expand button is slightly different functionality than "clear filters" and "share this view". Note the issue with expand vs show below, too. Option 1 works for me too, but it adds slightly more vertical space (not really an issue, though). I could not even find the button in option 2, and it disappears when the filtering tab is selected, which is probably when it is most needed. I do not feel comfortable with this option at all. New related issue: I just realized that messages like "showing all techniques" or "showing techniques for technologies HTML" collide with the wording of "expand all techniques" - think the difference between "showing what is filtered" and "expand from what is shown" might be too subtle for the general public to understand. I think we need to change the word "showing" to something else but don't have a better idea at the moment. Unfortunately I think this is a big issue. |
James Green |
|
|
Eric Eggert | ||
Brent Bakken |
|
In my opinion location 5 is the most intuitive. I do not like the ones that disappear when you scroll or change to a different tab. |
Andrew Arch |
|
|
Vicki Menezes Miller |
|
|
Joy Relton |
|
|
Susan Hewitt |
|
|
Sharron Rush |
|
|
Howard Kramer |
|
Could also go with 2 or 3. Don't like 1 or 2. Seems strange that yellow band has text that says: Showing all success criteria and all techniques. But then you have a button that says "expand all techniques." Seems a contradiction. |
Shawn Lawton Henry |
|
Here's another vote for 5: <https://lists.w3.org/Archives/Public/wai-eo-editors/2016Mar/0055.html> I think it would be good to re-think Showing... and Show/Hide and Expand/Collapse. Right now it's not consistent or clear -- e.g., "Showing..." relates to filters whereas "Show techniques and failures for 1.1" is expand/collapse; and "Show techniques and failures for 1.1" and "Expand all techniques" do the same thing, but are worded differently. Also, that button doesn't expand *all* techniques if some are filtered out. Perhaps "Showing xyz success criteria and xyz techniques." becomes "Listed: xyz success criteria and xyz techniques."? Then the new button could better match the others: "Show techniques" or "Show techniques below" or "Show all listed techniques". If we want to keep the new button "Expand techniques" or "Expand techniques below" or "Expand listed techniques" -- then I think we ought to change the buttons below that do the same thing from "Show/Hide" to "Expand/Collapse" Since we're considering adding this new button around 5, I'd like to ask if "Share this view" can be shortened to just "Share"? We could put more in the pop-up, e.g., "Link to this view:"-> "Link to this view with the filters you have selected" or such... |
Choice | Responders |
---|---|
I like location 1 best. |
|
I like location 2 best. |
|
I like location 3 best. | |
I like location 4 best. |
|
I like location 5 best. |
|
I don’t like any of the options, but I have an idea for a better location (add to comments). | |
I don’t like any of the options, but I don’t have a better idea. |
The latest discussion and proposal for the start title and end title content for all videos is outlined in Start/title and ending screens Issue #108.
The proposal is also outlined below.
Choice | All responders |
---|---|
Results | |
I think the "title of specific video" should be included in all videos. (Please provide comment in the rationale field) | 6 |
I think the "title of specific video" should *NOT* be included in all videos. (Please provide comment in the rationale field) | |
I have no preference and will support the overall decision of the working group. | 5 |
Responder | Web Accessibility Perspectives: Video start and end screens | Rationale |
---|---|---|
Shadi Abou-Zahra | I think the "title of specific video" should be included in all videos. (Please provide comment in the rationale field) | I really don't think adding the titles gives away that much, as most stories are not built around revealing a secret. In contrary, I think we want to promote specific concepts with these examples and videos, and want people to walk away remembering these concepts. That is, accessibility is about captions, colors, layout, ... |
James Green | I think the "title of specific video" should be included in all videos. (Please provide comment in the rationale field) | I don't imagine we are going to only put a number in the links to watch the videos, keeping the topics secret.... So, this makes me think of https://www.w3.org/TR/WCAG20-TECHS/G199.html. When users click on a video they should get feedback immediately that they are seeing what they expected to see and not have to spend thought figuring it out... |
Eric Eggert | I have no preference and will support the overall decision of the working group. | |
Brent Bakken | I think the "title of specific video" should be included in all videos. (Please provide comment in the rationale field) | I think setting the stage for the viewer is important. And this may be the only place that this specific video title will be used during the entire video. We need the title somewhere and I would rather it be up front. |
Andrew Arch | I think the "title of specific video" should be included in all videos. (Please provide comment in the rationale field) | To reassure the viewer that they're watching the video they selected or were directed to from elsewhere. |
Vicki Menezes Miller | I have no preference and will support the overall decision of the working group. | |
Joy Relton | I have no preference and will support the overall decision of the working group. | I believe that it is good form to have the title up front so that we can ensure that everyone is on the same page. I.e., the person knows which video they will be watching. |
Susan Hewitt | I think the "title of specific video" should be included in all videos. (Please provide comment in the rationale field) | We can't guarantee users will visit the resource page first (what if they're linked directly to the video from somewhere else?) I think they need to know what it is before they watch it. And, if they do go to the video from the resources page, they've already seen the title so it rather defeats the "suspense" purpose, doesn't it? |
Sharron Rush | I have no preference and will support the overall decision of the working group. | |
Howard Kramer | I think the "title of specific video" should be included in all videos. (Please provide comment in the rationale field) | I guess this goes back to the discussion at the face 2 face where Eric indicated his preference for 2. I think we need to be upfront with the subject of each video. |
Shawn Lawton Henry | I have no preference and will support the overall decision of the working group. | As I've said, this is difficult to decide on without seeing at least a rough cut of the videos. |
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
.