Re: Invitation to initial discussion March 17th on potential work on accessibility conformance testing

Dear Wilco

Very sorry for this late reply.
Intention is to return to flow,  now looking possible

I will try to make the next calls and the meet up.

Interestingly, the work of the auto wcag group came up this afternoon in an
informal meeting of a futures thinktank.  I cited it s an example of a bona
guide has roots style effort.

Apologies again for the late notice

And until soon ! ( much catching up to do with all the work you have done,
I will )

John

John
On 17 Mar 2016 08:55, "Wilco Fiers" <wilco.fiers@deque.com> wrote:

> Dear All,
>
> On Monday you received an invitation to participate in a meeting to
> discuss the development of a rule set for normative accessibility
> conformance testing. As promised I'm sending you the details on how to join
> the WebEx call and the agenda for this meeting.
>
> *Auto-WCAG: Conformance Testing*
> Thursday, March 17, 2016 - 4:00 pm
> Europe Time (Amsterdam, GMT+01:00)  |  1 hr 30 mins
>
> *Join WebEx meeting*
> <https://mit.webex.com/mit/j.php?MTID=m8140542dcd2707e2bfa34ae5ae59ef9e>
> Meeting number: 649 967 819
> Meeting password: Please obtain your meeting password from your host.
>
> *Join by phone*
> *+1-617-324-0000 <%2B1-617-324-0000>* US Toll Number
> Access code: 649 967 819CCP:+16173240000x649967819# Mobile Auto Dial:
> +1-617-324-0000,,,649967819#
>
> Add this meeting
> <https://mit.webex.com/mit/j.php?MTID=md74a534e5da0b311e626e4c7bc3f8a75> to
> your calendar. (Cannot add from mobile devices.)
>
> Can't join the meeting? Contact support. <https://mit.webex.com/mit/mc>
>
>
>
>
>
>
>
>
> *Please note: *If you have contacted me about joining the meeting I will
> forward you the password by e-mail. For this meeting we will also be using
> our IRC channel, where you can also get the password if you have not
> received it. The IRC channel is: irc://irc.w3.org:6665/#auto-wcag If you
> do not have an IRC client you can use: http://irc.w3.org
>
> *Agenda*
> 1. Introductions
>
> 2. Problem outline:
> We'll explore what are common problems that have lead to an interest for
> WCAG compliance rules. The aim is to gain a common understanding of what
> the goals will be to work on.
>
> 3. Stakeholders:
> We'll look at who among the participants would be interested to commit
> resources to the initiative. Secondly we'll explore who else should be
> invited to participate.
>
> 4. Organization with W3C:
> What is the best way to organize this within the W3C. Should this work be
> done within a working group? If so, which one. What connections are there
> to other working groups?
>
> 5. How to frame the work process:
> We'll need to discuss the size of this initiative, making sure there can
> be a meaningful result within a reasonable amount of time. The key
> questions here are what must be developed, and in what time frame.
>
> 6. Final thoughts
>
>
> Regards
>
> Wilco Fiers, Judy Brewer, Shadi Abou-Zahra
>
> On Mon, Mar 14, 2016 at 2:34 PM, Wilco Fiers <wilco.fiers@deque.com>
> wrote:
>
>> Dear All,
>>
>> We have been hearing increasing interest in development of a set of rules
>> for normative accessibility conformance testing for WCAG 2.0, rising at
>> least in part from differences in interpretations of conformance with WCAG
>> 2.0, and resulting problems in inter-rater reliability.
>>
>> Since the Automated WCAG Monitoring Community Group ("Auto WCAG CG") has
>> already been working on related issues, we would like to explore the
>> possibility of developing a proposal in the Auto WCAG CG for Recommendation
>> Track work on a set of rules for normative accessibility conformance
>> testing, to be developed within a W3C Working Group once better defined.
>>
>> Depending on people's interest, exploratory work within the Auto WCAG CG
>> could include:
>> - reviewing suitability for normative accessibility conformance testing
>> of a variety of rule sets that have been offered to W3C/WAI for further
>> development;
>> - combining different rule sets within a framework that would focus first
>> on automated testing, but be expandable later to semi-automated and manual
>> tests, and to potential normative extensions and/or future versions of WCAG;
>> - incubating an initial draft specification, possibly to include a
>> normative core and informative test procedures;
>> - developing a proposal for a W3C Working Group, to include:
>>     * a clear problem statement;
>>     * explicit success criteria;
>>     * royalty-free licensing commitments;
>>     * a list of interested parties.
>>
>> Meeting time and logistics:
>> - The first meeting would occur this Thursday, March 17, at 16:00 - 17:30
>> CET (the same time slot as the usual Auto WCAG CG meeting), with likely
>> meetings to follow at two-week intervals.
>> - Because of the daylight savings time change in the US and Canada over
>> the past weekend, please note the time zone correspondences for the meeting
>> this week: <
>> http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160317T16&p1=195&ah=1&am=30
>> >
>> - Depending on expressions of interest, we may adjust the meeting time
>> for future meetings.
>> - Teleconference details to be confirmed based on the number of
>> expressions of interest.
>>
>> If you are interested but unable to attend the initial discussion, please:
>> - Let us know of your potential interest.
>> - If attending the CSUN 2016 Conference in San Diego the following week,
>> please note a related session
>>
>> http://www.csun.edu/cod/conference/2016/sessions/index.php/public/presentations/view/210
>> - Comments, questions and suggestions welcome on the Auto WCAG WG mailing
>> list: public-auto-wcag@w3.org
>>
>> Kind regards,
>>
>> Wilco Fiers, Shadi Abou-Zahra, Judy Brewer
>>
>
>
>
> --
> *Wilco Fiers* - Senior Accessibility Engineer
>
>