W3C

Site Navigation

Nearby

Results of Questionnaire EOWG Survey on Tips Refinement

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

This questionnaire was open from 2015-06-03 to 2015-06-12.

8 answers have been received.

Jump to results for question:

  1. Tips Review
  2. Designing Tips
  3. Developing Tips
  4. Writing Tips
  5. Evaluating Tips
  6. Managing Tips
  7. Advocating Tips

1. Tips Review

We are coming closer to agreeing on the titles for the main page and the tips pages. Several people have contributed to the text of the Tips.

Next we need to finalize the text of the Tips themselves. After that we will refine the explanation (the paragraphs under the tips) and the links.

Please review very thoroughly the Tips on each page. Consider the following:

  • Add tips - Are there any things that are not included that we might want to add a tip for? (i.e., what that role needs to do to get started in accessibility)
  • Delete tips - Of the tips that are there now, are there any that we might not want to keep?
  • Edit tips - Can these be worded more clearly and succinctly?

Please put your comments in Github, if you are comfortable with that. Otherwise, you can put them in this survey or in the wiki or in e-mail.

(Note: Focus on the tip text, which is listed at the top. The explanation text underneath each tip is still in progress and very rough. You do *not* need to comment on that yet. However, you can if you want.)

Details

Responder Tips Review
Sharron Rush



Melody Ma Because of the few number of tips highlighted, the user can easily misinterpret that this is all they have to do to comply with accessibility requirements. This is especially pronounced in the Development section, which has fewer accessibility tips than every other section. There seems like there's good introductory text in some sections, but not consistently throughout.
Lydia Harkey The "Tips" page is nicely laid out with the icons which provides great visual effects. The icons with Tip menus is short and consistent on the side navigation section.

Would it be feasible to consolidate many of the information that currently exist within W3C to make the tips more robust by either consolidating or referring back to those pages, on the basis the information is up to date?



Howard Kramer
Shawn Lawton Henry I put some overall suggestions as Github issues.

EOWG might want to discuss this one: I wonder if we need to "define" "accessibility" as "to people with disabilities" in the opening paragraph [of every page]? -- to give it context for people who land on this page and don't know. (I was interested in the HTML5 WebX course comments that at least 2 people did not know about accessibility!)(https://github.com/w3c/wai-quick-start/pull/22>)
Shadi Abou-Zahra
Vicki Menezes Miller Congratulations: A really nice package of tips
I really like the usage of icons.
Andrew Arch mixture of comments below + in Github

2. Designing Tips

summary | by responder | by choice

Designing for Web Accessibility: Tips for user interface and visual design

Summary

ChoiceAll responders
Results
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly. 7
I will get to it soon.
I'll pass on this one.

Skip to view by choice.

View by responder

Details

Responder Designing Tips
Sharron Rush
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Edit suggestion: ...interactive elements are easily and unambiguously identified.

Melody Ma
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 "Present text in a flexible font size and line length" is unclear. It can be interpreted as scaling font size up and down using media queries.
Lydia Harkey
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Within each section of the tips if other resources that have already been provided elsewhere within W3C what about linking to that page. For example, in Evaluating Tools the content for 'Select tools to assist in testing' would refer/link to the Web Accessibility Evaluation Tools List page.
Howard Kramer
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Shawn Lawton Henry I submitted pull request for ideas on the opening paragraph.
Shadi Abou-Zahra
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Minor wording suggestions:

