<PhilA> scribeNick: Phil

<PhilA> scribeNick: PhilA

Phil: Proposed model that had mobileOK Basic as is plus recording the values for individual tests - i.e. not always pass/fail

Kai: What's the point?

Phil: It is achiveable and avoids placing a pass/fail threshhold on a subjective decision
... mOK Pro therefore becomes true in the eye of the beholder

Kai: Then there is no sich thing as mOK Pro
... Also last night we discussed... mOK Pro doesn't need to be a Rec Track doc, it can be a Note
... We could give people a target to aim for

Alan: Is it not better to have a subset of the tests?

Kai: Even providing values as outcomes we still need to be more deterministic and to set goals for what we want people to do
... So should we think about different levels of mOK Pro?

PROPOSED RESOLUTION: The TF would accept mOK Pro as a WG Note cf. Rec Track document

Resolution: Not passed (for now anyway)

Kai: we want to provide values for the tests - the question is whether we want to set fixed threshholds for passing Pro

More discussion on how we might work this... let's look at some tests. Discussion turns to editing the doc itself.

We have edited the Access Keys test, made it more precise...

The Avoid Free Text test has also been amended. It now only refers to situations where there is a finite list of possible options

<achuter> http://juicystudio.com/services/colourcontrast.php#contrast

<achuter> New colour contrast analzer tool

<achuter> http://www.paciellogroup.com/resources/contrast-analyser.html#download

<achuter> We're deeply into discussing background image readability

<jo> [it's not the background image that needs to be readable, surely]

<achuter> agree

<achuter> [discussing colour gradients]

<achuter> PA: Patterns may make text unreadable even when contrast is good.

<achuter> scribenick achuter

<achuter> KD: [drawing on board] Contrast between adjacent colour areas may be sufficient but interfere with text shapes.

<achuter> [look at Ishihara Test for Color Blindness as examples of what fails]

<achuter> http://www.toledo-bend.com/colorblind/Ishihara.html

<achuter> http://en.wikipedia.org/wiki/Ishihara_color_test

And we've just improved the background images test, essentially deferring its essence to the colour contrast test which is deterministic

The balance test has been reduced and simplified. If any page has more than 30 links - fail. (Things like site maps with more than 30 links should be split across several pages, for example)

rrasgent, draft minutes

<achuter> Stopping for lunch now...

<achuter> [Back from lunch]

<achuter> Have continued reviewing 4.6 Device Capabilities test.

<achuter> Continuing with 4.7 Central Meaning and Limited test

<achuter> we finished with the control labelling test.

This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/wasnt/wasn't/
Succeeded: s/wasn't/want/
Found ScribeNick: Phil
WARNING: No scribe lines found matching ScribeNick pattern: <Phil> ...
Found ScribeNick: PhilA
Inferring Scribes: Phil, PhilA
Scribes: Phil, PhilA
ScribeNicks: Phil, PhilA

WARNING: No "Topic:" lines found.

Present: Kai Alan Phil
Got date from IRC log name: 19 Mar 2008
Guessing minutes URL: http://www.w3.org/2008/03/19-bpwg-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report