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 address: shawn@w3.org
This questionnaire was open from 2018-04-06 to 2018-04-17.
6 answers have been received.
Jump to results for question:
summary | by responder | by choice
Please read or skim this week's teleconference meeting minutes. Indicate your approval or concerns with the minutes and resolution(s) passed at that meeting. The summary and the link to the full minutes is on the 2018 Minutes wiki page.
If you missed the teleconference, please indicate on the wiki page that you read the minutes — after [done], add your name and date.
Choice | All responders |
---|---|
Results | |
I was in the teleconference and I don't have any comments on the Resolutions or minutes. | 3 |
I have reviewed the minutes and agree to the Resolutions passed. | 1 |
I have reviewed the minutes but have concerns with the minutes or Resolutions, and I explain them below. | 2 |
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 | Minutes and Resolutions from Teleconference | Comments |
---|---|---|
Brent Bakken |
|
|
Laura Keen |
|
|
Sylvie Duchateau |
|
|
Vicki Menezes Miller |
|
|
Eric Eggert |
|
Re: Ra11y Matrix I don’t feel strongly about the “A11y” part of the word, but I wonder if 'Ra11y' does a good job of representing the resource. Even if I know the a11y abbreviation, it is unclear what a Raccessibility Matrix would feature. I think we could be much simpler and just call it something like “Accessibility Roles Matrix” with an A11Y-Roles abbreviation. Just food for thought. |
Shawn Lawton Henry |
|
Re: "Ra11y Matrix" While "a11y" is a common abbreviation *within* the field, it is very jargony and thus exclusive-cluby. Also, in many fonts, one cannot distinguish between a-one-one-y and a-l-l-y ; that is, the number 1 or the lowercase letter L. Also, "a11y" is hard for some people to process, including some people with certain cognitive disabilities. (This lack of clarity is even more pronounced in "Ra11y" because it is like the word "rally".) For these and other reasons, I think we do not want to use "a11y" in the name of a significant project, especially one intended for people who aren't accessibility insiders. Less importantly, I think "Ra11y Matrix" doesn't communicate what it is. Maybe I'm missing something, but "Matrix" doesn't mean anything to me. I think it needs "Roles" in there. <joke>maybe Accessibility Roles and Responsibilities Guidance (ARRG)</joke> I think it would be good to have a brainstorming session about this when people are up for it. (maybe "over drinks" in Austin in May?) Usually when EOWG takes a little time to work together, we come up with a solution that really "sings" and fits well. Note that the descriptions for the roles themselves might end up being very useful throughout W3C work, such as for "Silver" (next gen accessibility guidelines) -- so it'd be good to have a project title that's not limiting. /me re-reads the minutes... I see "just a working title for now and can finalize as project develops". I'd like to share my thoughts, yet am OK with Ra11y Matrix as a working title if others want to stick with that. I do hope we revisit before Ra11y Matrix gets ingrained. ------- Re: "We are in beta release now and by the week of the 16th we will do the full release (as currently planned and understood.) Then will need to do outreach." Correction: We hope to have a revised/updated beta the week of 16 April. We hope to replace the existing site later in April -- although we might go into May to give people more time to get used to the new design in the beta. ------- Re: "Laura: I was curious why we have not announced the beta version. Did we decide we did not want to get that wide feedback?" We announced it on 15 March: * WAI IG e-mail: https://lists.w3.org/Archives/Public/w3c-wai-ig/2018JanMar/0275.html * EOWG e-mail: https://lists.w3.org/Archives/Public/w3c-wai-eo/2018JanMar/0053.html * Tweet: https://twitter.com/w3c_wai/status/974351936358158336 After we address known issues, we plan to do more announcements and promotion of the beta. Per above, that might be late the week of 16 April. |
Choice | Responders |
---|---|
I was in the teleconference and I don't have any comments on the Resolutions or minutes. |
|
I have reviewed the minutes and agree to the Resolutions passed. |
|
I have reviewed the minutes but have concerns with the minutes or 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. |
summary | by responder | by choice
Over the next few months a small team of EOWG participants will be focusing work on providing editorial contributions for the Understanding Documents for new 2.1 Success Criteria. This team will be working on a weekly basis reading draft content and providing editorial recommendations to the Accessibility Guidelines Working Group. Work will begin shortly.
Read meeting minutes on this topic for more detail concerning the time and effort of this work.
If interested, we invite you to join this important focused work over the next few months.
Choice | All responders |
---|---|
Results | |
I would like to commit my time to this project. Please include me when we get started. | 2 |
I might be interested. I would like more detailed information of time and effort. | 1 |
I am not interested, or don't have the time to be an editor of the Understanding WCAG 2.1 Documents. | 3 |
Skip to view by choice.
Responder | Understanding WCAG 2,1 Documents - Editorial Contributor | Comments |
---|---|---|
Brent Bakken |
|
|
Laura Keen |
|
|
Sylvie Duchateau |
|
|
Vicki Menezes Miller |
|
It all depends on the time required. I have an intense project between now and end May. |
Eric Eggert |
|
No time. Totally interested, but no time. *sadface* |
Shawn Lawton Henry |
|
Choice | Responders |
---|---|
I would like to commit my time to this project. Please include me when we get started. |
|
I might be interested. I would like more detailed information of time and effort. |
|
I am not interested, or don't have the time to be an editor of the Understanding WCAG 2.1 Documents. |
|
Feel free to put here things such as:
(Note that the results of this survey are available publicly, so what you put here can be seen by all. :)
Work for upcoming EOWG teleconferences: If you have upcoming work, please describe what you want to bring to the group in the comment field below. Send any draft material to public-eo-plan@w3.org by Tuesday if possible.
Please plan to join the EO-Planning meeting to prepare for Friday EOWG meeting:
Wednesday- 8am CT / 9am ET / 3pm CET
Teleconference connection info (requires W3C login permission)
Responder | Other Information to Share |
---|---|
Brent Bakken | |
Laura Keen | |
Sylvie Duchateau | |
Vicki Menezes Miller | |
Eric Eggert | Working on the redesign over the next few days. Hope to launch it soon! |
Shawn Lawton Henry |
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
.