Document: http://www.w3.org/WAI/ER/2005/03/scenarios.html
<Andrew> Chaals: lets start with existing propopsed lists
<Andrew> http://lists.w3.org/Archives/Public/public-wai-ert/2005Feb/0015.html
<Andrew> Also present: Katie Hairtos-Shea
<Andrew> Chaals: 8 scenarios in emailed list; what about #9 multi-lingual usage
<Andrew> Chaals: rather, supporting multiple languages
<chaalsgrr> http://lists.w3.org/Archives/Public/public-wai-ert/2005Feb/0009.html
<Andrew> Also present: Andrew Kirkpatrick
<chaalsgrr> Shadi's list of scenarios sent to the mailing list: http://lists.w3.org/Archives/Public/public-wai-ert/2005Feb/0015.html
<chaalsgrr> The stuff in the spec already: http://www.w3.org/TR/EARL10/#user-scenarios
Document: http://www.w3.org/WAI/ER/2005/03/requirements.html
<chaalsGrr> Dropping item on user requirements for document. We think that we are not ready to pin it down, and can get more feedback on the shape of a spec when we have more of the spec in place.
<chaalsGrr> Need an editor, in order to have a draft spec. CMN offers to do it, but we will discuss on the list before deciding.
Document: http://www.w3.org/WAI/ER/2005/03/issues.html
CMN Issue: The current draft has a schema that is not valid. Fixing that is easy (see my mail http://lists.w3.org/Archives/Public/public-wai-ert/2005Mar/0003.html with a valid version of the current schema)
SAZ: If there is an identified problem in a page and the page changes, what happens to that report? How do we deal with this?
CMN (continued) we could decide to publish a minimally changed draft very soon, or we could let it roll on for a few months...
AWK So if a page changes, do we have the hope that we can still find an error that was picked uyp efore without retesting?
CMN Yep. If the test was done manually by someone not around now, it is expensive to get it redone.
I sent my repair tool scenario to the list: http://lists.w3.org/Archives/Public/public-wai-ert/2005Mar/0005.html
some more work on scope... noted by SAZ
SAZ, what do people think of splitting document in two - a more reference document and a general guide thing...
scribe: and leave the RDF stuff out altogether and point people to existing documentation on RDF.
AMJA, KHS, CMN agree that this is a good idea
====locating errors
SAZ Need more than line nubmers?
CMN Should list the possible solutions
CMN Line numbers are easy for tools to maintain as they change the page. But they break under hand editing
SAZ There is a problem of what exactly you refer to with a line number - how do you identify a table, or a part of a table, or...
<Ryladog> testing
=== existing tool page
CMN Would be good to be able to sort according to the things that can be tested (e.g. WCAG levels? particular tests?)
AMJA sort according to how new an entry is
SAZ have a simple and an advanced search
AWK We have language already
SAZ By support for technologies
CI can we sort by licensing - free/commercial?
<Andrew> consider "how new an entry is" vs "when the tool was updated"
(long discussion about whether or not we can list price information)
CMN When I maintained the document it noted whether things were free or not.
Kerstin Goldsmith joined
KG: but not keeping prices?
CMN/AMJA Nope. Too hard to keep that accurate
Coffee break.
After the break we meet in grand ballroom (where we had lunch)
oh, that's after 1530
Visitors: Jack, Wayne, Charmane, Justin, Chuck, Alan, Judy, Shawn, Helle, Sylvie, Henk, Harvey
Document: http://www.w3.org/WAI/ER/2005/03/tools.html
being scribed into the EO channel...
<AWK> How about: A user who prefers to avoid flickering images utilizes a browser-plug in that modifies the content of a web page to prevent the display of flickering images when the EARL document linked to a page indicates that such images exist.