Assisgment 3.2 L1 SC1

 Guideline 3.2 <http://www.w3.org/WAI/GL/WCAG20/#consistent-behavior>  [1]
Make the placement and functionality of content predictable. 

*	3.2
<http://www.w3.org/WAI/GL/WCAG20/#consistent-behavior-change-of-context>  L1
SC1 [2] Any change of context is implemented in a manner that can be
programmatically
<http://www.w3.org/WAI/GL/WCAG20/#programmaticallydetermineddef>  determined
[3]. 

Proposal: remove this criterion because if you meet the other level 1
success criterion, then a user agent should be able to programmatically
determine changes in context in a fairly straightforward way. 

This was the only criterion at level 1, but in looking at the level 2
criterion, we'd like to also propose moving L2 SC3 (When any component
receives focus, it does not cause a change of context.) to level 1. 

While reviewing this SC, we came up with some proposed revisions to
definitions (which are used in other SC for this guideline). They address
some of the issues that were raised in last week's call.


Key terms 


change of context  

change of user agent, viewport, or focus; or complete change of main
content. 

Note: we removed "user interface controls" from this definition based on
standard form control show/hide behavior practice such as Gez's example.
<http://juicystudio.com/wcag/changecontext.html> 

 


Misc. text written while working on this, but now being discarded unless
pieces are useful to others for their success criteria 


The intent of this success criterion is to ensure that users who can not see
the screen are aware that the displayed content has materially changed or
that they are no longer in the same window or context that they were a
moment before. For users who can see, this isn't a problem, since it's
visually apparent, that things have suddenly changed. Modern assistive
technologies automatically notify users when new windows pop up and when
other standard methods for change of context occur. Therefore, this success
criteria generally met when standard mechanisms for dialog boxes, pop up
windows, etc. are used. 

With some technologies, however, it is possible to create dialog "boxes" or
to substantially or completely change the content within the same window in
ways that are visually obvious, but not easily programmatically determined. 

Change of context should not be confused with change of content. Small
changes in content, such as an expanding outline, do not change the context
and therefore, are not covered by this particular success criterion.

[1] <http://www.w3.org/WAI/GL/WCAG20/#consistent-behavior>
[2]
<http://www.w3.org/WAI/GL/WCAG20/#consistent-behavior-change-of-context>
<http://www.w3.org/WAI/GL/WCAG20/#consistent-behavior-change-of-context>
[3]
<http://www.w3.org/WAI/GL/WCAG20/#consistent-behavior-change-of-context>
<http://www.w3.org/WAI/GL/WCAG20/#consistent-behavior-change-of-context>

[end notes on 3.2 L1 SC1]