Minutes for Teleconference on 16 October 2014

Automated WCAG Monitoring Community Group
Teleconference 2014-10-16, 16:00 - 17:00 h (CET)
Attendees:
Birkir, Frank, Hanno, Jesse, Kamyar, Wilco

ITEM 1 - Action items:
https://www.w3.org/community/auto-wcag/wiki/index.php?title=Action_items&direction=prev&oldid=788

Annika updated and combined SC 3.1.1 and SC 3.1.2.
Wilco wrote some test cases for tests from Quail
Wilco sent feedback on H95>"step 2" problem to WCAG working group.


ITEM 2,3 Review SC3-1-1-xml-lang, SC3-1-2-xml-lang
Moved to the next week as Annika is not present in this week meeting.

ITEM 4 Review SC2-4-2-titles-across-pages
https://www.w3.org/community/auto-wcag/wiki/SC2-4-2-titles-across-pages
Birkir is not present so far so move to next weeks.

ITEM 5 Brainstorm auto-wcag communication
What we can to to be more visible and get more contributers:
Katie suggested to join "Web for all" conference (May 2015 Italy).
Sharron suggested joining TPAC.
Birkir suggested the CSUN conference 2015.

Thoughts on what kind of subjects people are interested in a conference
about accessibility:
Hanno: We should promote automated testing.

Jesse: unless the tool fits into their normal toolchain and easy to
integrate, then it is not going to get used. The best you might get is
someone running some tests at the end of the project.
Another issue is debuggability, being able to get a failure and trace
the fact to the cause to fix it. In Qauil we try to address this problem
by associating issues with DOM element and then associating information
about the test with the report about it.

The main development focus about Quail for the next 6 month: to address
how do we build quail in something like Travis or Karma or one of these
automatic test running suites. So we can give real-time debug on
development as changes are committed. The behavior is to be determined
by adding some assertions that developers can add to their unit tests
and iteration tests.
So we add tools and integrated them to the work flow of the developers
and building the tools against the the system they already use.

Birkir: The work flow of fireeyes: we do this as a combination two parts:
1. WorldSpace: server based version. it can automate scans, scan all the
pages in the project, create a project on the server. you say these are
URLs that are included in this project and you use patterns and
definitions to create a project and then you specify the scan that you
want, rules like "I want wcag 2 level AA ".
2. The user download and setting up the fireeyes (which is a plugin for
firebug / firefox). Then he points this fireeyes plugin in the browser
to the project the he created on the Worldspace server to make sure he
use the same rules. For example, use can say: for my company if the alt
tag of this image doesn't have trademark in it, then an error should be
called becasue we have decided in this company that trademark should be
in the alt tag.
Confusing for the small projects, very nice for big projects. if you
modify a little bit of a page, developer has to run this on that page.
They are very much look like unit tests because we want to as much as
possible integrate accessibility with quality assurance.

Birkir on CSUN conference: it is a 40 minutes talk (co presenter is
Katie) about why do you want autowcag. what's cool of going selectively
through every single success criteria. Selectors and everything you need
to implement your own test and your own tool.

Jesse: I have been invited to a keynote wordpress camp in Pennsylvania
in Feb to talk about quail but I can talk about autowcag group as well.

Hanno: I found  Continuous Integration and Testing Conference which
sounds interesting.

Birkir: on the website I like to have a very short blog. say when we
tackle a success criteria, write thoughts on challenges and say this is
what we discussed in the meeting and we can twit that link to the
community and ask for [continues] contribution. Wilco: it would be nice
if we can connect developers through our work.

Hanno: Google has accessibility tools we can ask them to join. Birkir
they have accessibility add ons tool but the tool itself is inaccessible.
Jesse: I have a contact with Shawn Lauriat, he runns the team that  does
the accessibility development for Google Docs.

Action on Wilco: Send Email to Jesse about the group and work references
to be used for the Google Docs contact.

Action on Birkir: Start a twitter account.

SUMMARY OF ACTIONS:
https://www.w3.org/community/auto-wcag/wiki/index.php?title=Action_items&direction=next&oldid=708

Received on Thursday, 30 October 2014 14:12:57 UTC