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+EOsurvey@w3.org
This questionnaire was open from 2016-03-04 to 2016-03-09.
8 answers have been received.
Jump to results for question:
summary | by responder | by choice
Please read the 04 March EOWG teleconference meeting minutes or summary. Indicate your approval or concerns with the resolution(s) passed at that meeting.
Choice | All responders |
---|---|
Results | |
I was in the teleconference and I'm OK with it! | 5 |
I have reviewed the minutes and agree to the Resolution as passed. | 4 |
I have reviewed the minutes but have concerns with the Resolution 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.
Responder | Resolution of 04 March 2016 | Comments |
---|---|---|
Andrew Arch |
|
|
Brent Bakken |
|
|
Eric Eggert |
|
|
Shawn Lawton Henry |
|
|
James Green |
|
|
Susan Hewitt |
|
|
Sharron Rush |
|
|
Howard Kramer |
|
Choice | Responders |
---|---|
I was in the teleconference and I'm OK with it! |
|
I have reviewed the minutes and agree to the Resolution as passed. |
|
I have reviewed the minutes but have concerns with the Resolution and I explain them below. | |
I have not read the minutes yet, and have put the date for my review into the comments box. |
At this stage, we have finalized the visuals and general tenor of all video scripts. However, there is still some room to refine the narration as long as it does not change the meaning or impact the visuals. That is, only purely editorial, word-smithing, and copy-editing is welcome.
Please review All video scripts (1-10) and add any comments in GitHub as new issues. If you are not comfortable with GitHub, please add your comments below.
Please note specifically the following aspects in your review:
Choice | All responders |
---|---|
Results | |
I reviewed it and have no comments on the narration! | 2 |
I am pretty happy with the revised narration but suggest you to consider my comment (at the discretion of the Task Force). Suggestion only, not a show stopper - in GitHub or below. | 4 |
I do have a *strong* (showstopping) objection and have commented in GitHub or below. | 1 |
I didn't get to it; I will pass on commenting on the document and accept the decisions of the Group. |
(1 response didn't contain an answer to this question)
Responder | Showcase Examples with Videos | |
---|---|---|
Andrew Arch | ||
Brent Bakken | I am pretty happy with the revised narration but suggest you to consider my comment (at the discretion of the Task Force). Suggestion only, not a show stopper - in GitHub or below. | Added a comment to Issue 109. Mild comment, okay with group decision. |
Eric Eggert | I reviewed it and have no comments on the narration! | |
Shawn Lawton Henry | I am pretty happy with the revised narration but suggest you to consider my comment (at the discretion of the Task Force). Suggestion only, not a show stopper - in GitHub or below. | I reviewed and commented on the issues linked above. I did not get to a thorough review of all of the scripts. I'd need more time. |
James Green | I am pretty happy with the revised narration but suggest you to consider my comment (at the discretion of the Task Force). Suggestion only, not a show stopper - in GitHub or below. | I submitted https://github.com/w3c/wai-showcase-examples/pull/121, https://github.com/w3c/wai-showcase-examples/issues/122, and added my thoughts to https://github.com/w3c/wai-showcase-examples/issues/109. |
Susan Hewitt | I am pretty happy with the revised narration but suggest you to consider my comment (at the discretion of the Task Force). Suggestion only, not a show stopper - in GitHub or below. | My comments in Github on Issue 109 are important but I'm not the only one chiming in. I'm sure the TF will consider everyone's comments. |
Sharron Rush | I do have a *strong* (showstopping) objection and have commented in GitHub or below. | Catch phrase must be short, memorable and repeated, don't think we are there yet. |
Howard Kramer | I reviewed it and have no comments on the narration! |
summary | by responder | by choice
'Showcase Examples with Video' is what we have used to reference this resource. However, it is more than just video. Consider that this asset is a series of vignettes about the impact and benefits of web accessibility with accompanying text and links to other resources. Please read the resource title discussion in the minutes of 04 March and add your suggestions or ideas in GitHub or below. Feel free to open a new issue or add to the existing issue disussing the resource URL and title: What to link to - issue #8 Thanks!
Choice | All responders |
---|---|
Results | |
I submitted to GitHub | 3 |
I included comments below. | 1 |
I am out of ideas and have nothing to add at this time. Send me a list of titles and let me vote. | 3 |
(1 response didn't contain an answer to this question)
Skip to view by choice.
Responder | Name that showcase with video resource! | Comments |
---|---|---|
Andrew Arch | ||
Brent Bakken |
|
|
Eric Eggert |
|
|
Shawn Lawton Henry |
|
|
James Green |
|
|
Susan Hewitt |
|
|
Sharron Rush |
|
I submitted ideas in an earlier survey and am looking for something along the lines of "Web Accessibility - what it is, why it matters" |
Howard Kramer |
|
I still like "Experience Web Accessibility in Action" or "Web Accessibility in ACTION: Benefits and Impacts" |
Choice | Responders |
---|---|
I submitted to GitHub |
|
I included comments below. |
|
I am out of ideas and have nothing to add at this time. Send me a list of titles and let me vote. |
|
summary | by responder | by choice
Thanks to the volunteers a wide range of UI Components are getting submitted. Thanks for that!
A few questions have come up around the data organization, mainly about where to put Themes for content management systems. Just to recap, currently we have the following three categories (or buckets) to sort UI components into:
Proposal: Add Themes.
Rationale: Themes are tied to CMS solutions. They are more complex than templates which are more static.
Considerations:
Choice | All responders |
---|---|
Results | |
I support adding “Themes”. | 5 |
I don’t support think we should add “Themes” for the reasons outlined below. | 1 |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | [AUICL]: Accessible UI Components List – Add Themes category | Comments |
---|---|---|
Andrew Arch |
|
|
Brent Bakken |
|
Support Editors discretion here. |
Eric Eggert | [Editor] | |
Shawn Lawton Henry | ||
James Green |
|
|
Susan Hewitt |
|
I don't think this category would have enough resources to justify it, partly for the reasons listed above. |
Sharron Rush |
|
|
Howard Kramer |
|
Choice | Responders |
---|---|
I support adding “Themes”. |
|
I don’t support think we should add “Themes” for the reasons outlined below. |
|
summary | by responder | by choice
Regardless of the changes above, there are some other considerations:
What shall we do with small examples of code that are beneficial to learn how to make some specific things accessible. For example, on blog posts and codepen.io there are some nice accessibility approaches that can’t be clearly placed in one of the categories (Widgets, Frameworks, Templates or Themes) in the tool right now.
Proposal: Add a category “Snippets” or “Demos”.
Rationale: Sometimes one just needs a hint or an example to learn how to implement a technique. This category can be useful to find examples and would also lower the barrier for entry as those examples are much easier to create than full-fledged widgets and can also be specific to a certain problem.
Choice | All responders |
---|---|
Results | |
I support adding such a category. I’d prefer the name “Snippets”. | 4 |
I support adding such a category. I’d prefer the name “Demos”. | |
I support adding such a category. I don’t have a name preference. | 2 |
I don’t support adding the category, see comments below. |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | [AUICL]: Accessible UI Components List – Add Snippets or Demos category | Comments |
---|---|---|
Andrew Arch |
|
I like "snippets" but suspect it won't translate well |
Brent Bakken |
|
I have a mild preference to using the term Snippets over Demos. |
Eric Eggert | [Editor] | |
Shawn Lawton Henry | ||
James Green |
|
|
Susan Hewitt |
|
|
Sharron Rush |
|
|
Howard Kramer |
|
Choice | Responders |
---|---|
I support adding such a category. I’d prefer the name “Snippets”. |
|
I support adding such a category. I’d prefer the name “Demos”. | |
I support adding such a category. I don’t have a name preference. |
|
I don’t support adding the category, see comments below. |
summary | by responder | by choice
While researching UI Components, it quickly became apparent that there are few that identify themselves as templates. templates are usually part of themes or frameworks nowadays or used as a intermediate deliverable while producing (a theme for) a website
Proposal: Remove “Templates”.
Rationale: Templates seem to sit in-between themes and frameworks but the term seems not to be used often anymore. They are mostly very simple frameworks.
Choice | All responders |
---|---|
Results | |
I support removing Templates. | 6 |
I don’t support removing Templates. |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | [AUICL]: Accessible UI Components List – Remove “Templates” category | |
---|---|---|
Andrew Arch |
|
|
Brent Bakken |
|
Support Editors discretion here. |
Eric Eggert | [Editor] | |
Shawn Lawton Henry | ||
James Green |
|
|
Susan Hewitt |
|
|
Sharron Rush |
|
|
Howard Kramer |
|
Choice | Responders |
---|---|
I support removing Templates. |
|
I don’t support removing Templates. |
summary | by responder | by choice
The participation of individuals has been incredibly valuable for the development of the resource. If you haven’t had a chance to look into it, watch this “how to submit” video (password: eowgnow). (I have exported the video with a louder volume.)
Then head over to the Accessible UI Components List and submit a component. You need to login with your W3C account.
Please note below if you have any thoughts or run into any problems while submitting.
Choice | All responders |
---|---|
Results | |
I did submit a component.Find my observations below! | 3 |
I didn’t get to it yet, but I expect to get to it by [indicate date below]. | 3 |
(2 responses didn't contain an answer to this question)
Skip to view by choice.
Responder | [AUICL]: Accessible UI Components List – Submit a UI Component | Comments |
---|---|---|
Andrew Arch | ||
Brent Bakken |
|
I have watched the video and will try to submit a component by 11 March. |
Eric Eggert |
|
[Editor] |
Shawn Lawton Henry | ||
James Green |
|
March 18 |
Susan Hewitt |
|
Before CSUN |
Sharron Rush |
|
At the time, I was unable to add a new vendor - that seems to have been fixed, thanks. |
Howard Kramer |
|
Choice | Responders |
---|---|
I did submit a component.Find my observations below! |
|
I didn’t get to it yet, but I expect to get to it by [indicate date below]. |
|
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
.