W3C

Evaluation and Repair Tools Working Group Teleconference

08 Jan 2014

See also: IRC log

Attendees

Present
Shadi, Samuel, Carlos
Regrets
Chair
Shadi
Scribe
Shadi

Contents


Status of WCAG-EM

latest Editor Draft is always here: http://www.w3.org/WAI/ER/methodology/

Eval TF still addressing comments on the previous Editor Draft

expect to come back to ask for approval for publication next week or the week after

Discussion of draft AERT (working title)

latest Editor Draft is always here: http://www.w3.org/WAI/ER/WD-AERT/ED-AERT

SAZ: looking much better, thanks for your work on it!
... but need to wrap it up by August, so need to assign much more time to it in the next period

CV: worked more on clarifying the abstract and framing

http://lists.w3.org/Archives/Public/public-wai-ert/2014Jan/0002.html

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

SAZ: on Samuel's first comment, in WCAG-EM for example we moved towards listing "purposes" rather than "audiences"

CV: think request was from Samuel

SM: yes, did suggest that but agree to going towards tasks rather than roles
... my point relates to the fact that we say the document can be used for selection purposes and procurers seem important
... but can still organize by task rather than by role

SAZ: might also be better to separate "audience"/"purpose" from "scope"

RESOLUTION: change "audience" approach to "purpose" or "task"-based approach, and separate from "scope"

CV: partially agree with Samuel's second comment
... think technically possible but not seen use of SAX

SM: proposing to use XML parsed entities as a more generic term to cover DOM, SAX, and others

CV: XML parsed entities is a subset of DOM
... DOM also not necessarily restricted to XML

SM: can live with DOM

http://www.w3.org/WAI/ER/WD-AERT/ED-AERT20131202#fragments

[[To test such resources, the tool should generate a DOM document fragment]]

-> [[To assess such document fragments, evaluation tools need to be able to process document fragments to test them]]

-> [[Evaluation tools need to be able to process document fragments. Usually this is done by creating a DOM tree from the document fragment that is then tested.]]

-> [[Evaluation tools need to be able to process document fragments. Usually this is done by creating a DOM fragment from the document fragment that is then tested.]]

<carlos> https://developer.mozilla.org/en-US/docs/Web/API/DocumentFragment

<carlos> http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-B63ED1A3

[[Nowadays, it is typical in Content Management Systems the generation of fragments of HTML documents that are aggregated into templates to generate a website]] -> [[Many websites are generated dynamically by combining templates with snippets of code that are created by website authors. Some evaluation tools can be integrated into CMS and IDE tools to check these snippets as website authors create them. Usually this is done by creating DOM document fragments from the

se snippets.]]

[[Some tools are able to filter the accessibility tests according to their relevance to the document fragment]]

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2014-01-14 16:07:34 $