W3C

Site Navigation

Nearby

Results of Questionnaire EOWG Weekly Survey – 1 June 2015

The results of this questionnaire are available to anybody. In addition, answers are sent to the following email addresses: shawn@w3.org, kevin@w3.org, shadi@w3.org

This questionnaire was open from 2015-06-01 to 2015-06-10.

10 answers have been received.

Jump to results for question:

  1. Quick Start Tips: Titles
  2. Quick Start Tips: Banner
  3. Quick Start Tips: Intro Paragraph
  4. Quick Start Tips: Icons

1. Quick Start Tips: Titles

Based on the input from the 29 May EOWG teleconference, we have mocked up ideas for the titles and sub-titles of the main page and the Tips pages. See the updated draft Tips for Getting Started with Web Accessibility and the headings of the Tips pages — e.g., Designing for Web Accessibility: Tips for user interface and visual design.

(For comparison: previous draft titles; ideas from the previous survey.)

What do you think of this approach to the titles?

Summary

ChoiceAll responders
Results
I support this approach as is. 6
I like the direction, and have suggestions for tweaks in the comments below. 3
I don't like it, and have comments below.
I didn't get to it. 1
Other

Details

Responder Quick Start Tips: TitlesComments
Emmanuelle Gutiérrez y Restrepo I support this approach as is.
Shawn Lawton Henry I like the direction, and have suggestions for tweaks in the comments below. We expect that people will often get to a specific tips page without ever going to the overview page.

Conceptually, the content of the individual tips page is:
* Tips for Getting Started Designing for Web Accessibility (specifically for user interface and visual design)
* Tips for Getting Started Developing for Web Accessibility (specifically for markup and coding)
* etc.

On the overview page, we want the key phrase to stand out and be front-loaded (Designing, Developing, etc.)
And we want the tips page titles to clearly match the links in the overview page (using the same front-loaded word).

So we need to figure out the best way to address all that.

After working on this more, I now suggest:
* Overview page as drafted with h1/title "Tips for Getting Started with Web Accessibility" and tips page listed as: "_Designing<br/>for Web Accessibility_<br/> Tips for user interface and visual design."
* Tips pages:
** title/<h1>Designing for Web Accessibility: Tips for Getting Started</h1>
** intro paragraph includes: "... for user interface and visual design ..."
** box with "Tips for Getting Started with Web Accessibility" & links to others is a box float right or otherwise not at the top.

- pro: title/h1 is front-loaded with Designing, Developing, etc.
- pro: "tips for getting started" is in the title/h1 of each tips page
- pro: shorter title/h1 (that if we included the details)
- con: the details "for user interface and visual design" have less visibility in the tips pages (I think that's OK -- especailly because except for the first two, they don't add any much info anyway.)

(fyi, another idea that I reasoned myself out of:
* "Tips for Getting Started with Web Accessibility" is a banner across the top of each page
* <h1>Designing for Web Accessibility <subtitle>Tips for user interface and visual design</subtitle></h1>
- cons: long title/h1; "getting started" not in the title/h1 )

Or maybe there is a more graceful and clear way to address the issues?
Paul Schantz I support this approach as is.
Howard Kramer I like the direction, and have suggestions for tweaks in the comments below. I wouldn't put "designing" and "developing" next to each other - takes a few seconds to distinguish one from the other.
Perhaps more line spacing or a thin border would aid visual scanning of the 6 choices.
Melody Ma I like the direction, and have suggestions for tweaks in the comments below. The layout is odd and non-traditional. The titles and subtitles are fine.
Sylvie Duchateau I didn't get to it.
Vicki Menezes Miller I support this approach as is.
Jonathan Metz I support this approach as is.
Eric Eggert I support this approach as is.
Brent Bakken I support this approach as is.

2. Quick Start Tips: Banner

In the 29 May EOWG teleconference, there was a suggestion to have some kind of banner that would: 1. provide context for the Tips pages, and 2. provide navigation to the other Tips pages. Note that we agreed that often people would focus on only one Tips page, and not use all of the Tips pages. (as opposed to something like the business case where users would often use all of the sub-pages) Two ideas for consideration:

  1. Separate Box, maybe float right
  2. Banner above the H1 (maybe with a drop-down or pop-up to link to the others).

NOTE: Do not get hung up on the visual design of these rough ideas; they're just quick mockups to help discuss the concepts.

Do you prefer either of these approaches? Why?
What other ideas do you have to refine either of these approaches, or ideas on a different approach?

