- From: Nick Kew <nick@webthing.com>
- Date: Mon, 4 Feb 2002 03:27:54 +0000 (GMT)
- To: <w3c-wai-er-ig@w3.org>
On Sun, 3 Feb 2002, Nick Kew wrote: > > I've put up a second Page Valet+EARL prototype. This one has dropped the > XHTML, and is somewhat more considered. It's still at > <URL:http://valet.webthing.com/page/wai.html> OK, this is now updated: please take a look. > Some Issues: > > (1) testSubjects are now references into the document being checked, > and take three formats: > * Validation - the overall result is the URL - that's fine > http://foo.bar/docname.html Added an overall result to accessibility testing: Pass and Fail, each with two confidence levels (high confidence pass is very hard at any accessibility test suite). > * Validation messages - use a fragment to identify line and column > http://foo.bar/docname.html#(16,37) Changed this as per sbp's suggestion > * Accessibility checks - reference an element in the normalised > parse tree. I'm aiming for a "fuzzy Xpointer" (as discussed > in IRC), but there's some significant hacking to visval > required first > http://foo.bar/docname.html#e12 (now) > http://foo.bar/docname.html#1/4/1 (goal) Goal now reached. Jim's going to see if this is any use to him a clientside app. > > (2) testObjects for validation messages are a placeholder. I don't > know what really makes sense Updated, but still not very useful. > (3) I've used predicates (passes|fails) for validation messages, and > suspectAgainst for accessibility warnings. Next step is to > generate confidence levels from visval, so we can distinguish > between definite problems, and issues flagged for manual inspection. Confidence levels now implemented. > > Comments, criticisms, and especially help, invited. Thanks to Sean for his comments: I've used some of them, and will endeavour to use more as time and round tuits permit. Anyone else? -- Nick Kew Site Valet - the mark of Quality on the Web. <URL:http://valet.webthing.com/>
Received on Sunday, 3 February 2002 22:27:58 UTC