13 Jan 2009


See also: IRC log


Shadi, CarlosI, Christophe, Michael


Web interface for displaying test samples

<shadi> http://www.w3.org/WAI/ER/tests/Overview

<Christophe> Requirements: http://www.w3.org/WAI/ER/tests/WebInterface/Mockups/design.html

saz: prototype interface (not functional yet)

<shadi> http://www.w3.org/WAI/ER/tests/complete

saz: you can view "all tests" and tool can crawl everything

in the "view for tools" option

cs: worried about a new ID separate from the ones in the XML files
... should table with tests have success criterion shown?

mc: techniques can apply to multiple SC, think it would be confusing to show SC

would rather that be in a search view

<shadi> http://www.w3.org/WAI/ER/tests/view.php?id=123

cs: currrently only one SC per test

<shadi> http://canada.esat.kuleuven.be/bentoweb/tsdtf/xhtml/index.html

cs: able to see XML of test?

saz: the generated version is shown

with links to the other parts

saz: open issue is the ID

mc: don't want semantics in ID, one generated by database is fine; if want the XML one, could expose as another field

saz: problem is that we now have many IDs?

cs: yes, the URI, the ID from the XML, and now the DB one

harder to resolve when someone says "I used ID x"

<shadi> http://www.w3.org/WAI/ER/tests/view.php?id=213

<shadi> http://www.w3.org/WAI/ER/tests/simple

mc: not sure why 3 screens in the search

saz: each screen filters the next, difficult to do in one without a lot of options and scripting

mc: well, at least could be clearer what the steps are; didn't see on first pass through why they needed to be separate

cs: what if someone wants to sort by technique, not by technology?

saz: true, not as intuitive, would have to get to 3rd screen to make selections

<shadi> http://www.w3.org/WAI/ER/tools/simple

saz: could also do it without prefiltering, but easier for user to choose a set of options that yield no results

mc: could use AJAX, or script arrays of data to refine search options as user makes selections, or just accept reporting "no results"

cs: screens could show what your choices were in previous steps, so when you get to end you know why no results

<shadi> http://www.w3.org/WAI/ER/tests/complete.php?sort=id&submit=Sort&view=tools

saz: you can give the TCDL to a compliant tool so it can process metadata

(reduces manual steps in test)

saz: will revise the search interface

<shadi> http://www.w3.org/WAI/ER/tests/WebInterface/Mockups/search.html

<scribe got lost for a while>

<discussion of using short names instead of full titles>

Open action items: http://www.w3.org/WAI/ER/2006/tests/tracker/actions/open

cs: can close actions relating to accessibility support database

need to see if actions to review test samples are still current

asks Carlos I to take a pass

ci: ok

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2009/01/13 22:48:10 $