W3C

Evaluation and Repair Tools Working Group Teleconference

09 Oct 2014

See also: IRC log

Attendees

Present
Shadi, Samuel, Carlos
Regrets
Emmanuelle
Chair
Shadi
Scribe
Shadi

Contents


Samuel's Comments

[[2.1.1. Markup formats: "ability to build a Document Object Model ( DOM ) [ DOM ] according to the different specifications, that includes styles ( CSS ), scrips (JavaScript) and other media (see below), which can then be parsed and analyzed:" Current wording seems to read that DOM is built according to CSS, scripts and media. While this is true, I'm not sure if this clearly conveys what is expected.]]

SAZ: complex sentence

SM: resources are related but not part of DOM

SAZ: is "according to the different specifications" important? all resources have different versions

CV: DOM level is relevant

"ability to render the content according to the Document Object Model (DOM), including all associated resources, such as the CSS, scripts, media, and others."

"Note that the particular version ("Level") of the DOM has significant impact on the rendering, and is relevant to consider as part of this tool feature."

[[2.2.5 Emulating how people with disabilities experience the web: is this exactly an "awareness raising component"? They help emulating different contexts of use (think of e.g. change your system to high-contrast mode to check how it will be seen in that mode).]]

SM: not really emulating the experience of a person
... just showing some contexts of use
... changing color contrast does not mimic the feeling of a person with color-blindness
... it just highlights some of the issues

CV: agree title needs changing

SM: tools can also identify barriers, so they are evaluation features

CV: agree

<samuelm> https://github.com/w3c/w3c-waet/issues/66

<samuelm> http://www.w3.org/WAI/ER/tracker/actions/149

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2015/03/21 10:12:46 $