7 Dec 2005


See also: IRC log


Johannes, Shadi, Sandor, Christophe, Chris, CarlosI, Nick


Accessibility Test Suites

<ChrisR> Notes on test suite: http://checker.atrc.utoronto.ca/docs/TestSuiteForHTML.txt

<ChrisR> current test suite for WCAG: http://www.w3.org/WAI/GL/WCAG20/tests/

CR: likes other people to participate in the test suite
... not specific to WCAG 2.0

CR: some tests are common to more guidelines/laws
... idea is: does page conform to guidelines?
... designed for average HTML author, not necessarlity expert
... it's only for HTML content (no flash etc.)
... some are automatic, some require human judgement
... there are no tests yet for color contrast and flicker
... will come when algorithms are stable
... tests are small/atomic
... remove ambiguities (pass or fail?)
... finer in detail than WCAG 1.0 HTML techniques
... but tests map to certain technique

SAZ: what is ERT WG's role in this

CR: have more people review tests and agree on them

SAZ: ERT WG's job is not interpreting WCAG
... harmonizing ways to describe test cases
... feedback on whether tests are ambiguous

CR: important to harmonize checks to produce same results

<Zakim> niq, you wanted to ask who stands behind the testsuite

CR: ERT WG should say, we can / cannot implement these tests

NK: who develops the test suite (CR and ???)

SAZ: what about copyright? documents are on W3C site, but copyright is on University of Toronto

<ChrisR> test suite at WAI: http://www.w3.org/WAI/GL/WCAG20/tests/

CR: documents have W3C license
... in order to change the copyright, lawyer have to be involved -> money

<niq> "W3C .... document use and software licensing rules apply."

CR: part of techniques task force
... staw poll about tests and success criteria

<ChrisR> test process: http://www.w3.org/WAI/GL/WCAG20/tests/ctprocess.html

CR: some have XQuery expression to make automated tests

<ChrisR> complete test suite: http://checker.atrc.utoronto.ca/servlet/ShowCheck

<ChrisR> example: http://checker.atrc.utoronto.ca/servlet/ShowCheck?check=1&lang=eng

SAZ: are XQuery expressions approved by WCAG WG

CR: no

<ChrisR> Can also be translated. Example Italian: http://checker.atrc.utoronto.ca/servlet/ShowCheck?check=1&lang=ita

SAZ: what happens if someone has another expression to test?

CR: WCAG WG have to agree which tests apply to WCAG

<ChrisR> tests can be mapped to other guidelines: http://checker.atrc.utoronto.ca/servlet/ChangeGuideline?lang=eng

CS: there's also BenToWeb test suite
... tests for each success criterion

CR: public?

CS: not yet

SAZ: submit to WCAG WG?

CS: yes

<niq> ChrisR: http://checker.atrc.utoronto.ca/servlet/ChangeGuideline?lang=eng doesn't work for me; just always sends me to Accessibility Test 197 whatever I select

SAZ: WCAG WG's task is development of test suite
... should we develop or should we review?

CR: help in development, but WCAG WG should decide about accepting tests

<niq> I think we're implementing the software.

<niq> If group members want to develop tests e.g. with wcag, that falls outside ERT IMO

JK: we as tool developers can create xpath or xquery expressions based on our interpretation of success criteria / guidelines

SAZ: overlap between WCAG and ERT WGs
... difficult to produce test suite for a still changing specification

CR: create tests based on real world testing, not on specifications

JK: requrement to have tests for each success criteria

SAZ: some BenToWeb people may be interested in test suite work
... there must be a process for creating tests
... any more interested people? NK, SH, CI?
... test suite development task force?

NK: yes

CI: disagree with some already approved tests

<CarlosI> partially

<niq> but that doesn't invalidate the exercise

SAZ: will check with Wendy how to procede
... may result in a joint task force

CR: make sure this is not just for WAI

SAZ: we should not promote development of different accessibility guidelines

<ChrisR> I agree. Let's try to bring them all together.

CS: see 'Understanding WCAG 2.0' document

<niq> :-)

CR: send all accessibility test suites to me

SAZ: no meeting next week, next meeting December 21st

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2005/12/07 19:08:38 $