Proposals for 3.2.2

Hi all,

The following proposals are being considered for SC 3.2.2. They are the 
result of some issues that came up at the face to face last week, and an 
action item that David and I had from a couple weeks ago to look whether 
this criterion should be moved to level 1.

Current:

3.2.2  Changing the setting of any input field does not automatically 
cause a change of context .

3 Changes proposed:

1.) Change ‘input field’ to ‘form control or field’ so that it is clear 
that check boxes, radio buttons etc are covered.

2.) Add the phrase, "unless instructions are provided that describe the 
behavior" to the end of success criterion 3.2.2.

Proposed:

Changing the setting of any form control or field does not automatically 
cause a change of context unless instructions are provided that describe 
the behavior.

Note: Sufficient techniques would need to explain where the instructions 
should appear. (either directly preceding the form control itself or (if 
multiple controls of this nature are used) preceding the first item that 
causes the change of context.)

Rationale:

This would allow for behaviors where focus change is helpful and not 
disorienting for those who cannot see (if they are aware that this is 
how the component was intended to operate.)  For example, clicking on 
radio buttons could cause the rest of the page to change from one 
document to another.

3.) Revise the definition of change of context to allow for changes of 
focus that are not disorienting See Becky's example at 
<http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0834.html>.

Current:

changes of context

     A change of user agent, viewport, or focus; or complete change of 
content that changes the meaning of the delivery unit.

     Note: A change of content is not always a change of context. Small 
changes in content, such as an expanding outline or dynamic menu, do not 
change the context.


Proposed:

changes of context

changes of:
    - user agent,
    - viewport,
    - focus (except next field in tab order),
    - content (that change the meaning of the delivery unit).

     Note: A change of content is not always a change of context. Small 
changes in content, such as an expanding outline or dynamic menu, do not 
change the context.

I'm a bit unsure about whether or not to recommend moving this to level 
1. Looking at the threads and examples that have been discussed so far, 
I'm inclined to leave this at level 2 since the issues we've been most 
concerned about around this criterion seem to be covered at level 1 by 
guideline 2.1.

Thoughts?

-Ben

-- 
Ben Caldwell | <caldwell@trace.wisc.edu>
Trace Research and Development Center <http://trace.wisc.edu>