Evaluation and Repair Tools Working Group Teleconference

EARL 1.0 Test Suite

http://lists.w3.org/Archives/Public/public-wai-ert/2012Oct/0003.html

http://lists.w3.org/Archives/Public/public-wai-ert/2012Oct/att-0003/EARL_Report.xml

SAZ: combines automatic and semi-automatic test cases
... maybe best to do them as separate test cases?

KV: actually combines failed and cannot tell

SAZ: "<acc:score>60.60</acc:score>", what does that mean?

KV: accessibility score
... not used anymore

SAZ: currently description of the tool rather than of the report
... would need to be a separate assertion

KV: will remove

<earl:Assertion rdf:about="http://www.w3.org/WAI/WCAG20/quickref/#qr-text-equiv-all#1.1.1">

<earl:Assertion rdf:about="id01">

<earl:Assertion rdf:about="#id01">

<kostas> ok

self#id01

SM: rdf:about or rdf:I
... rdf:about or rdf:id

<earl:Assertion rdf:about="#assertion"> <earl:assertedBy rdf:resource="#assertor"/> <earl:subject rdf:resource="http://www.example.org/"/> <earl:test rdf:resource="http://www.w3.org/TR/WCAG20-TECHS/H36"/> <earl:result rdf:resource="#result"/> </earl:Assertion>

SAZ: think rdf:about and rdf:ID seems to be equivalent
... but ID seems more sensisble

SM: will check this

<acc:step>2</acc:step>

SAZ: important to have in the test case?
... not part of EARL

<acc:problematicElement>

http://www.w3.org/TR/EARL10/#pointer

<acc:level>A</acc:level>

<earl:test rdf:about="http://www.w3.org/TR/WCAG20-TECHS/H37#H37-tests">

<acc:level>A</acc:level>

</earl:test>

SAZ: though need to be carefull with that because a technique could map to more than one success criterion that could have more than one level

http://www.w3.org/TR/EARL10/#TestCriterion

SM: could be part of the test result because interpretation of the technique outcome

<kostas> it is better to follow the test criterion

<earl:TestCase rdf:about="http://www.w3.org/TR/WCAG20-TECHS/H36"> <dct:title xml:lang="en">H36</dct:title> <dct:description xml:lang="en">Technique H36 - Using alt attributes on images used as submit buttons </dct:description> <dct:isPartOf rdf:resource="http://www.w3.org/TR/WCAG20-TECHS/"/> <dct:hasPart rdf:resource="http://www.w3.org/TR/WCAG20-TECHS/H36#H36-tests"/> </earl:TestCase>

<earl:TestResquirement rdf:about="http://www.w3.org/TR/WCAG20/@@@successcriterion_ID"> <dct:title xml:lang="en">H36</dct:title> <dct:description xml:lang="en">Technique H36 - Using alt attributes on images used as submit buttons </dct:description> <dct:isPartOf rdf:resource="http://www.w3.org/TR/WCAG20-TECHS/"/> <dct:hasPart rdf:resource="http://www.w3.org/TR/WCAG20-TECHS/H36#H36-tests"/> </earl:TestRequirement>

<acc:tip>

http://www.w3.org/TR/EARL10/#info

<kostas> ok

Accessibility Support Database

http://www.w3.org/WAI/ACT/asd

SAZ: crowd.sourced repository of information about how accessibility features are supported across platform, browsers, and assistive technologies

KV: new resources or only what exists from W3C?

SAZ: tests are new but always based on existing Techniques

<kostas> ok

SAZ: let me know if you have any questions or comments

Website Accessibility Conformance Evaluation Methodology 1.0

http://www.w3.org/TR/WCAG-EM/

SAZ: commenting review period ends this Friday, please send your comments to Eval TF

<kostas> sorry there is a problem with my line

Techniques For Accessibility Evaluation And Repair Tools 1.0

http://www.w3.org/TR/AERT

http://www.w3.org/WAI/ACT/deliverables#eval_tools

SAZ: guidance for evaluation tool developers on how to better support WCAG 2.0, including WCAG-EM