<scribe> Scribe: Jim Allan

Review Aciotn items

1c. More clearly identify who benefits from accessible user agents.

suggestion change to "Identify who benefits from accessible user agents. "

All: change is fine.

<scribe> ACTION: JA change 1c to reflect wording change [recorded in http://www.w3.org/2007/04/12-ua-minutes.html#action01]

1e. Address author responsibilities when creating content vs. UA functionality (repair and control functions)

reviewed WCAG 2 and UAAG (intersection)

cl: browser exposes information to accessibility api...if author provided it.
... if author does not provide appropriate information (alt, label), then browser or AT must repair (find some information)

change to: 1e. Address author responsibilities when creating content and UA functionality when author is irresponsible (need to word smith)

cl: aside - ajax, dojo techniques make extensive use of style sheets. may need change requirement of being functional without stylesheets.

ja: style sheet conflict issues, user not allowed to turn off style sheets?

cl: must take low vision users into account, what about user stylesheet
... how many are actually used. have to be very technical to even create one.
... problem with explict requirement for being able to turn off style sheets.

ja: don't think most users have own style sheet. this has fallen to the author to create multiple styles and allow user to choose between them, also authors have taken control of font size changing rather than letting the user use the UA functionality

<scribe> ACTION: JA change language for 1e [recorded in http://www.w3.org/2007/04/12-ua-minutes.html#action02]

Review requirements document

cl: what things should a user be allowed or not allowed to do

ja: such as using personal style sheet that will break ajax applications

cl: changing styles is ok for static web pages but not for web applications
... UAAG responsiblity for keyboard access to elements with event handlers, but with web apps, the UA can't know, it is up to the author
... mouseover, currently UAAG says UA should provide keyboard access
... should be posting these items to x-tech or pf list for input

ja: conformance:

Jan sugeest combining 2a and 2b as follows

Consider modularizing the UAAG 2.0 document such that "basic" browser

capabilities are clear (i.e. features for people needing some

accessibility support, but who do not use assistive technologies), while

also addressing voice browsers, speech input, etc. that while important

might be implemented by assistive technologies or browser extensions

ja: conformance model (core, core + extensions, core + AT, core + extensions + AT)

cl: baseline, see wcag

ja: need to review atag to see if they have a baseline

cl: UAAG will probably need a base line
... change conformance to include baseline, such that a claim declares which technologies (browser + extension + AT) are required to meet specific requirements

specific requirements = UAAG requirements

cl: could also include technology in items 3 a, b, c. conformance would declare SVG etc.

This is scribe.perl Revision: 1.128  of Date: 2007/02/23 21:38:13  
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: AllanJ
Found Scribe: Jim Allan
Default Present: Jim_Allan, cklaws
Present: Jim_Allan cklaws

WARNING: Fewer than 3 people found for Present list!

Agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2007AprJun/0003.html
Got date from IRC log name: 12 Apr 2007
Guessing minutes URL: http://www.w3.org/2007/04/12-ua-minutes.html
People with action items: 1c change ja