W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2005

RE: proposed example for 3.2, l2, sc1

From: Loretta Guarino Reid <lguarino@adobe.com>
Date: Tue, 1 Nov 2005 16:27:58 -0800
Message-ID: <0DAF2B31FBCEB6439F63FA7F91601F7434EA4D@namail3.corp.adobe.com>
To: "Kerstin Goldsmith" <kerstin.goldsmith@oracle.com>, "John M Slatin" <john_slatin@austin.utexas.edu>
Cc: "wcag" <w3c-wai-gl@w3.org>
Yes, Enter or Space is usually used to make the selection in the list.

 

Loretta Guarino Reid
lguarino@adobe.com
Adobe Systems, Acrobat Engineering 

________________________________

From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Kerstin Goldsmith
Sent: Tuesday, November 01, 2005 3:25 PM
To: John M Slatin
Cc: wcag
Subject: Re: proposed example for 3.2, l2, sc1

 

Hey, John:

What about the idea of having the user hit ENTER when they have
highlighted their choice to activate an on-change, and then exiting the
list?

-kerstin

John M Slatin wrote: 

Kerstin wrote:

 

<blockquote>

  -   When a user moves focus to a dropdown list, or poplist,
highlighting a choice in the list does not automatically activate an
on-change event.  The
on-change event can be activated either by the user exiting the list, or
having the next function in the tab order be a submit action of some
kind outside
the list altogether.

</blockquote>

 

According to the proposed example, merely exiting a pulldown menu/popup
menu/selection list could cause a change of context. This would be
almost as disorienting as firing the onChange event when the downArrow
is pressed.

 

I think we should disallow this.

 

JOhhn

 

 

"Good design is accessible design."

Dr. John M. Slatin, Director 
Accessibility Institute
University of Texas at Austin 
FAC 248C 
1 University Station G9600 
Austin, TX 78712 
ph 512-495-4288, fax 512-495-4524 
email jslatin@mail.utexas.edu 
Web http://www.utexas.edu <http://www.utexas.edu/research/accessibility>
/research/accessibility 

	-----Original Message-----
	From: w3c-wai-gl-request@w3.org
[mailto:w3c-wai-gl-request@w3.org] On Behalf Of Kerstin Goldsmith
	Sent: Monday, October 31, 2005 4:16 PM
	To: wcag
	Subject: proposed example for 3.2, l2, sc1

	I took an action item to come up with example/s for 3.2, L2 SC1,
which read:
	      Changing the setting of any input field does not
automatically cause a change of context
<http://trace.wisc.edu/wcag_wiki/index.php?title=Guideline_3.2#context-c
hangedef> . (Guide to 3.2 L2 SC1
<http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_3.2_L2_SC1> )
	
	
	
	Proposed Example:

	  -   When a user moves focus to a dropdown list, or poplist,
highlighting a choice in the list does not automatically activate an
on-change event.  The on-change event can be activated either by the
user exiting the list, or having the next function in the tab order be a
submit action of some kind outside the list altogether.
Received on Wednesday, 2 November 2005 00:27:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:40 GMT