- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Mon, 25 Jun 2018 13:47:29 +0200
- To: public-auto-wcag@w3.org, Wilco Fiers <wilco.fiers@deque.com>
Note that we will need to formally close this group and start another with the new name. This is not necessarily a bad thing, as we can now probably better describe the purpose and processes of the new group. I'd also like to throw in the mix: "Accessibility Conformance Testing (ACT) Community Group", to match the name of the related W3C spec and effort. After all, I think we now consider this will be a longer-term group that will pre-standardize (incubate) ACT Rules for AGWG. Best, Shadi On 25/06/2018 13:32, Wilco Fiers wrote: > Hey all, > Thanks for the great feedback. I've scheduled an Auto-WCAG retrospective > meeting next week. This topic is on the agenda. I'd like to come out of > that meeting with a poll so that we can do a vote on the question. > > Wilco > > > On Mon, Jun 25, 2018 at 1:25 AM Katie Haritos-Shea <ryladog@gmail.com > <mailto:ryladog@gmail.com>> wrote: > > +1 to Makoto! > > On Sun, Jun 24, 2018, 1:03 PM Hilera González José Ramón > <jose.hilera@uah.es <mailto:jose.hilera@uah.es>> wrote: > > +1 to Testing-WCAG or WCAG-Testing > > > Enviado desde mi teléfono móvil. > > From my mobile phone. > > > -------- Mensaje original -------- > De: Jonathan Avila <jon.avila@levelaccess.com > <mailto:jon.avila@levelaccess.com>> > Fecha: 24/6/18 17:07 (GMT+01:00) > Para: Auto-WCAG List <public-auto-wcag@w3.org > <mailto:public-auto-wcag@w3.org>> > Asunto: Re: Rebranding Auto-WCAG?? > > +1 to Makoto. > > Jonathan > > Sent from my iPhone > > On Jun 24, 2018, at 2:14 AM, Makoto UEKI - Infoaxia, Inc. > <makoto.ueki@gmail.com <mailto:makoto.ueki@gmail.com>> wrote: > >> I like “WCAG-Testing-CG”. >> >> “Accessibility” implies broader meaning than WCAG. This CG is >> about testing for WCAG. >> >> Cheers, >> Makoto >> >> >> 2018年6月24日(日) 2:52 Wilco Fiers <wilco.fiers@deque.com >> <mailto:wilco.fiers@deque.com>>: >> >> Hey all, >> I had the same experience as Judy. Most people I talk to >> about this work is under the impression that we're focused >> on accessibility tooling. Even people that know we've got >> a broader scope still mostly think of standardising >> accessibility tools as being the primary goal for >> Auto-WCAG. While that's certainly how it started, that no >> longer fits with the work that's actually going on. The >> two changes we've made since are these: >> >> 1. Rules no longer describe test procedures. They tell >> "what" to test rather than "how" to test. In that way, >> what Auto-WCAG is doing is rewriting the WCAG criteria to >> be atomic and remove their ambiguities. Rule writing no >> longer is about writing code - how something is coded up >> has become irrelevant, as long as results are consistent. >> >> 2. The distinction between what is automated, >> semi-automated and manual no longer exists in rules. By >> keeping "Auto" in our name, this group keeps implying that >> the work is mostly about automation, rather than being >> about harmonising test methodologies. >> >> I like Gian's suggestion of "testing", so something like a >> "wcag-testing CG" or "accessibility testing CG". >> >> Wilco >> >> On Sat, Jun 23, 2018 at 2:27 AM Gian Wild >> <gian@accessibilityoz.com >> <mailto:gian@accessibilityoz.com>> wrote: >> >> I like the idea of using the word “testing” instead of >> auto____ >> >> __ __ >> >> Cheers,____ >> >> Gian____ >> >> __ __ >> >> *From:* Wilco Fiers <wilco.fiers@deque.com >> <mailto:wilco.fiers@deque.com>> >> *Sent:* 22 June 2018 8:43 PM >> *To:* public-auto-wcag@w3.org >> <mailto:public-auto-wcag@w3.org> >> *Subject:* Rebranding Auto-WCAG??____ >> >> __ __ >> >> Hey all,____ >> >> I wanted to get some thoughts on this. Auto-WCAG was >> originally conceived with the intent to write rules >> for automated tools, and for semi-automated tools. >> Those were two separate categories that we'd write >> separate rules for. With the ACT Rules Format evolving >> the way it did, this distinction has largely gone >> away. This begs the question of: Should we remain the >> Auto-WCAG community group, or is this name no longer >> representative enough of our work that we should >> rebrand?____ >> >> __ __ >> >> I'm curious to hear your thoughts. Should we rename >> the group, and if we do, what should our new name be?____ >> >> __ __ >> >> -- ____ >> >> *Wilco Fiers*____ >> >> Senior Accessibility Engineer - Co-facilitator >> WCAG-ACT - Chair Auto-WCAG____ >> >> ____ >> >> >> >> -- >> *Wilco Fiers* >> Senior Accessibility Engineer - Co-facilitator WCAG-ACT - >> Chair Auto-WCAG >> >> -- >> -- >> <以下、署名> >> >> 株式会社インフォアクシア >> 植木 真 >> <ueki@infoaxia.co.jp <mailto:ueki@infoaxia.co.jp>> >> >> https://www.infoaxia.co.jp/ <http://www.infoaxia.co.jp/> >> https://weba11y.jp <https://www.facebook.com/weba11y.jp>/ > > > > -- > *Wilco Fiers* > Senior Accessibility Engineer - Co-facilitator WCAG-ACT - Chair Auto-WCAG -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Accessibility Strategy and Technology Specialist Web Accessibility Initiative (WAI) World Wide Web Consortium (W3C)
Received on Monday, 25 June 2018 11:47:39 UTC