See also: IRC log
<jallan> title: UAWG Teleconference
<jallan> scribe: Jan Richards
<JR> Scribe: JR
JA: UA needs to recharte by Dec
... I am up to date on techniques table.
... May need to turn this into an ssues list as reason to move towards uaag 1.1
JA: JR and I went back and forth
... But just sent to JR so am now sending to the group
... JR had suggested combining this with 9.3.
JA: Agreed in email (http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0024.html)
<scribe> ACTION: JA to Combine 9.7 into 9.3 - moving backwards will be a req [recorded in http://www.w3.org/2006/11/16-ua-minutes.html#action01]
JR's original email: http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0023.html
<jallan> JR: if in the source of an 'input' with place holder text the UA should be able to search this text
JA: Doesn't think user entered words should be searchable - since it says rendered
JR: Would like to see it addded
JA: If author supplies it, user agent should find it
PP: In Firefox 1.5 can't search
in large text area - which is a bother in Wikis etc
... Browser does know what's in there.
JR: IE does this already
... So for form controls we want to cover labels, default text content inside textboxes etc, and end-user text addded to textboxes etc.
JA, PP: OK
JA: Discussion of conditional
... If images on, alt text is conditional so not searchable...
... But if images not on (or in HPR or screen reader) ...then should be searchable
PP: Seems strange that conditional is not searchable...
<scribe> ACTION: JA to Add issue to issues doc concerning searching within conditional text [recorded in http://www.w3.org/2006/11/16-ua-minutes.html#action02]
JA: Some non screen reader users have prob if they are brought to image by search but don't see alt text
PP: Has question about reverse search being in doing more of 9.8,
JA: Almost all tools have reverse built in already
JR: Maybe we add to req 2.
JA: Or maybe we just remove "forward" and "backward"
JR, PP: OK to remove both "forward" and "backward" (req 2 or 9.8)
<jallan> ACTION: JA remove requirement 2 of 9.8. removing requirement for "forward" search implies that requiement 1 includes the current functionality of UAs to provide forward/backward search functionality [recorded in http://www.w3.org/2006/11/16-ua-minutes.html#action03]
<jallan> JR: not 'allow' but 'provide' structured navigation
JA: THis became a P2, because ua manufacturers were against P1.
JR: Comment was how essential this was.
PP: Has just come up in
... No consensus for how should this work.
... Orca (Screen reader) just asked Firefox but declined.
JA: When people shown screen
reader features, people who don't need SR's also want
... Surprised no one has written an extension
PP: Charles Chen has provided a
structured navigation extension...but there are issues with
folding in his code to the main code
... Also tricky with Jaws because there are multiple modes (e.g. form mode). Most users might be confused.
JA: So would move away from
... Change "allow" to "provide"?
<scribe> ACTION: JA to Change "allow" to "provide" [recorded in http://www.w3.org/2006/11/16-ua-minutes.html#action04]
<jallan> JR: there is a richness of functionality provided to all users with this checkpoint
<jallan> JR: would like to see it be a P1
JR: Actually I said if it was
allow then why not P1...P2 works for provide.
... ATAG has a similar section for Prompting (B.2.1) that breaks out techniques nicely with pics etc.
PP: In Windows, Jaws grabs raw
HTML and walks it.
... In linux don't have that option so need ua to tell sr the element type etc.
... THis is provided by the Linux API.
... Although some limitation (eg. has HEADER, but not h1, h2, etc
... Though there is a workaround since uas can define own pairs
... someheat slow to do this element at a tim
JA: OK but still browser must supply roles to API for use by AT's
<jallan> if browser does not give info to api, the api cannot pass information to the AT
<jallan> ACTION: JA add technique stating that UA must provide object attributes (element name and roles, etc.) to the accessibiltiy api to enable structured navigation. [recorded in http://www.w3.org/2006/11/16-ua-minutes.html#action05]
PP: May have been left out of original uaag because can't do it with MSAA
JA: Personally would like the browser to do more of this natively.
</jim's rant> :)
JA: Seems like extension of
... Less impressed with having tons of configuration settings
JR: Maybe lots of power users on the original WG
<scribe> ACTION: JA to Consider including this a technique for 9.9 [recorded in http://www.w3.org/2006/11/16-ua-minutes.html#action06]
JA: Doing more "similar style" is not well defined.
JR: Yeah "similar" always worries me.
<scribe> ACTION: JA to Remove Similar styles doing more item [recorded in http://www.w3.org/2006/11/16-ua-minutes.html#action07]
JA: Next meeting in 2wks
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: Jan Richards Found Scribe: JR Inferring ScribeNick: JR Scribes: Jan Richards, JR Default Present: Jim_Allan, parente, JR Present: Jim_Allan parente JR 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/2006OctDec/0022.html Got date from IRC log name: 16 Nov 2006 Guessing minutes URL: http://www.w3.org/2006/11/16-ua-minutes.html People with action items: add attributes element etc. ja must name object provide roles stating technique that ua WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]