review of techniques for 6.4-6.6

6.4 Note: No techniques
6.5 Provision 1. Provide programmatic read access to user agent user
interface controls...
<item 1>
	Issue: the definition of "user agent user interface control" specifies
"out of the box". There is increase availability and use of extensions,
toolbars, etc. from the time UAAG was written. Does each UA have an API (?
is that the correct term) that extensions, toolbars, and other add-ons
write to, to meld with the user interface controls presented to the user?
Are there any accessibility guidelines (best practices, etc.) for
extension, toolbar, etc. authors?

	<definition>
	the user agent user interface, i.e., the controls (e.g., menus, buttons,
prompts, and other components for input and output) and mechanisms (e.g.,
selection and focus) provided by the user agent ("out of the box") that 	are
not created by content. [1]
	</definition>
</item 1>

<item2>
	Example technique 3, 6, and 8 talks about OSs and does not mention Linux.
	What if any information related to Linux should be added to these
techniques ?
</item2>

<item3>
	What are some references to Linux that can be added in the Reference
section?
</item3>

6.6 Programmatic notification of changes
<item>	in the normative inclusions...
	The user agent is not required to provide notification of changes in the
rendering of content (e.g., due to an animation effect or an effect caused
by a style sheet) unless the document object is modified as part of those
changes.

	issue: this may be out of date. in past calls we have talked about UAs
increasingly relying on API rather than the DOM. How do we update this
exclusion?
</item1>

<item2>Example technique 2. Provide notification when an action in one frame
causes the content of another frame to change. Allow the user to navigate
with little effort to the frame(s) that changed.

	issue: is this referring to activating an anchor? If so, I think default
behavior should be for content focus and visual point of reference should
move to the new frame. If it is not referring to anchor activation, then it
may need further expansion or an example.






1. http://www.w3.org/TR/UAAG10-TECHS/glossary.html#def-ua-ui

Jim Allan, Webmaster & Statewide Technical Support Specialist
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
---> Share to Win!! <---

> -----Original Message-----
> From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org]On
> Behalf Of Jim Allan
> Sent: Tuesday, August 29, 2006 3:37 PM
> To: WAU-ua
> Subject: User Agent Teleconference for 31 August 2006
>
>
>
> W3C User Agent Teleconference for 31 August 2006
> -------------------------------------------------------------
> Chair: Jim Allan
> Date: Thursday, 31, August 2006
> Time: 2:00-3:00 pm Boston Local Time, USA (19:00-20:00 UTC/GMT)
> Call-in: Zakim bridge at: +1-617-761-6200, code 8294#
> IRC: sever: irc.w3.org, port: 6665, channel: #ua.
> -------------------------------------------------------------
> Please send RSVP or additional agenda items to the list.
>
> Agenda Action Items
>
>
> 	1. Review of UAAG techniques for checkpoints  for currency
> and relevance.
> submit suggested deletions, improvements, additions 6.6-6.10 to the list.
>
> 	2. Review updated Checklist
> 		www.tsbvi.edu/technology/uawg/checklist-aug29.htm
>
>
>
> Jim Allan, Webmaster & Statewide Technical Support Specialist
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
> ---> Share to Win!! <---
>

Received on Thursday, 31 August 2006 16:12:04 UTC