W3C

Site Navigation

Nearby

Results of Questionnaire EOWG Weekly Survey - 8 January 2016

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-01-08 to 2016-01-13.

12 answers have been received.

Jump to results for question:

  1. Resolutions of 8 January
  2. Gallery of Accessible Web Components [Working Title]
  3. Gallery of Accessible Web Components [Working Title]: Name brainstorming

1. Resolutions of 8 January

summary | by responder | by choice

Please read the 8 January EOWG teleconference meeting minutes. Indicate your approval or concerns with the resolution(s) passed at that meeting. The summary and the link to the full minutes is on the 2016 Minutes wiki page.

Summary

ChoiceAll responders
Results
I was in the teleconference and I'm OK with them! 10
I have reviewed the minutes and agree to the Resolutions passed. 2
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.

Skip to view by choice.

View by responder

Details

Responder Resolutions of 8 JanuaryComments
Howard Kramer
  • I was in the teleconference and I'm OK with them!
Andrew Arch
  • I was in the teleconference and I'm OK with them!
Eric Eggert
  • I was in the teleconference and I'm OK with them!
Brent Bakken
  • I have reviewed the minutes and agree to the Resolutions passed.
 I have read the detailed minutes.
Anna Belle Leiserson
  • I was in the teleconference and I'm OK with them!
Susan Hewitt
  • I was in the teleconference and I'm OK with them!
David Berman
  • I was in the teleconference and I'm OK with them!
George Heake
  • I was in the teleconference and I'm OK with them!
James Green
  • I was in the teleconference and I'm OK with them!
Shawn Lawton Henry
  • I was in the teleconference and I'm OK with them!
Sylvie Duchateau
  • I have reviewed the minutes and agree to the Resolutions passed.
Sharron Rush
  • I was in the teleconference and I'm OK with them!

View by choice

ChoiceResponders
I was in the teleconference and I'm OK with them!
  • Howard Kramer
  • Andrew Arch
  • Eric Eggert
  • Anna Belle Leiserson
  • Susan Hewitt
  • David Berman
  • George Heake
  • James Green
  • Shawn Lawton Henry
  • Sharron Rush
I have reviewed the minutes and agree to the Resolutions passed.
  • Brent Bakken
  • Sylvie Duchateau
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.

2. Gallery of Accessible Web Components [Working Title]

summary | by responder | by choice

Please give us your first impressions of the early mockup of the Gallery of Accessible Web Components [Working Title]. From the requirements analysis:

Make it easy for web developers to find ready-made, accessible components to use in their projects by providing a repository of accessible web components. Components include frameworks, templates and widgets. The user interface of the repository will provide options to sort tagged components for a better findability. Users will have a possibility to provide feedback on every component to ensure a good quality of the components.

More information about the project:

Please consider the following:

  • The links contain content that is not real, some of it isn’t dynamic yet. Expect that links are not working.
  • All layout and/or design treatment is done to give you an impression of the relationship of the different elements on the page.
  • The final design will resemble the new “How to Meet WCAG 2.0”.

Take a look at the example overview and details page.

Summary

ChoiceAll responders
Results
I did look at the requirements and the mockup and put comments into the comment field below. 5
I did look at the requirements and the mockup but don’t have any comments at the moment. 5
I will review it by the date in the comment section below. 1