Summary

ChoiceAll responders
Results
I strongly prefer 1. box 5
I mildly prefer 1. box 3
I strongly prefer 2. banner
I mildly prefer 2. banner 1
I don't like either, and suggest something different.
I didn't get to it.
Other 1

Details

Responder Quick Start Tips: BannerPlease explain
Emmanuelle Gutiérrez y Restrepo I strongly prefer 1. box
Shawn Lawton Henry Other It depends on what we do with the titles. See above.
Paul Schantz I strongly prefer 1. box The box is SO much more obvious to me.
Howard Kramer I mildly prefer 1. box I was an advocate for the banner last week but with the change in colors for the box (white background instead of gray and reddish text font, I think the box works well for branding and identifying this resource.
Melody Ma I strongly prefer 1. box
Sylvie Duchateau I mildly prefer 2. banner
Vicki Menezes Miller I strongly prefer 1. box
Jonathan Metz I strongly prefer 1. box I don't like how clicking on "more tips" opens a new page. Also, it didn't seem obvious enough to separate itself from the other content.
Eric Eggert I mildly prefer 1. box I like both, the banner needs a lot of visual polishing to make everything appear as one coherent resource. I prefer the box (mildly) as it gives immediate access to the individual topics without going through the “main page”.
Brent Bakken I mildly prefer 1. box At this stage of development I prefer the box, but I am not against the banner approach if it can have the other pages listed instead of going back to the overview page again. That may make the banner too crowded or cluttered, but there may be a very interesting visual way to do it.

3. Quick Start Tips: Intro Paragraph

For each tips page, do we want an intro paragraph, or not? (Remember that each Tips page has a "Learn more about accessibility" tip.)

  1. Example intro paragraph
  2. Example without intro paragraph

If we do have an intro paragraph, what would be the boilerplate text across all pages? Would there be additional specific text for each? If so, please provide example text.

You can put your ideas here, or in Github.

Summary

ChoiceAll responders
Results
I strongly think the Tips pages need an intro paragraph. 3
I mildly think the Tips pages need an intro paragraph. 4
I strongly think the Tips pages do not need an intro paragraph. 1
I mildly think the Tips pages do not need an intro paragraph.
I didn't get to it. 1
Other. 1

Details

Responder Quick Start Tips: Intro ParagraphSuggestion for boilerplate introduction text - and/or - Suggestions for intro paragraph for specific pages
Emmanuelle Gutiérrez y Restrepo I strongly think the Tips pages need an intro paragraph.
Shawn Lawton Henry Other. I think the current intro paragraphs are superfluous.

However, if we do my suggestion above, then they would provide a little useful information by further clarifying the scope of the pages.

[I'll try to suggest boilerplate text asap.]
Paul Schantz I mildly think the Tips pages need an intro paragraph. IMO, it's nice to orient the reader, especially if they arrive there from a search engine.
Howard Kramer I mildly think the Tips pages need an intro paragraph. I support an intro paragraph but it should be short and concise but could be talked into no intro. I like the version without the into also although I'd change the subheading from "Tips on planning and managing to address accessibility" to just "Tips on planning and managing"
Melody Ma I strongly think the Tips pages need an intro paragraph. I like the fact that it says this is not and exhaustive list that there's more.
Sylvie Duchateau I didn't get to it.
Vicki Menezes Miller I strongly think the Tips pages need an intro paragraph.
Jonathan Metz I strongly think the Tips pages do not need an intro paragraph. It just seems redundant.
Eric Eggert I mildly think the Tips pages need an intro paragraph. The headings (and sub headings) are very descriptive, so I don’t think the Tips pages need an intro paragraph every time. I suggest using an intro paragraph when the topic is not clear through the title. If you want it consistent, I’d mildly vote in favor of such paragraph.
Brent Bakken I mildly think the Tips pages need an intro paragraph. Even though about half of the users will not read the paragraph, that does not mean a paragraph should not be there for other users who like some information or level setting of what they are about to explore in the tips listed on the page.

4. Quick Start Tips: Icons

summary | by responder | by choice

One idea is to have an icon for each category that would be on the on the main page and the sub-page. (maybe like this mockup but with different icon for each)

Do you have any concerns with using icons?
Would you help to develop the icons?

Summary

ChoiceAll responders
Results
I'll help! I can lead the work. 2
I'll help, but cannot lead the work. 4
Sorry, not my thing. 2
other 3

Skip to view by choice.

View by responder

Details

Responder Quick Start Tips: IconsAny concerns or considerations
Emmanuelle Gutiérrez y Restrepo
  • I'll help! I can lead the work.
Shawn Lawton Henry
  • I'll help, but cannot lead the work.
  • other
 I support icons. Of course they will be challenging.
Paul Schantz
  • Sorry, not my thing.
 I support the idea of using an icon for each category, but my art skills are TERRIBLE!
Howard Kramer
  • I'll help, but cannot lead the work.
 I support use of icons. I'm happy to provide suggestions on how they might look but I'm not experienced in creating art work.
Melody Ma
  • other
 I don't think the icons will add a lot of value in this context of how it's used.
Sylvie Duchateau
  • Sorry, not my thing.
Vicki Menezes Miller
  • other
 I usually like icons but I must say the way the page has been designed, you may not actually need icons. It really is clear.
Jonathan Metz
  • I'll help! I can lead the work.
  • I'll help, but cannot lead the work.
 I would be more than happy to draw a icon for anything that someone else tells me to draw. Abstract thinking is not really my strong suit, but I can draw what you tell me to draw.

There's also fontawesome iconography as well...
Eric Eggert
Brent Bakken
  • I'll help, but cannot lead the work.
 I like to brainstorm and come up with design concepts like layout and iconography. I do not have skills to create icons, but I would like to help with the process.

View by choice

ChoiceResponders
I'll help! I can lead the work.
  • Emmanuelle Gutiérrez y Restrepo
  • Jonathan Metz
I'll help, but cannot lead the work.
  • Shawn Lawton Henry
  • Howard Kramer
  • Jonathan Metz
  • Brent Bakken
Sorry, not my thing.
  • Paul Schantz
  • Sylvie Duchateau
other
  • Shawn Lawton Henry
  • Melody Ma
  • Vicki Menezes Miller

More details on responses

  • Emmanuelle Gutiérrez y Restrepo: last responded on 3, June 2015 at 18:46 (UTC)
  • Shawn Lawton Henry: last responded on 3, June 2015 at 19:32 (UTC)
  • Paul Schantz: last responded on 3, June 2015 at 23:03 (UTC)
  • Howard Kramer: last responded on 4, June 2015 at 02:52 (UTC)
  • Melody Ma: last responded on 4, June 2015 at 07:22 (UTC)
  • Sylvie Duchateau: last responded on 4, June 2015 at 07:54 (UTC)
  • Vicki Menezes Miller: last responded on 4, June 2015 at 20:28 (UTC)
  • Jonathan Metz: last responded on 5, June 2015 at 00:16 (UTC)
  • Eric Eggert: last responded on 5, June 2015 at 11:19 (UTC)
  • Brent Bakken: last responded on 5, June 2015 at 13:02 (UTC)

Non-responders

The following persons have not answered the questionnaire:

  1. Eric Velleman
  2. Andrew Arch
  3. Shadi Abou-Zahra
  4. Kazuhito Kidachi
  5. Sharron Rush
  6. Jedi Lin
  7. David Sloan
  8. Mary Jo Mueller
  9. Reinaldo Ferraz
  10. Bill Kasdorf
  11. Cristina Mussinelli
  12. Kevin White
  13. Kevin Rydberg
  14. Ahmath Bamba MBACKE
  15. Adina Halter
  16. Denis Boudreau
  17. Laura Keen
  18. Sarah Pulis
  19. Bill Tyler
  20. Gregorio Pellegrino
  21. Ruoxi Ran
  22. Jennifer Chadwick
  23. Sean Kelly
  24. Muhammad Saleem
  25. Sarah Lewthwaite
  26. Daniel Montalvo
  27. Mark Palmer
  28. Jade Matos Carew
  29. Sonsoles López Pernas
  30. Greta Krafsig
  31. Jason McKee
  32. Jayne Schurick
  33. Billie Johnston
  34. Michele Williams
  35. Shikha Nikhil Dwivedi
  36. Brian Elton
  37. Julianna Rowsell
  38. Tabitha Mahoney
  39. Fred Edora
  40. Rabab Gomaa
  41. Marcelo Paiva
  42. Eloisa Guerrero
  43. Leonard Beasley
  44. Frankie Wolf
  45. Supriya Makude
  46. Aleksandar Cindrikj
  47. 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 w3c/wbs-design or by mail to sysreq.