W3C

- DRAFT -

UAWG Teleconference 25 May 2006

25 May 2006

See also: IRC log

Attendees

Present
Jim_Allan, [IBM]
Regrets
Cathy, Laws
Chair
Jim Allan
Scribe
JR

Contents


 

 

<scribe> Scribe: JR

WCAG comments

JA: Will right something up for programmatically determined.

<jallan> JR: Programmatically Determined:

<jallan> determined by software from data provided in a user-agent-supported

<jallan> [implemented by user agents and assistive technologies] manner such that

<jallan> the user agents [any software that retrieves and renders Web content for

<jallan> users] can extract and present this information to users in different

<jallan> modalities

<jallan> This may be more clear:

<jallan> Available in a user-agent-supported [implemented by user agents and

<jallan> assistive technologies] manner that supports unambiguous automatic

<jallan> processing by user agents [any software that retrieves and renders Web

<jallan> content for users].

(Context, this is a proposal JR sent to JA last week that JA has just pasted in)

<jallan> JA: revision: Available in a user-agent-supported [implemented by user agents and

<jallan> assistive technologies] manner that supports unambiguous automatic

<jallan> processing by user agents [any software that retrieves and renders Web

<jallan> content for users] for presentation to users in different modalities.

(context: JA pastes in his newer version)

<jallan> cleaner - Available in a user-agent-supported manner that supports unambiguous automatic

<jallan> processing by user agents for presentation to users in different modalities.

JA: Can live with this.

JR: So can I

Peter: So can I

<jallan> ACTION: JA to contact CL about change of definition vs. change all sc in wcag [recorded in http://www.w3.org/2006/05/25-ua-minutes.html#action01]

Peter: Prob can expect better reception from WCAG than suggesting changes to lots of success criteria

WCAG 3.2.3

<jallan> 3.2.2 Changing the setting of any form control or field does not automatically cause a change of context (beyond moving to the next field in tab order) unless the authored unit contains instructions before the control that describe the behavior. [How to meet 3.2.2]

JA: Statement "(beyond moving to the next field in tab order)" should be removed since it undermines the whole thing

JR: Agreed

Peter: So why did they do it?
... Perhaps there are situations eg phone numbers with a known number of digits.

JA: If that clause is removed then it makes sense

JR, perter: Agreed

Summary of Action Items

[NEW] ACTION: JA to contact CL about change of definition vs. change all sc in wcag [recorded in http://www.w3.org/2006/05/25-ua-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/05/25 18:31:35 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.127  of Date: 2005/08/16 15:12:03  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: JR
Inferring ScribeNick: JR
Default Present: Jim_Allan, [IBM]
Present: Jim_Allan [IBM]

WARNING: Fewer than 3 people found for Present list!

Regrets: Cathy Laws
Got date from IRC log name: 25 May 2006
Guessing minutes URL: http://www.w3.org/2006/05/25-ua-minutes.html
People with action items: ja

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


[End of scribe.perl diagnostic output]