- From: Katie Haritos-Shea <ryladog@gmail.com>
- Date: Sun, 24 Jun 2018 19:23:53 -0400
- To: Hilera González José Ramón <jose.hilera@uah.es>
- Cc: Jonathan Avila <jon.avila@levelaccess.com>, Auto-WCAG List <public-auto-wcag@w3.org>
- Message-ID: <CAEy-OxFDahddEeV_7KSZSsc-S5_AAefDSDPq0Z2AXSmia28fzA@mail.gmail.com>
+1 to Makoto! On Sun, Jun 24, 2018, 1:03 PM Hilera González José Ramón <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> > Fecha: 24/6/18 17:07 (GMT+01:00) > Para: Auto-WCAG List <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> 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>: > >> 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> >> wrote: >> >>> I like the idea of using the word “testing” instead of auto >>> >>> >>> >>> Cheers, >>> >>> Gian >>> >>> >>> >>> *From:* Wilco Fiers <wilco.fiers@deque.com> >>> *Sent:* 22 June 2018 8:43 PM >>> *To:* 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> > > https://www.infoaxia.co.jp/ <http://www.infoaxia.co.jp/> > https://weba11y.jp <https://www.facebook.com/weba11y.jp>/ > >
Received on Sunday, 24 June 2018 23:24:45 UTC