(1 response didn't contain an answer to this question)

Skip to view by choice.

View by responder

Details

Responder Gallery of Accessible Web Components [Working Title]Comments
Howard Kramer
  • I did look at the requirements and the mockup and put comments into the comment field below.
 I wondered if the icons listing the found components wasn't a bit larger. Perhaps it would be more readable if the results were shown as a vertical list.
Andrew Arch
  • I did look at the requirements and the mockup and put comments into the comment field below.
 Overview
- gridded boxes take up lots of space, will there be a list or table option?
- all looks good otherwise
Details
- looks good (do you have any other options in mind for version info if the iem isn't being managed on github)
Eric Eggert
  • I did look at the requirements and the mockup and put comments into the comment field below.
 [Editor] I’m personally not really convinced that the tiles view works… probably having a tabular overview would be better for this kind of resource.
Brent Bakken I really like the layout of the Details Page. I like that the left navigation remains consistent on that page with all other pages. I also like the title and detailed description in the center content column and then the company, licensing, and contact information on the far right if anyone is more interested in more details.

When conducting a search for "Acme" the results came up, but it would have been nice to see the results by category subheading (and also in the same order as the left side navigation: frameworks, templates, then widgets) and have the thumbnail image as the result feedback.

Looks good so far. Looking forward to seeing further development.
Anna Belle Leiserson
  • I did look at the requirements and the mockup and put comments into the comment field below.
 I'm more used to simple lists (or tables) for this kind of collection. The boxes with large fonts and graphics seem busy and IMO take up more real estate than is needed. That aside, I love the concept.
Susan Hewitt
  • I did look at the requirements and the mockup but don’t have any comments at the moment.
David Berman
  • I did look at the requirements and the mockup but don’t have any comments at the moment.
George Heake
  • I did look at the requirements and the mockup and put comments into the comment field below.
 I am not sure if the icon scheme works because the re=sizing of the icons are not uniform (on my screen (PC) the third one on the right was shorter.
James Green
  • I did look at the requirements and the mockup but don’t have any comments at the moment.
Shawn Lawton Henry
  • I did look at the requirements and the mockup but don’t have any comments at the moment.
 Comments about title/name:
* "Repository" seems like a good word. "Catalog" seems OK, too.
* What are the pros and cons of "library" from a developer's perspective, e.g., is this resource/tool too different from "code libraries" and would be confusing?
* I don't think "Gallery" works.
* I don't think we want "WAI" in the title.
* "Accessibility" may have better SEO thatn "Accessible"?
My ideas in the next answer are "brainstorms", not "suggestions". :-)
Sylvie Duchateau
  • I did look at the requirements and the mockup but don’t have any comments at the moment.
Sharron Rush
  • I will review it by the date in the comment section below.
 Monday Jan 18

View by choice

ChoiceResponders
I did look at the requirements and the mockup and put comments into the comment field below.
  • Howard Kramer
  • Andrew Arch
  • Eric Eggert
  • Anna Belle Leiserson
  • George Heake
I did look at the requirements and the mockup but don’t have any comments at the moment.
  • Susan Hewitt
  • David Berman
  • James Green
  • Shawn Lawton Henry
  • Sylvie Duchateau
I will review it by the date in the comment section below.
  • Sharron Rush

3. Gallery of Accessible Web Components [Working Title]: Name brainstorming

The Gallery of Accessible Web Components needs a good, memorable name. Let’s think about it early in the process.

The current title is “WAI Components Gallery” or “WAI Gallery of Accessible Web Components”. There are some problems with those names:

  1. There is a W3C initiative called web components (also here), which means something completely different. This might be confusing for users.
  2. The names are rather long.
  3. They are not generating easy to remember abbreviations (WCG – too similar to WCAG – or WGAWC – unpronounceable).
  4. Other types of resources might be added to the gallery that are not strictly web components, so we might think of a more open name.

Details

Responder Suggestion 1Suggestion 2Suggestion 3Suggestion 4Suggestion 5Suggestion 6Suggestion 7Suggestion 8Suggestion 9Suggestion 10
Howard Kramer accessible web component repository accessible interface elements accessible user interface components
Andrew Arch catalogue (rather than gallery)
Eric Eggert Accessibility Repository (AR) Accessible Components on the Web (ACW) Accessibility Resources on the Web (ARW) Repository of Accessibility Resources (RAR) Web Accessibility Components List (WACL) Accessible Interface Elements Repository (AIER) Web Accessibility Resources Directory (WARD – probably not a good acronym) Directory of Web Accessibility Resources (DWAR)
Brent Bakken Accessible Component Resource Catalog Component Resource Catalog WAI Component Catalog WAImart - The Component Store (sorry, just had to include it) WAI CompCat - An accessible web component catalog The WAI Component Collection WAI Component Hub WAI Open Components WAI Bank WAI Component Bank
Anna Belle Leiserson WAI Finder for … (Accessible Code Patterns or Accessible Web Components, etc.) WAI Compendium of Code Components [WAI CCC] Compendium of Accessible Code Components
Susan Hewitt Accessible Web Library Accessible Web Code Library Accessible Web Element Library Accessible Web Element Repository Library (or Repository) of Accessible Web Elements Accessible Web Element Cache Accessible Web Code Cache Accessible Web Assests Library Accessible Bits and Bobs
David Berman Accessible Web Components Library Accessible Web Toolkit eAccessibility Elements Gallery
George Heake Gallery of Accessible Internet Tools (GAIT)
James Green Accessible Code Bank Accessible Code Co-Op Accessible Code Library Accessible Code Museum A11y's List WAI C4 (Crowdsourced Code Component Catalog)
Shawn Lawton Henry Repository of Accessibility Resources (ROAR) [works if it is more broad, e.g., including articles] Accessible Web Resources [works if it is more broad] Library of Web Accessibility [works if it is more broad] UI Components for Web Accessibility Web Accessibility Copy & Paste Code [see comments in previous question]
Sylvie Duchateau WAI's accessible Implementation Templates (WAIT) Examples of Components that are accessible and WCAG Compliant (ECAWC) Templates of Accessible Web Content
Sharron Rush

More details on responses

  • Howard Kramer: last responded on 13, January 2016 at 06:44 (UTC)
  • Andrew Arch: last responded on 13, January 2016 at 10:42 (UTC)
  • Eric Eggert: last responded on 13, January 2016 at 13:09 (UTC)
  • Brent Bakken: last responded on 13, January 2016 at 20:15 (UTC)
  • Anna Belle Leiserson: last responded on 13, January 2016 at 20:44 (UTC)
  • Susan Hewitt: last responded on 13, January 2016 at 22:39 (UTC)
  • David Berman: last responded on 13, January 2016 at 23:01 (UTC)
  • George Heake: last responded on 14, January 2016 at 00:47 (UTC)
  • James Green: last responded on 14, January 2016 at 03:15 (UTC)
  • Shawn Lawton Henry: last responded on 14, January 2016 at 14:47 (UTC)
  • Sylvie Duchateau: last responded on 14, January 2016 at 15:11 (UTC)
  • Sharron Rush: last responded on 14, January 2016 at 15:37 (UTC)

Non-responders

The following persons have not answered the questionnaire:

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