<scribe> Scribe: JR

<JR> hi Al

Hi All, I am on the phone

* al how do I not be scribe?

this is jim

<jallan> http://lists.w3.org/Archives/Public/public-cdf/2006Jan/0068.html

<JR> WAI last call comments on CDF, WICD, WICD Full, WICD Mobile, WICD Core

WAI last call comments on CDF, WICD, WICD Full, WICD Mobile, WICD Core

<JR> JA: Now seems to read MathML

<JR> DP: Because Jaws now reads unicode

<JR> CL: IBM has done an internal WindowEyes and Firefox report

<JR> DP: Firefox now behaving much more like IE with Jaws.

<JR> JA: Waiting for Al to join.

<JR> JA: Al wants our input on Accesskey doc

<JR> JA: UA Comments on Compound Docs combined with PF comments and submitted.

<JR> JA: We'll need some compound doc test cases: SVG, MathMl etc.

<JR> JR: Opera 8 has native SVG support

Other business from CG

<JR> JA: Networking opportunities with other groups.

Screen Readers and Firefox

<JR> Aaron: Jaws not ready for FF

<JR> Aaron: no official support for several months

<JR> Aaron: We have done WindowEyes and FF, but with bugs filed for FF

<JR> Aaron: Check out bug 24413 in bugzilla for FF (have uaag in title)

<JR> Aaron: Some other bugs - look for "uaag"

<JR> Aaron: FF on Mac is not very accessible - because Mac readers son't use DOM?

<JR> Aaron: 2 probs - (1) uses Carbon instead of Coco (2) nobody has signed up for Mac access.

<JR> for FF

<JR> Because Safari is so big on Mac

<JR> JA: SVG?

<JR> Aaron: Yes there is some native support for SVG in FF?

<JR> rem ?

<JR> JA: In compound docs there was questions about passing focus into and out of different types of content ALSO sub links

<JR> Aaron: Using depth first search on layout object tree.

<JR> Aaron: Some things are focussable, but not tabable (e.g. items in a drop down list)

Accesskeys with Al

<jallan> http://lists.w3.org/Archives/Public/w3c-wai-ua/2006JanMar/0016.html

<JR> Al: The HCG recognizes Accesskeys are problematic but desirable...

<JR> XHTML2 is coming up with a replacement.

<JR> Al: we're supposed to bring use case to them next Friday.

<JR> Al: Mobile phone people also interested in accesskeys.

<JR> Al: Latest statement - there has to be a label - needs to be discoverable

<JR> Al: Users would prefer to set their own mnemonics but MUST be able to access it somehow.

<JR> Al: Overall, we're not taking a strong position.

<JR> Al: But there are "firm requirements"

<JR> JA: On user side the user simply needs to be able to found out what the keys are and what they do.

<JR> Al: but in larger scheme, to capture mode apps to the web shortcut capability should be increased.

<JR> Aaron: Can we give weight to pros and cons in "debatable" area

<JR> JA: "Discoverable" requirement should be dug out and put at the top

<JR> Al: Label is an operational model - must work like a label on a form control

<JR> DP: Might feel better about author assignment if two paths - author specifies method of activation vs. generic method of activation

<JR> AL: I need to add in authoring guidance that there is a preference for binding keys to roles when there is a relevant role already.

<JR> Al: Use rel=home to identify a link that goes home---then browser is smart enough to interpret "h" keypress as meaning user wants to go home (ie.e. press that link)

<JR> DP: Author trying to come up with way to activate non-standard things..

<JR> maybe easier to provide trigger and let user agent handle putting keys to triggers.

<JR> Al: Loses all mnemonics

<JR> Al: It's a tugofwar

<JR> CL: Problem: HTML accesskeys --combines mnemonics with sahortcuts - these should be different.

<JR> MMnemonics need to appear in label, shortcuts are different.

<JR> CL: e.g. in chrome menu items, an underlined character is the mnemonic

<JR> Al: In reqs it must be somehow discoverable.

<JR> AL: IG - why not just mark the letter eg. with tag wrapping a key ---but T2speech chokes on that

<JR> JA: What about negotiation...

<JR> Al: Onscreen keyboards can process accesskeys, so can screen readers, could be a browser feature

<JR> JA: What about authors who put the key in the title?

<JR> Al: The UA's need to start showing access keys somehow - e.g. on mouseover, tabbing, etc.

<JR> ACTION: Al to Will modify reqs to add "discoverable" and author should bind access keys to available roles. [recorded in http://www.w3.org/2006/02/02-ua-minutes.html#action01]

<JR> JA: on this timeslot next week will be a special meeting on the Mobile Web Berst Practices

<JR> http://www.w3.org/TR/2006/WD-mobile-bp-20060113/

<JR> ACTION: JR to Review for AU and send to JA. [recorded in http://www.w3.org/2006/02/02-ua-minutes.html#action02]

<JR> ACTION: JA to Review for UA [recorded in http://www.w3.org/2006/02/02-ua-minutes.html#action03]

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: scribe
ScribeNicks: JR, scribe
Default Present: Jim_Allan, [IBM], Jan_Richards, DPoehlman, Aaron_Leventhal, AlGilman
Present: Jim_Allan [IBM] Jan_Richards DPoehlman Aaron_Leventhal AlGilman
Got date from IRC log name: 2 Feb 2006
Guessing minutes URL: http://www.w3.org/2006/02/02-ua-minutes.html
People with action items: al ja jr

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