<AllanJ> GL: Introduces self

<AllanJ> all: introductions

Group going through intros.

http://www.w3.org/2002/09/wbs/36791/200905

http://www.w3.org/2002/09/wbs/36791/20090505/

zakim close item 3

zakim take up item 1

zakim takeup item 2

zakim item 2

<scribe> Scribe: kford

Survey Results

Taking up #38 Text Configuration

Jan Proposal 3.6.2 Text Scale Distinctions: when rendered text is rescaled, the user has the option to either preserve or remove distinctions in the relatives scales

of rendered text. (Level A)�

<AllanJ> KF: MH comment in survey. Requires AT. should expand to include Jan's wording

<AllanJ> JA: +1 Jan wording

<AllanJ> MH: +1 Jan wording

GL: In general proposal looks good. One question does current proposal allow wiggle room that would allow multiple designs that might be good or bad.
... One can imaging scaling up all items at same rate.

G: Second is like a word draft mode.GL: Option 3 I want everything to scale at same relative percentages but don't make anything beyond size X.

GL: Do we want a UA author to be able to do this?
... Capping size is more complicated.

KP: What I want is a particular type of text in one font and everything else in something eolse?

<AllanJ> KP: change size by class of text (headings, etc.)

<AllanJ> KF: this is a good idea. perhaps should have a requirement. build user css based on page

JR: Another thing to think about is that the user might not want something below size X. I think we need to rewrite taking this all into consideration.

<AllanJ> JR: set floor and ceiling. need rewrite

GL: A floor and a ceiling are good ideas. We have to think about the level that these are. Setting everything to a given font may be easier.

<Zakim> Jan, you wanted to say also could set a floor

GL: I could imagine the single size being level A and floor and ceiling being AA.

Some clarification around rendered text and whether this applies to content and UI.

As written this applied to rendered text.

Some discussion around how W3C specs could reference ISO standards and any plans.

<AllanJ> JR: can refence informationally to other standards

<AllanJ> KF: Jan proposal, but many expansions, should rewrite.

<AllanJ> JA: summary: scale fonts, min/max, floor - bring anything smaller upto a min size, remove distinctions when scaling,

<scribe> ACTION: Greg to update 3.6.2 for text sizing. [recorded in http://www.w3.org/2009/05/07-ua-minutes.html#action01]

<trackbot> Sorry, couldn't find user - Greg

Next Up: #53 Allow users supplied stylesheets

<AllanJ> JR: what is data of user supplied style sheet

<AllanJ> KF: low

<AllanJ> users don't know about the ability, difficult to write a css

GL: When I worked on Windows we added a range of high contrast color schemes. But we got a lot of complaints when there was part of the UI that the user couldn't customize. While the number was low, for those who needed it it was critical.

<AllanJ> KF: What about the Kindle. should they have user style sheets.

<AllanJ> GL: if they wanted AA

Group is in agreement that user creating stylesheets being able to create is AA.

<AllanJ> KF: A switch or disable author CSS, AA is create apply user CSS

<Jan> +1

<AllanJ> GL: be careful of and/or

<scribe> ACTION: kford to update guideline on style sheets to reflect current thinking. [recorded in http://www.w3.org/2009/05/07-ua-minutes.html#action02]

<trackbot> Sorry, couldn't find user - kford

<scribe> ACTION: KFord to update guideline on stylesheets. [recorded in http://www.w3.org/2009/05/07-ua-minutes.html#action03]

<trackbot> Sorry, couldn't find user - KFord

<AllanJ> ACTION: Kelly to rewrite 3.6.2 on style sheets to reflect current [recorded in http://www.w3.org/2009/05/07-ua-minutes.html#action04]

<trackbot> Created ACTION-182 - Rewrite 3.6.2 on style sheets to reflect current [on Kelly Ford - due 2009-05-14].

On to: #55 Clarify difference between 4.1.10 and 4.1.11

Group looking through survey comments.

<AllanJ> discussion of key precedence

Extensive discussion on keyboard behavior. Ranged from access keys to conflicts and such.

<AllanJ> GL: user can change modifier keys

<KimPatch> I'm going to have to go at 2:30

<AllanJ> GL: change non-modifier, and/or change modifier key

<AllanJ> GL: saving keybinding changes for individual websites would be lots of overhead, perhaps AA

<scribe> Chair: Jim_allan

This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: kford
Inferring ScribeNick: kford
Default Present: kford, Allanj, Jeanne, sharper, Jan, Kim_Patch, Mark_Hakkinen, +1.425.895.aaaa, Greg_Lowney
Present: kford Allanj Jeanne sharper Jan Kim_Patch Mark_Hakkinen +1.425.895.aaaa Greg_Lowney

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2009AprJun/0038.html
Got date from IRC log name: 07 May 2009
Guessing minutes URL: http://www.w3.org/2009/05/07-ua-minutes.html
People with action items: greg kelly kford

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.