w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire EOWG Weekly Survey - 24 July 2015
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-24 to 2015-08-05.
15 answers have been received.
Jump to results for question:
- Tips on Writing: readable and understandable tips separate or together?
- Tips on Writing - Rating which to include or not
- Tips on Developing - Rating which to include or not
- [DONE] Tips on Developing - Approach to ordering
1. Tips on Writing: readable and understandable tips separate or together?
First, please read the telecon discussions of combining points related to readable and understandable under one tip from 24 July (under topic "Writing Tip on Lists") and 31 July.
Next, look at these pages with two options:
- Separate tips related to readable and understandable includes tips for:
- Keep content clear and concise
- Avoid using overly complex words and phrases
- Expand acronyms on first use
- (missing: Use list formatting as appropriate.)
- (missing: Provide images to reinforce information presented in text.)
- One tip on readable and understandable has the above points under the tip:
- Make text readable and understandable
Also, please include your thoughts on why we might want to do one option versus the other.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I strongly prefer separate tips for the readable and understandable points. | 4 |
| I mildly prefer separate tips for the readable and understandable points. | 2 |
| I'm not sure. | 1 |
| I mildly prefer one tip on readable and understandable. | 1 |
| I strongly prefer one tip on readable and understandable. | 4 |
| I haven't had a chance to consider this, and will pass on commenting on it. | 3 |
Details
| Responder | Tips on Writing: readable and understandable tips separate or together? | Thoughts on pros and cons of each option |
|---|---|---|
| Kevin White | I strongly prefer separate tips for the readable and understandable points. | Presenting a tip as 'Make text readable and understandable' obscures too much of what needs to be done. It hides the detail from the skim reader and forces them to work much harder to determine what it is they need to do. It also means that the tips don't function on their own and they must have the descriptive content to be understood. I also feel that there is too much crammed into this tip simply because it is done that way in WCAG 3.1. If there is a desire to consider encouraging writers to use lists, I think there may be better ways to do it. For example, rather than confine tip on meaning and structure to just headings, it could be made more general. |
| Lydia Harkey | I strongly prefer separate tips for the readable and understandable points. | I found the separate tips easy to read and did not find it cluttered. the side by side comparison was an easy read and helpful. Providing one tip may not appear to provide enough information for readers even though the information may be the same. The layout seems less cluttered but wondered if the user would have to scroll down to read versus reading in "z" format. |
| Brent Bakken | I mildly prefer one tip on readable and understandable. | I was first opposed to combining for one tip, but now that I see it laid out on the page, I think that each sup-tip is well enough explained. I also think the example is excellent as it is one example that demonstrates the entire collection of sub-tips well. I even like the idea of the image to support the text as a quick visual for those who like that modality. The example really drives home the power of using all these sub-tips collectively. The content is much more consumable when all the sup-tips are implemented. I am fine if the group decides separate tips are better, I just think this is tied together well and shortens the list of Tips on Writing. |
| Reinaldo Ferraz | I strongly prefer separate tips for the readable and understandable points. | |
| Andrew Arch | I mildly prefer separate tips for the readable and understandable points. | Happy to go with one tip (currently well done) if we chose to go that way, but does lose some detail. |
| Shawn Lawton Henry | I strongly prefer one tip on readable and understandable. | I think these points are all very related and it makes sense to put them together in one tip. I don't think they need more explanation than is in the one tip. (I think in the option where they are separate, there is too much explanation text for most of them.) I think putting these points together in one tip helps reduce clutter overall -- and *gives better visibility to the other tips*. I would be open to having separate tips *if* they were grouped, e.g., like in <http://www.w3.org/WAI/eval/preliminary#toc> |
| Sharron Rush | I mildly prefer separate tips for the readable and understandable points. | I will go with the group on this, but lumping them together will encourage less attention to each point. |
| Shadi Abou-Zahra | I strongly prefer one tip on readable and understandable. | Pros: - Together these make a stronger point; - They all relate to "penmanship"; Cons: - Don't really see any negatives - doesn't seem like a problem lumping them up - they really all relate to the same objective. |
| Paul Schantz | I haven't had a chance to consider this, and will pass on commenting on it. | |
| Howard Kramer | I haven't had a chance to consider this, and will pass on commenting on it. | |
| Melody Ma | I strongly prefer one tip on readable and understandable. | Having one tip allows flexibility to add more specific sub tips. |
| Anna Belle Leiserson | I haven't had a chance to consider this, and will pass on commenting on it. | |
| George Heake | I strongly prefer separate tips for the readable and understandable points. | In regards to issue of skimming and reading through information, separate points are important part of the structure of information that we are trying to convey. |
| Vicki Menezes Miller | I strongly prefer one tip on readable and understandable. | I prefer one tip for the following reasons: - they are so closely related - separating them makes each tip on its own weaker - presented together, there is a logical flow of thought and understanding - a single example can be given - it makes the page shorter and more readable |
| Jonathan Metz | I'm not sure. |
2. Tips on Writing - Rating which to include or not
Tips on Writing for Web Accessibility
Let's do a final poll to help decide which tips to include or not. (We realize the issue above will effect this somewhat, but we didn't want to put off the rating any longer.)
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 Tips on Writing 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.
Summary
| Choice | All responders | |||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | No opinion | |
| Provide informative, unique page titles | 1 | 3 | 4 | 4 | 3 | |
| Use headings to convey meaning and structure | 3 | 9 | 3 | |||
| Keep content clear and concise [if separate] | 1 | 6 | 3 | 5 | ||
| Avoid using overly complex words and phrases [if separate] | 1 | 1 | 6 | 2 | 5 | |
| Make link text meaningful | 2 | 5 | 5 | 3 | ||
| Provide text alternatives for images | 1 | 4 | 7 | 3 | ||
| Provide transcripts and captions for multimedia | 8 | 4 | 3 | |||
| Provide clear instructions | 2 | 8 | 2 | 3 | ||
| Expand acronyms on first use [if separate] | 1 | 2 | 6 | 2 | 4 | |
| Use list formatting as appropriate (GitHub120) [if separate] | 1 | 3 | 5 | 1 | 5 | |
| Provide images to reinforce information presented in text (not drafted) [if separate] | 1 | 5 | 2 | 1 | 6 | |
| Make text readable and understandable [if one tip] | 4 | 6 | 5 | |||
Averages:
| Choices | All responders: |
|---|---|
| Value | |
| Provide informative, unique page titles | 3.92 |
| Use headings to convey meaning and structure | 4.75 |
| Keep content clear and concise [if separate] | 4.10 |
| Avoid using overly complex words and phrases [if separate] | 3.80 |
| Make link text meaningful | 4.25 |
| Provide text alternatives for images | 4.50 |
| Provide transcripts and captions for multimedia | 4.33 |
| Provide clear instructions | 4.00 |
| Expand acronyms on first use [if separate] | 3.82 |
| Use list formatting as appropriate (GitHub120) [if separate] | 3.60 |
| Provide images to reinforce information presented in text (not drafted) [if separate] | 3.33 |
| Make text readable and understandable [if one tip] | 4.60 |
Details
| Responder | Provide informative, unique page titles | Use headings to convey meaning and structure | Keep content clear and concise [if separate] | Avoid using overly complex words and phrases [if separate] | Make link text meaningful | Provide text alternatives for images | Provide transcripts and captions for multimedia | Provide clear instructions | Expand acronyms on first use [if separate] | Use list formatting as appropriate (GitHub120) [if separate] | Provide images to reinforce information presented in text (not drafted) [if separate] | Make text readable and understandable [if one tip] | Comments on order or anything |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kevin White | 3 | 5 | 5 | 4 | 4 | 5 | 4 | 4 | 4 | 3 | 2 | No opinion | [Document author] |
| Lydia Harkey | 5 | 4 | 5 | 5 | 4 | 5 | 4 | 5 | 5 | 4 | 3 | 4 | |
| Brent Bakken | 4 | 4 | 4 | 4 | 5 | 4 | 5 | 4 | 4 | 4 | 4 | 5 | I rated the [if separate] tips at a 4++++ and the [if one tip] as a 5+++++. I believe all of these are important and should be on the page, I just think that a collective "one tip" is more effective than separate. |
| Reinaldo Ferraz | 5 | 5 | 4 | 4 | 5 | 5 | 4 | 4 | 4 | 4 | No opinion | No opinion | |
| Andrew Arch | 3 | 5 | 4 | 4 | 5 | 5 | 5 | 3 | 3 | 3 | 3 | 4 | |
| Shawn Lawton Henry | 4 | 5 | No opinion | No opinion | 3 | 4 | 4 | 5 | No opinion | No opinion | No opinion | 4 | |
| Sharron Rush | 5 | 5 | 5 | 3 | 5 | 5 | 4 | 3 | 3 | 5 | 3 | 5 | Provide clear instructions seems complex for a quick tip |
| Shadi Abou-Zahra | 3 | 5 | 4 | 4 | 3 | 4 | 4 | 4 | 2 | 2 | 3 | 5 | - Are titles typically provided by page authors? - Suggest "provide graphics and illustrations to support" rather than "images" (sounds vague) and "to reinforce" (sounds forceful) |
| Paul Schantz | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | |
| Howard Kramer | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | |
| Melody Ma | 4 | 5 | 4 | 4 | 5 | 5 | 5 | 4 | 5 | 3 | 4 | 5 | |
| Anna Belle Leiserson | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | |
| George Heake | 5 | 5 | 4 | 5 | 4 | 5 | 5 | 4 | 4 | 4 | 3 | 4 | |
| Vicki Menezes Miller | 4 | 5 | No opinion | No opinion | 4 | 4 | 4 | 4 | 4 | No opinion | No opinion | 5 | |
| Jonathan Metz | 2 | 4 | 2 | 1 | 4 | 3 | 4 | 4 | 4 | 4 | 5 | 5 |
3. Tips on Developing - Rating which to include or not
Tips on Developing for Web Accessibility
Same thing for developing: Let's do a final poll to help decide which tips to include or not. Remember to keep in mind the criteria/considerations on which tips to include.
If you missed the telecons, please get caught up with perspectives on specific tips by reading Developing Tips discussions in: 24 July and 30 July.
Please rate the whether or not you think each tip should be included in the Tips on Developing page, with lowest meaning you think it should not be included.
- Keep in mind that the current draft has lots of tips and we probably want many fewer, so will need to cut out some of these.
- Please add comments in the survey about why you think specific tips should be included or should not be included.
If you have comments on the Tips themselves, please put them in GitHub -- either Fork and Edit, or create a new issue.
Summary
| Choice | All responders | |||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | No opinion | |
| Use progressive enhancement | 1 | 1 | 4 | 3 | 6 | |
| Adopt a responsive design approach | 2 | 8 | 2 | 3 | ||
| Use mark-up to convey meaning and structure | 1 | 3 | 7 | 4 | ||
| Associate all form elements with labels | 1 | 10 | 4 | |||
| Help users avoid and correct mistakes | 1 | 1 | 5 | 5 | 3 | |
| Reflect the reading order in the code order | 2 | 4 | 5 | 1 | 3 | |
| Provide meaning to non-standard interactive elements | 5 | 3 | 2 | 5 | ||
| Ensure that all interactive elements are keyboard accessible | 1 | 2 | 9 | 3 | ||
| Check that your code validates (see discussion at GitHub 154) | 2 | 2 | 1 | 6 | 4 | |
| Ensure compatibility of your code (see discussion at GitHub 118) | 1 | 3 | 2 | 3 | 6 | |
| Include alternative text for images | 1 | 1 | 3 | 3 | 4 | 3 |
| Ensure resized text is legible | 1 | 8 | 3 | 3 | ||
| Ensure that CAPTCHAs have accessible alternatives | 1 | 1 | 1 | 4 | 3 | 5 |
| Identify page language and language changes | 1 | 1 | 5 | 4 | 4 | |
Averages:
| Choices | All responders: |
|---|---|
| Value | |
| Use progressive enhancement | 3.78 |
| Adopt a responsive design approach | 4.00 |
| Use mark-up to convey meaning and structure | 4.45 |
| Associate all form elements with labels | 4.91 |
| Help users avoid and correct mistakes | 4.17 |
| Reflect the reading order in the code order | 3.42 |
| Provide meaning to non-standard interactive elements | 3.70 |
| Ensure that all interactive elements are keyboard accessible | 4.67 |
| Check that your code validates (see discussion at GitHub 154) | 3.00 |
| Ensure compatibility of your code (see discussion at GitHub 118) | 2.78 |
| Include alternative text for images | 3.67 |
| Ensure resized text is legible | 4.17 |
| Ensure that CAPTCHAs have accessible alternatives | 3.70 |
| Identify page language and language changes | 4.00 |
Details
| Responder | Use progressive enhancement | Adopt a responsive design approach | Use mark-up to convey meaning and structure | Associate all form elements with labels | Help users avoid and correct mistakes | Reflect the reading order in the code order | Provide meaning to non-standard interactive elements | Ensure that all interactive elements are keyboard accessible | Check that your code validates (see discussion at GitHub 154) | Ensure compatibility of your code (see discussion at GitHub 118) | Include alternative text for images | Ensure resized text is legible | Ensure that CAPTCHAs have accessible alternatives | Identify page language and language changes | Comments |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kevin White | 4 | 4 | 5 | 5 | 5 | 4 | 4 | 4 | 3 | 1 | 3 | 4 | 1 | 1 | [Document author] |
| Lydia Harkey | No opinion | 4 | 4 | 5 | 4 | 4 | No opinion | 3 | 4 | 3 | 5 | 4 | 5 | 5 | |
| Brent Bakken | 4 | 3 | 4 | 5 | 4 | 3 | 3 | 5 | 4 | 4 | 4 | 5 | 4 | 3 | |
| Reinaldo Ferraz | 1 | 4 | 2 | 5 | 5 | 2 | 3 | 5 | 4 | 3 | 2 | 4 | 2 | 5 | |
| Andrew Arch | 5 | 4 | 5 | 5 | 4 | 4 | 3 | 4 | No opinion | No opinion | 3 | 3 | 3 | 5 | |
| Shawn Lawton Henry | 2 | 4 | 5 | 5 | 2 | 2 | 3 | 5 | 1 | 2 | 5 | 4 | No opinion | No opinion | I had trouble rating because I don't think this tip is right yet, per https://github.com/w3c/wai-quick-start/issues/153 I'm conflicted about "Ensure that CAPTCHAs have accessible alternatives" and "Identify page language and language changes". These are important; however, I'm not sure if they ought to be included or not, given there are already so many tips on this page and it's just supposed to be for getting started... |
| Sharron Rush | 5 | 5 | 5 | 5 | 3 | 3 | 5 | 5 | 2 | 2 | 5 | 5 | 4 | 4 | |
| Shadi Abou-Zahra | 4 | 4 | 5 | 4 | 4 | 3 | 4 | 5 | 1 | 2 | 1 | 4 | 4 | 4 | - Suggest to combine "progressive enhancement", "responsive design", and "resize text" into something like "make content robust and adaptable", so that it is also better backed by WCAG; - Think "check your code validates" and "ensure compatibility" are adequately covered by "use markup" and "non-standard elements" - "ensure compatibility" could be mentioned in "use markup" if needed; - We already have "images" in writing, so not needed here - actually it may be counter-productive to keep repeating it everywhere. also, it reinforces the unfortunate myth that accessibility is only about alt-text; |
| Paul Schantz | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | |
| Howard Kramer | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | |
| Melody Ma | 5 | 4 | 5 | 5 | 5 | 5 | 5 | 5 | 4 | 4 | 4 | 4 | 4 | 4 | |
| Anna Belle Leiserson | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | No opinion | |
| George Heake | No opinion | 4 | No opinion | No opinion | 5 | 4 | 4 | 5 | 4 | 4 | 4 | 5 | 5 | 4 | |
| Vicki Menezes Miller | No opinion | 3 | 4 | 5 | 5 | 3 | No opinion | 5 | 4 | No opinion | 5 | 4 | No opinion | 5 | |
| Jonathan Metz | 4 | 5 | 5 | 5 | 4 | 4 | 3 | 5 | 2 | No opinion | 3 | 4 | 5 | 4 |
4. [DONE] Tips on Developing - Approach to ordering
summary | by responder | by choice
[UPDATE 31 July: EOWG resolved this at the 31 July telecon, so unless you strongly disagree, you can ignore this question now.]What order do we want these tips in? Think about approaches to ordering the tips, including the perspectives in GitHub 67.
Summary
| Choice | All responders |
|---|---|
| Results | |
| I thought about it carefully and commented in GitHub. | 4 |
| I thought about it carefully and put comments below. | |
| I thought about it carefully and don't have any ideas to add | 6 |
| 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. | 2 |
(3 responses didn't contain an answer to this question)
Skip to view by choice.
View by responder
Details
| Responder | [DONE] Tips on Developing - Approach to ordering | Comments |
|---|---|---|
| Kevin White |
|
[Document author] |
| Lydia Harkey |
|
|
| Brent Bakken |
|
|
| Reinaldo Ferraz |
|
|
| Andrew Arch |
|
|
| Shawn Lawton Henry |
|
|
| Sharron Rush |
|
|
| Shadi Abou-Zahra | ||
| Paul Schantz |
|
|
| Howard Kramer |
|
|
| Melody Ma |
|
|
| Anna Belle Leiserson | ||
| George Heake |
|
|
| Vicki Menezes Miller |
|
|
| Jonathan Metz |
View by choice
| Choice | Responders |
|---|---|
| I thought about it carefully and commented in GitHub. |
|
| I thought about it carefully and put comments below. | |
| I thought about it carefully and don't have any ideas to add |
|
| 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. |
|
More details on responses
- Kevin White: last responded on 28, July 2015 at 19:22 (UTC)
- Lydia Harkey: last responded on 30, July 2015 at 02:11 (UTC)
- Brent Bakken: last responded on 30, July 2015 at 16:09 (UTC)
- Reinaldo Ferraz: last responded on 30, July 2015 at 17:46 (UTC)
- Andrew Arch: last responded on 31, July 2015 at 12:06 (UTC)
- Shawn Lawton Henry: last responded on 31, July 2015 at 16:13 (UTC)
- Sharron Rush: last responded on 3, August 2015 at 15:50 (UTC)
- Shadi Abou-Zahra: last responded on 4, August 2015 at 09:53 (UTC)
- Paul Schantz: last responded on 4, August 2015 at 23:38 (UTC)
- Howard Kramer: last responded on 5, August 2015 at 01:50 (UTC)
- Melody Ma: last responded on 5, August 2015 at 05:04 (UTC)
- Anna Belle Leiserson: last responded on 5, August 2015 at 14:37 (UTC)
- George Heake: last responded on 5, August 2015 at 18:37 (UTC)
- Vicki Menezes Miller: last responded on 5, August 2015 at 21:11 (UTC)
- Jonathan Metz: last responded on 6, August 2015 at 05:39 (UTC)
Non-responders
The following persons have not answered the questionnaire:
- Eric Velleman
- Sylvie Duchateau
- Kazuhito Kidachi
- Jedi Lin
- David Sloan
- Mary Jo Mueller
- Bill Kasdorf
- Cristina Mussinelli
- Kevin Rydberg
- Ahmath Bamba MBACKE
- Adina Halter
- Denis Boudreau
- Laura Keen
- 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