W3C

- DRAFT -

SV_MEETING_TITLE

4 Aug 2005

See also: IRC log

Attendees

Present
Jim_Allan, AlGilman, [IBM]
Regrets
Chair
SV_MEETING_CHAIR
Scribe
jallan

Contents


 

Hi Al, we mostly use the telephone

<Al> OK, will join you now

Al are you on the phone

discussion of <col> and <colgroup>

discussion of draft response for accesskey

author proposes/user disposes

mobile devices want to change the accesskey based on the device, not leave it up to the user/author

related to onchange on wwwhtml list

need to wok on future implementation of accesskey in xhtml2 and new browser implementation and repair for accesskey in html4

discussion of draft requirements

problem is knowing what the associations are.

base user agents don't have a way to expose accesskey bindings, the task has been taken by the Assistive Technology.

there is a requirement in UAAG for users to query the agent to find the bindings

say explicitly: User must be able to get a listing of keybindings for accesskeys

the user agent must do this, menu option. built into UA not left to AT repair or Author styling or other indicaton of accesskey

what about internationalization? if an accesskey is ~n, and I don't have it on my keyboard, how is it negotiated.

make interationalization a comment.

users needs to be able to change keys, but not necessarily anykey to anykey2

don't want to bind to key only, multimodal wants it broader.

discussion of how to expose accesskey, author supplied styling, UA exposing, using roles and let user define

desktop borwsers could expose this information to the user, but don't.

if UA use/expose accesskey to user in a standard way (using an api)

then AT could gather the bindings/roles and expose them in alternative ways to users. Authors might be more inclined to use accesskey if they did not have to style or provide other indication of accesskey on a page.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.126 (CVS log)
$Date: 2005/08/04 19:09:25 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.126  of Date: 2005/05/16 16:49:48  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: jallan
Inferring Scribes: jallan

WARNING: No "Topic:" lines found.

Default Present: Jim_Allan, AlGilman, [IBM]
Present: Jim_Allan AlGilman [IBM]

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


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 4 Aug 2005
Guessing minutes URL: http://www.w3.org/2005/08/04-ua-minutes.html
People with action items: 

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


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


[End of scribe.perl diagnostic output]