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@w3.org,kevin@w3.org
This questionnaire was open from 2015-07-10 to 2015-07-23.
15 answers have been received.
Jump to results for question:
Tips on Designing for Web Accessibility
Let's do a final poll to help decide which tips to include or not. First, please read the criteria/considerations on which tips to include.
Please rate the whether or not you think each tip should be included in the Designing Tips page, with lowest meaning you think it should not be included. Feel free to add comments in the survey about including tips or not, and on the order of the tips.
If you have comments on the Tips themselves, please put them in GitHub -- either Fork and Edit, or create a new issue.
Choice | All responders | |||||
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | No opinion | |
Provide sufficient contrast between foreground and background | 1 | 1 | 11 | 2 | ||
Don't use color alone to convey information | 1 | 2 | 10 | 2 | ||
Ensure that interactive elements are easy to identify | 1 | 4 | 8 | 2 | ||
Provide clear and consistent navigation options | 3 | 4 | 6 | 2 | ||
Ensure that form elements include clearly associated labels | 1 | 8 | 4 | 2 | ||
Provide clear feedback | 2 | 7 | 4 | 2 | ||
Use spacing and headings to group related content | 1 | 6 | 1 | 5 | 2 | |
Create designs for different viewport sizes | 1 | 2 | 1 | 2 | 6 | 3 |
Provide a text alternative for images | 2 | 6 | 2 | 1 | 2 | 2 |
Provide controls for content that starts automatically | 1 | 1 | 3 | 4 | 3 | 3 |
[Images of Text] - idea in GitHub 73 | 4 | 1 | 4 | 1 | 5 |
Averages:
Choices | All responders: |
---|---|
Value | |
Provide sufficient contrast between foreground and background | 4.62 |
Don't use color alone to convey information | 4.62 |
Ensure that interactive elements are easy to identify | 4.54 |
Provide clear and consistent navigation options | 4.23 |
Ensure that form elements include clearly associated labels | 4.23 |
Provide clear feedback | 4.15 |
Use spacing and headings to group related content | 3.77 |
Create designs for different viewport sizes | 3.83 |
Provide a text alternative for images | 2.62 |
Provide controls for content that starts automatically | 3.58 |
[Images of Text] - idea in GitHub 73 | 2.20 |
Responder | Provide sufficient contrast between foreground and background | Don't use color alone to convey information | Ensure that interactive elements are easy to identify | Provide clear and consistent navigation options | Ensure that form elements include clearly associated labels | Provide clear feedback | Use spacing and headings to group related content | Create designs for different viewport sizes | Provide a text alternative for images | Provide controls for content that starts automatically | [Images of Text] - idea in GitHub 73 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
Lydia Harkey | 5 | 4 | 4 | 3 | 5 | 4 | 2 | 1 | 4 | 4 | No opinion | |
Melody Ma | 5 | 5 | 5 | 5 | 4 | 5 | 3 | 4 | 2 | 4 | 3 | "Provide a text alternative for images" is more of a content writer tip than designer. |
Eric Eggert | 5 | 5 | 5 | 4 | 3 | 5 | 4 | 5 | 1 | 2 | 3 | |
Andrew Arch | 5 | 5 | 5 | 5 | 4 | 4 | 3 | 4 | 2 | 4 | 1 | |
Shadi Abou-Zahra | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 2 | 3 | 1 | |
Howard Kramer | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | |
Kevin White | 5 | 5 | 5 | 4 | 4 | 4 | 5 | 5 | 1 | 3 | 1 | |
Jonathan Metz | 1 | 2 | 4 | 3 | 5 | 4 | 5 | 5 | 3 | 5 | 4 | I interviewed 8 Creatives last month, and everyone of them made some mention about accessibility having to do with making sure there's enough color contrast. It took me a while to figure it out, but I believe that of most WCAG recommendations, it's the most self-evident one that is easiest to understand. If Standards are a field where vagueness is abundant, proper color contrast is the most precise and clear to grasp in the world of visual design. |
Sylvie Duchateau | 4 | 5 | 5 | 4 | 4 | 3 | 3 | 2 | 5 | 5 | No opinion | |
George Heake | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | |
Reinaldo Ferraz | 5 | 5 | 4 | 5 | 5 | 5 | 5 | 5 | 2 | 5 | 1 | |
Brent Bakken | 5 | 5 | 4 | 4 | 4 | 4 | 3 | 3 | 2 | 4 | 3 | I have rated "Provide a text alternative for images" a 2. It is an important tip, but I am okay with it being in the writing category if it is not in the designing category. |
Vicki Menezes Miller | 5 | 5 | 5 | 5 | 4 | 3 | 3 | 2 | 5 | 1 | 2 | |
Shawn Lawton Henry | 5 | 4 | 3 | 3 | 4 | 4 | 3 | No opinion | 2 | 3 | 3 | thoughts on order: * generally good to have easy ones first -- easy to understand and easy to implement * generally good to group tips, e.g., color-related, form-related * like color ones first * maybe move "Provide clear and consistent navigation options" up * maybe move "Use headings and spacing to group related content" up * maybe move "Ensure that interactive elements are easy to identify" down since it's best practice rather than required for lots of content (browser default meets minimum requirements for standard HTML content) all order comments are [low-medium] |
Sharron Rush | 5 | 5 | 5 | 5 | 4 | 4 | 5 | 5 | 3 | No opinion | No opinion |
summary | by responder | by choice
Tips on Writing for Web Accessibility
We'll do the same thing with rating the Tips on Writing. First we need to get all ideas.
Please think about any other tips that we might want to include. If you have suggestions on additional tips, please create a GitHub issue with a draft proposal of the tip text (and explanation and examples if you can).
(If you have comments on the current draft tips, please put those in GitHub -- either Fork & Edit, or create a GitHub issue.)
Choice | All responders |
---|---|
Results | |
I thought about it carefully and added issues(s) in GitHub. | 6 |
I thought about it carefully and added issues(s) in comments below. | 1 |
I thought about it carefully and think these are the right Tips. | 5 |
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] | 1 |
I'm not going to be able to get to this, and I will pass on commenting on it. | 1 |
(1 response didn't contain an answer to this question)
Skip to view by choice.
Responder | Tips on Writing | Comments |
---|---|---|
Lydia Harkey |
|
|
Melody Ma |
|
|
Eric Eggert |
|
I wondered if we might be able to combine tip 1 & 2 but leave that to editor’s discretion. |
Andrew Arch |
|
|
Shadi Abou-Zahra |
|
|
Howard Kramer |
|
7/23/15 |
Kevin White |
|
Document editor |
Jonathan Metz |
|
|
Sylvie Duchateau |
|
I'm not sure I can review this so I prefer not giving a date. |
George Heake | ||
Reinaldo Ferraz |
|
|
Brent Bakken |
|
Looks good! To me, all WCAG SC about writing content are covered in the current tips. |
Vicki Menezes Miller |
|
|
Shawn Lawton Henry |
|
https://github.com/w3c/wai-quick-start/issues/113 https://github.com/w3c/wai-quick-start/issues/114 |
Sharron Rush |
|
Should be able to review by Monday 20 July |
Choice | Responders |
---|---|
I thought about it carefully and added issues(s) in GitHub. |
|
I thought about it carefully and added issues(s) in comments below. |
|
I thought about it carefully and think these are the right Tips. |
|
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. |
|
summary | by responder | by choice
Tips on Developing for Web Accessibility
We'll do the same thing with rating the Tips on Developing. First we need to get all ideas.
Please think about any other tips that we might want to include. If you have suggestions on additional tips, please create a GitHub issue with a draft proposal of the tip text (and explanation and examples if you can).
(If you have comments on the current draft tips, please put those in GitHub -- either Fork & Edit, or create a GitHub issue.)
Choice | All responders |
---|---|
Results | |
I thought about it carefully and added issues(s) in GitHub. | 4 |
I thought about it carefully and added issues(s) in comments below. | 1 |
I thought about it carefully and think these are the right Tips. | 7 |
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] | 2 |
I'm not going to be able to get to this, and I will pass on commenting on it. | 1 |
Skip to view by choice.
Responder | Tips on Developing | Comments |
---|---|---|
Lydia Harkey |
|
Thursday, July 16 |
Melody Ma |
|
|
Eric Eggert |
|
https://github.com/w3c/wai-quick-start/pull/116 https://github.com/w3c/wai-quick-start/pull/117 https://github.com/w3c/wai-quick-start/issues/118 |
Andrew Arch |
|
|
Shadi Abou-Zahra |
|
|
Howard Kramer |
|
7/23/15 |
Kevin White |
|
Document editor |
Jonathan Metz |
|
Is there any chance we can suggest developers not go crazy with the Z-Order? I'm asking for a friend. |
Sylvie Duchateau |
|
|
George Heake |
|
Good example that conveys what we are trying to get across. |
Reinaldo Ferraz |
|
|
Brent Bakken |
|
I have read over all the tips. This is the area where I have the least accessibility knowledge and experience. To me it looks good, but I defer to others with development experience to know what else should be included. |
Vicki Menezes Miller |
|
- following last week's conference call, there was consideration to add a part on images - just a question, perhaps, it has already been discussed. Should there be anything about tables and data? (brainstorming > I don't feel strongly about it) - perhaps it has already been discussed. Should there be any mention of captcha and trying to find alternatives to captcha? (brainstorming > I don't feel strongly about it) |
Shawn Lawton Henry |
|
https://github.com/w3c/wai-quick-start/issues/151 https://github.com/w3c/wai-quick-start/issues/152 https://github.com/w3c/wai-quick-start/issues/153 https://github.com/w3c/wai-quick-start/issues/154 https://github.com/w3c/wai-quick-start/issues/156 https://github.com/w3c/wai-quick-start/issues/155 https://github.com/w3c/wai-quick-start/issues/67 |
Sharron Rush |
|
Choice | Responders |
---|---|
I thought about it carefully and added issues(s) in GitHub. |
|
I thought about it carefully and added issues(s) in comments below. |
|
I thought about it carefully and think these are the right Tips. |
|
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. |
|
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
.