w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire Auto-WCAG Renaming
The results of this questionnaire are available to anybody.
This questionnaire was open from 2018-07-23 to 2018-08-20.
15 answers have been received.
Jump to results for question:
1. Naming Preferences
This brings us to the big question: What should the name for the Auto-WCAG community group be?
Below are some suggestions. Please rank each on a scale from 1 to 5, where 1 is least preferred and 5 is most preferred. You can assign the same value to any number of suggestions, for example if you like several equally well. You can also make further suggestions in the comments field, or share further thoughts.
Summary
| Choice | All responders | |||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | No opinion | |
| Auto-WCAG CG (unchanged) | 7 | 2 | 1 | 5 | ||
| ACT Rules CG | 3 | 4 | 2 | 3 | 2 | 1 |
| WCAG Testing CG | 3 | 4 | 1 | 4 | 3 | |
| WCAG ACT Rules CG | 1 | 2 | 7 | 3 | 2 | |
| Accessibility Testing CG | 1 | 2 | 1 | 5 | 4 | 2 |
| Other (please specify below) | 1 | 14 | ||||
Averages:
| Choices | All responders: |
|---|---|
| Value | |
| Auto-WCAG CG (unchanged) | 1.40 |
| ACT Rules CG | 2.79 |
| WCAG Testing CG | 3.50 |
| WCAG ACT Rules CG | 3.92 |
| Accessibility Testing CG | 3.69 |
| Other (please specify below) | 5.00 |
Details
| Responder | Auto-WCAG CG (unchanged) | ACT Rules CG | WCAG Testing CG | WCAG ACT Rules CG | Accessibility Testing CG | Other (please specify below) | |
|---|---|---|---|---|---|---|---|
| Jonathan Avila | 1 | 2 | 5 | 4 | 3 | No opinion | |
| Gian Wild | 1 | 2 | 3 | 4 | 5 | No opinion | |
| Ken Petri | 2 | 4 | 5 | 4 | 2 | No opinion | |
| Charles Hall | No opinion | No opinion | No opinion | No opinion | 5 | No opinion | See comment #4 |
| Bryn Anderson | No opinion | 3 | 4 | 5 | No opinion | No opinion | |
| Katie Haritos-Shea | No opinion | 1 | 3 | 2 | 4 | 5 | W3C Accessibility Testing CG (this name would allow for Silver) |
| Makoto Ueki | 1 | 1 | 5 | 4 | 1 | No opinion | If Silver is also within this scope, my preference would be changed as WCAG will no longer exist in the future. If yes, +1 to Katie's suggestion. |
| Jens Pelzetter | 2 | 2 | 3 | 4 | 4 | No opinion | |
| Jey Nandakumar | No opinion | 5 | No opinion | 5 | No opinion | No opinion | |
| JOSE HILERA | No opinion | 5 | No opinion | No opinion | 4 | No opinion | |
| Wilco Fiers | 1 | 4 | 2 | 3 | 5 | No opinion | |
| Jedi Lin | 3 | 3 | 3 | 4 | 5 | No opinion | |
| Kasper Isager Dalsgarð | 1 | 1 | 2 | 4 | 4 | No opinion | |
| Anne Thyme Nørregaard | 1 | 4 | 2 | 5 | 2 | No opinion | |
| Jean Kaplansky | 1 | 2 | 5 | 3 | 4 | No opinion |
2. Transitioning
It is not technically possible to completely rename a community gruop. The group has a fixed URLs on the W3C site, and a mailinglist with an archive. This leaves one of two options. Either we close the existing group and start a new one, or we keep the group, change as much as we can, accepting that the mailing list and W3C URLs are going to remain unchanged. Closing the group would mean a disconnect in our archive. We'd have to get the group approved again, and everyone would have to reregister (at a chance of losing a lot of participants). Either one would be a lot of work, so that's not a consideration.
So than the question is: How do we do the renaming technically:
Summary
| Choice | All responders |
|---|---|
| Results | |
| Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | 8 |
| Close the group completely and open a new one from scratch | 5 |
| Keep the group (if you voted "Unchanged" before) |
(2 responses didn't contain an answer to this question)
Details
| Responder | Transitioning | Rationale |
|---|---|---|
| Jonathan Avila | ||
| Gian Wild | Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | |
| Ken Petri | Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | |
| Charles Hall | Close the group completely and open a new one from scratch | Limitations of technology should not be a constraint on meaningful work. If there is technical debt, solve it. If there are manual tasks to clone and migrate archives, solicit volunteers for the effort. |
| Bryn Anderson | ||
| Katie Haritos-Shea | Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | |
| Makoto Ueki | Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | |
| Jens Pelzetter | Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | |
| Jey Nandakumar | Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | |
| JOSE HILERA | Close the group completely and open a new one from scratch | It can be an opportunity to confirm the actual interest of the current members of Auto-WCAG, because there are 103 members, but very few really participate. |
| Wilco Fiers | Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | |
| Jedi Lin | Keep the infrastructure of the exiting group (url, mailinglist) but change the name and GitHub repo | |
| Kasper Isager Dalsgarð | Close the group completely and open a new one from scratch | |
| Anne Thyme Nørregaard | Close the group completely and open a new one from scratch | |
| Jean Kaplansky | Close the group completely and open a new one from scratch | Rebranding requires more than changing the name of a group. I realize that it creates some backend work for people to migrate customizations (e.g. github Kanban). Keeping part of the paths with the old name around will be confusing to new members who weren’t here for the name change and other non-participants who are interested in the work of the group. Navigating all of the WAI and ACT pages out there is confusing now. We shouldn’t propagate the confusion if we have a choice. |
3. Other Thoughts?
Please feel free to share any further thoughts and considerations on this topic.
Details
| Responder | Other Thoughts? |
|---|---|
| Jonathan Avila | |
| Gian Wild | |
| Ken Petri | |
| Charles Hall | The name should reflect the scope AND have longevity. As the WCAG acronym may change with Silver (not strictly content focused or explicitly web), AND the conformance model may change with Silver, this CG would need to change the name again. |
| Bryn Anderson | |
| Katie Haritos-Shea | |
| Makoto Ueki | |
| Jens Pelzetter | |
| Jey Nandakumar | |
| JOSE HILERA | |
| Wilco Fiers | |
| Jedi Lin | |
| Kasper Isager Dalsgarð | |
| Anne Thyme Nørregaard | |
| Jean Kaplansky |
More details on responses
- Jonathan Avila: last responded on 23, July 2018 at 13:44 (UTC)
- Gian Wild: last responded on 23, July 2018 at 13:50 (UTC)
- Ken Petri: last responded on 23, July 2018 at 14:11 (UTC)
- Charles Hall: last responded on 23, July 2018 at 14:17 (UTC)
- Bryn Anderson: last responded on 23, July 2018 at 14:43 (UTC)
- Katie Haritos-Shea: last responded on 23, July 2018 at 17:46 (UTC)
- Makoto Ueki: last responded on 24, July 2018 at 03:34 (UTC)
- Jens Pelzetter: last responded on 24, July 2018 at 10:54 (UTC)
- Jey Nandakumar: last responded on 24, July 2018 at 22:26 (UTC)
- JOSE HILERA: last responded on 25, July 2018 at 12:16 (UTC)
- Wilco Fiers: last responded on 29, July 2018 at 10:14 (UTC)
- Jedi Lin: last responded on 9, August 2018 at 06:04 (UTC)
- Kasper Isager Dalsgarð: last responded on 9, August 2018 at 07:41 (UTC)
- Anne Thyme Nørregaard: last responded on 9, August 2018 at 09:56 (UTC)
- Jean Kaplansky: last responded on 9, August 2018 at 15:18 (UTC)
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