* Provide sufficient contrast between colors -> Provide sufficient color contrast
* Ensure interactive elements are easily identified -> Ensure interactive elements are easy to identify
* Provide consistent navigation and orientation information -> Provide consistent navigation and orientation
* Ensure form elements include clearly associated labels -> Provide labels for forms and controls
* Provide clear presentation of errors -> Provide clear feedback [and errors]
* Use headers and whitespace to group content -> Use headers and spacing to group [related] information|content
Vicki Menezes Miller
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Add: a pointer to the images tutorial
Rationale: Images are so much part of design (thumbnails on portals to link to further information, images with text, images to perk up designs, logos etc). I think it would be important to have a link to further guidance on images.
Andrew Arch
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Contrast - what about also linking to http://www.w3.org/WAI/eval/preliminary.html#contrast (or in learn more)
Colour alone - suggest accessible pie chart uses same colours as inaccessible one if possible
Interactive elements - could plain example please have the defaults of underline; and then the hover and keyboard-focus could be similar (I wasn't sure what the activated one was illustrating for id - looked the same to me)
Media player - shouldn't 'cc' also be highly visible?
Form elements - maybe link to http://www.w3.org/WAI/eval/preliminary.html#forms; instructions - maybe suggest they should precede the form (or form element)
Headers & Text section are too repetitive at present (sorry - no immediate suggestions)

View by choice

ChoiceResponders
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
  • Sharron Rush
  • Melody Ma
  • Lydia Harkey
  • Howard Kramer
  • Shadi Abou-Zahra
  • Vicki Menezes Miller
  • Andrew Arch
I will get to it soon.
I'll pass on this one.

3. Developing Tips

summary | by responder | by choice

Developing for Web Accessibility: Tips for markup and coding

Summary

ChoiceAll responders
Results
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly. 7
I will get to it soon.
I'll pass on this one.

Skip to view by choice.

View by responder

Details

Responder Developing Tips
Sharron Rush
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Add: Maintain consistent names for navigation and other interactive elements (this may belong in Designing)

Edit: Use markup to convey meaning [and information structure]
Melody Ma
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 This seems extremely light for the actual amount of work that developers have to do to comply to Level A. Missing things like tables, menus, images, etc. that were part of the tutorials.
Lydia Harkey
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Consider adding CSS, JavaScript Web APIs, mobile, responsive design and other technical information that assists developers in coding. Maybe refer back to W3C resources for developers.
Howard Kramer
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Shawn Lawton Henry
Shadi Abou-Zahra
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Medium issues:

* add: Help users avoid and correct mistakes - similar to "Provide clear feedback [and errors]" in the "Designing Tips" but focuses on the mechanics rather than the output/design/placement etc.
* add: Use progressive enhancement approaches - could override the "Provide meaning to non-standard interactive elements" but does not have to overlap (could be very complimentary and useful)
* add: something about "breakpoints for mobile and adaptation"? This is related to design but maybe more geared to the programming
Vicki Menezes Miller
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 I think it's difficult not to get into more depth in this area. I feel that information is missing and would add something about tables, images (I realise that there is an overlap), menus, more on information structure, navigation.
Andrew Arch
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Suggest "Evaluate early ..." is placed high in tips list
See also GitHub suggestions

View by choice

ChoiceResponders
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
  • Sharron Rush
  • Melody Ma
  • Lydia Harkey
  • Howard Kramer
  • Shadi Abou-Zahra
  • Vicki Menezes Miller
  • Andrew Arch
I will get to it soon.
I'll pass on this one.

4. Writing Tips

summary | by responder | by choice

Writing for Web Accessibility: Tips for writing content

Summary

ChoiceAll responders
Results
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly. 7
I will get to it soon.
I'll pass on this one.

Skip to view by choice.

View by responder

Details

Responder Writing Tips
Sharron Rush
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Edit: "Provide short, meaningful headings to break up text"
The purpose of headings is not just to"break up text," but rather to convey information structure. This could cause writers to think they must just throw in headings for visual relief.
Melody Ma
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Lydia Harkey
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Suggest adding information on 'Descriptive Text' versus 'Audio Text' for multi-media content or art images, etc.
Howard Kramer
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Shawn Lawton Henry
Shadi Abou-Zahra
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Minor wording suggestions:
* Avoid using needlessly complex words -> Avoid using overly complex words|terms [and phrases]
* Make link text clear -> Provide useful link text
* Provide short, meaningful headings to break-up text -> Provide meaningful headings to organize text|content|information
* Use informative and unique page titles -> Provide informative titles for each web page
* Provide alternative text for all images -> Provide text alternatives for all images

Medium issues:
* Keep it short and simple - don't like the "it" (too ambiguous)
* Expand all acronyms on their first use - is this really as critical as text alternatives and labels (for people new to accessibility)?
Vicki Menezes Miller
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Andrew Arch
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 short and simple - mention that all audiences find shorter sentences with one idea per paragraph easier to read and especially easier to skim online which is what most (many?) do

We should also eat our own dog food - many "learn more" links on the pages that might become expand/collapse links :(

View by choice

ChoiceResponders
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
  • Sharron Rush
  • Melody Ma
  • Lydia Harkey
  • Howard Kramer
  • Shadi Abou-Zahra
  • Vicki Menezes Miller
  • Andrew Arch
I will get to it soon.
I'll pass on this one.

5. Evaluating Tips

summary | by responder | by choice

Evaluating Web Accessibility: Tips on the evaluation process

Summary

ChoiceAll responders
Results
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly. 6
I will get to it soon. 1
I'll pass on this one.

Skip to view by choice.

View by responder

Details

Responder Evaluating Tips
Sharron Rush
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Good, no suggestions
Melody Ma
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Lydia Harkey
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Suggest adding QA process as part of the evaluation.
Howard Kramer
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Shawn Lawton Henry
Shadi Abou-Zahra
  • I will get to it soon.
Vicki Menezes Miller
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Andrew Arch
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 suggestions in Github

View by choice

ChoiceResponders
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
  • Sharron Rush
  • Melody Ma
  • Lydia Harkey
  • Howard Kramer
  • Vicki Menezes Miller
  • Andrew Arch
I will get to it soon.
  • Shadi Abou-Zahra
I'll pass on this one.

6. Managing Tips

summary | by responder | by choice

Managing Web Accessibility: Tips on planning and managing

Summary

ChoiceAll responders
Results
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly. 6
I will get to it soon. 1
I'll pass on this one.

Skip to view by choice.

View by responder

Details

Responder Managing Tips
Sharron Rush
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Add: Integrate accessibility considerations throughout project life cycle.
Melody Ma
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Missing reviewing applicable legislation and compliance requirements for accessibility.
Lydia Harkey
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 Add Project Management
Add software life cycle
Howard Kramer
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Shawn Lawton Henry
Shadi Abou-Zahra
  • I will get to it soon.
Vicki Menezes Miller
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Andrew Arch
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 publicly available website accessibility statement - I have always advised priding a statement of intent rather than a statement of conformance which invites criticism as people can always find something wrong!

Also suggestion in Github

View by choice

ChoiceResponders
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
  • Sharron Rush
  • Melody Ma
  • Lydia Harkey
  • Howard Kramer
  • Vicki Menezes Miller
  • Andrew Arch
I will get to it soon.
  • Shadi Abou-Zahra
I'll pass on this one.

7. Advocating Tips

summary | by responder | by choice

Advocating for Web Accessibility: Tips for understanding and promoting accessibility

Summary

ChoiceAll responders
Results
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly. 5
I will get to it soon. 1
I'll pass on this one. 1

Skip to view by choice.

View by responder

Details

Responder Advocating Tips
Sharron Rush
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 OK, no suggestion
Melody Ma
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Lydia Harkey
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
 No suggestions
Howard Kramer
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Shawn Lawton Henry
Shadi Abou-Zahra
  • I will get to it soon.
Vicki Menezes Miller
  • I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
Andrew Arch
  • I'll pass on this one.

View by choice

ChoiceResponders
I reviewed the Tips text thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly.
  • Sharron Rush
  • Melody Ma
  • Lydia Harkey
  • Howard Kramer
  • Vicki Menezes Miller
I will get to it soon.
  • Shadi Abou-Zahra
I'll pass on this one.
  • Andrew Arch

More details on responses

  • Sharron Rush: last responded on 10, June 2015 at 03:01 (UTC)
  • Melody Ma: last responded on 10, June 2015 at 05:40 (UTC)
  • Lydia Harkey: last responded on 11, June 2015 at 02:23 (UTC)
  • Howard Kramer: last responded on 11, June 2015 at 04:54 (UTC)
  • Shawn Lawton Henry: last responded on 11, June 2015 at 12:57 (UTC)
  • Shadi Abou-Zahra: last responded on 11, June 2015 at 15:23 (UTC)
  • Vicki Menezes Miller: last responded on 11, June 2015 at 21:30 (UTC)
  • Andrew Arch: last responded on 24, June 2015 at 12:12 (UTC)

Non-responders

The following persons have not answered the questionnaire:

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