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

3.2 Close outs plus two discussion items

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Wed, 14 Dec 2005 15:22:52 -0600
To: <w3c-wai-gl@w3.org>
Message-ID: <01c701c600f4$98b3fab0$9baac246@NC6000BAK>
 

 Below are recommendations for 3.2 issue resolutions. 

 
Gregg



 

Discuss, decide and close

*	1659.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1659>  3.2 L2 SC1 wording seems vague

*	Now 3.2.3 Components that are repeated on multiple delivery
<http://www.w3.org/TR/WCAG20/appendixA.html#deliveryunitdef>  units within a
set of delivery units occur in the same
<http://www.w3.org/TR/WCAG20/appendixA.html#samerelorderdef>  relative order
each time they are repeated.
*	This seems to say that you couldn't have pages with same thing
sorted differently.
*	RECOMMEND : Be more specific as to what is meant / what is covered
or should be moved to level 3

*	1747.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1747>  GL 3.2 L2 SC 3 - Should be Level 1

*	Guideline 3.2 - Level 2 - 3: Shouldn't this be level 1? This is very
important to screen reader users. Users can become very confused if the
context changes by the mere action of changing the setting of an input field
(JavaScript enabled select boxes that redirect on the first selection is a
serious issue for keyboard users). [TWG]
*	This is now: 3.2.2 Changing the setting of any input field does not
automatically cause a change of context
<http://www.w3.org/TR/WCAG20/appendixA.html#context-changedef> .
*	RECOMMEND:  We discuss and close this item

 

Close all of these items as noted below

767.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#767>  Common ideas for making content consistent and predictable

*	This is 10 different recommendations:  
*	3 CLOSED BY PREVIOUS RESOLUTIONS. 
*	SUGGEST CLOSING THE REST AS NOTED BELOW.  

 1.) place navigation menus in a consistent location whenever possible
AS> CLOSE:  COVERED BY 3.2.3 Components that are repeated on multiple
delivery <http://www.w3.org/TR/WCAG20/appendixA.html#deliveryunitdef>  units
within a set of delivery units occur in the same
<http://www.w3.org/TR/WCAG20/appendixA.html#samerelorderdef>  relative order
each time they are repeated.

2.) similar layout for user interface components should be used for sections
or whole site
AS> CLOSE: COVERED BY 3.2.3 Components that are repeated on multiple
delivery units <http://www.w3.org/TR/WCAG20/appendixA.html#deliveryunitdef>
within a set of delivery units occur in the same
<http://www.w3.org/TR/WCAG20/appendixA.html#samerelorderdef>  relative order
each time they are repeated.

3.) similar user interface components should be labeled with similar
terminology
AS> CLOSE: COVERED BY 3.2.4 Components that have the same
<http://www.w3.org/TR/WCAG20/appendixA.html#samefunctionalitydef>
functionality in multiple delivery
<http://www.w3.org/TR/WCAG20/appendixA.html#deliveryunitdef>  units within a
set of delivery units are identified consistently.

4.) use headers consistently
CLOSED BY RESOLUTION 

5.) use templates for consistent presentation of sections or whole site 
CLOSED BY RESOLUTION

6.) pages with similar function should have similar appearance and layout
CLOSE WITH CURRENT SUCCESS CRITERIA ??   IF NOT CLOSE BECAUSE 'SIMILAR
APPEARANCE AND LAYOUT IS NOT OTHERWISE TESTABLE"   INCLUDE AS AN ADVISORY
TECHNIQUE
3.2.3 Components that are repeated on multiple delivery units
<http://www.w3.org/TR/WCAG20/appendixA.html#deliveryunitdef>  within a set
of delivery units occur in the same
<http://www.w3.org/TR/WCAG20/appendixA.html#samerelorderdef>  relative order
each time they are repeated.
 3.2.4 Components that have the same
<http://www.w3.org/TR/WCAG20/appendixA.html#samefunctionalitydef>
functionality in multiple delivery
<http://www.w3.org/TR/WCAG20/appendixA.html#deliveryunitdef>  units within a
set of delivery units are identified consistently. 


7.) controls that look or sound the same should be designed to act the same 
CLOSE:   Covered by  3.2.4 Components that have the same
<http://www.w3.org/TR/WCAG20/appendixA.html#samefunctionalitydef>
functionality in multiple delivery
<http://www.w3.org/TR/WCAG20/appendixA.html#deliveryunitdef>  units within a
set of delivery units are identified consistently.  

8.) conventions likely to be familiar to the user should be followed
CLOSED BY RESOLUTION

9.) unusual user interface features or behaviors that are likely to confuse
the first-time user should be described to the user before they are
encountered
RECOMMEND REJECT. Not testable as written - "unusual user interface
features"  [ASW]

10.) allow the user to select different page layout templates for
presentation of pages. (e.g. 3 column, linear, adding extra orientation or
navigation
elements, etc.)
AS> This doesn't seem to be applicable to GL 3.2 which is about predictable
placement and functionality of content. This is about allowing the user to
choose from several options for viewing the content. This seems like a good
accessibility "feature" that can be accomplished if GL 1.3 is met. But we
don't have a guideline that it really fits
RECOMMEND THIS BE AN ADVISORY TECHNIQUE UNDER 3.2 GUIDELINE

then CLOSE:

*	931.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#931>  Extreme changes in context, scripting, and programmatically
identified

*	Questions what the term "extreme change of context"  and PI  means 
*	CLOSE with comment -  fixed with our current draft wording. 

*	1172.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1172>  Who Benefits? "context" is not an appropriate word

*	CLOSE - new language provides different language to make the word
clear and provides examples. 

*	1408.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1408>  permit variation in layout of content

*	Similar to one of the 10 above.  
*	MAKE Advisory technique to GL 3.2 
*	CLOSE

*	1410.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1410>  GL 3.2 Level 3 success criteria aren't sufficient

*	CLOSE - Address by current changes

*	1411.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1411>  only use same text equivalents when appropriate

*	CLOSE - addressed by the current changes

*	1458.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1458>  Level 3 Success Criteria for Guideline 3.2 point 3 - how and
why?

*	Asks how this can be done
*	CLOSE - language being questioned is no longer a success criterion 

*	1510.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1510>  3.2 L1 SC1 proposed rewording

*	CLOSE - addressed by new language 

*	1517.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1517>  3.2 L3 SC1 proposed revision

*	CLOSE - addressed by new langauge

*	1568.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1568>  Level 2 SC seems circular

*	Internal comment 
*	CLOSE - addressed by current edits 

*	1569.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1569>  Do we really mean "change of content" instead of "change of
context"?

*	CLOSE - definitions and intent changed to make clear

*	1570.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1570>  Suggested reordering of Level 2 SC

*	CLOSE -  done in current draft

*	1571.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1571>  Replace "pages" with "delivery units"

*	CLOSE - done in current draft

*	1657.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1657>  3.2 L1 SC1 This seems very unclear

*	CLOSE - this success criterion no longer exists

*	1658.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1658>  3.2 L1 SC1 Example 2 needs to be changed

*	CLOSE - this example changed

*	1660.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1660>  3.2 L2 SC2 criterion as written would prohibit the user agent
from scrolling

*	CLOSE - that change would be included in the change TO the item.
Not caused by another change of focus after focus moves to the element

*	1661.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1661>  3.2 L2 SC3 makes this criterion prohibit such commonly-used
mechanisms as hiding or deactivating

*	CLOSE - current draft has changed to make it clear that this is not
prohibited.

*	1662.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1662>  3.2 L2 SC4 examples we should make clear

*	CLOSE - examples and 'how to meet' document now make this clearer

*	1663.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1663>  3.2 L3 SC1 This would prohibit having a graphical button

*	CLOSE - this is fixed with new language.

*	1664.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1664>  3.2 L3 SC2 Is it acceptable if the content updates automatically
by default

*	CLOSE - Answer is No.  At level 3 the content should update only by
user action.  Not the reverse.   This is what the success criterion says. 

*	1716.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1716>  provide examples of how a change of context would be
programmatically determined

*	CLOSE - we dropped this success criterion

*	1773.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1773>  Relevance of Note to SC 3.2.1 unclear

*	Asks why there is a cross reference.
*	CLOSE - cross references removed

*	1774.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1774>  Some input fields should change context

*	Jason White says: 3.2.2: "Input field" needs to be defined in the
glossary. In particular, the "go ahead and change context" control had
better not qualify as an input field. An input field can't be simply
anything that changes the value of a variable, since the "change context"
control will no doubt alter the values of variables in the software as well.
Maybe the real requirement is that no element of the user interface can both
(1) change the context and (2) perform some other action such as modifying
variables in an application.
*	CLOSE:  A button isn't a field.   The success criterion doesn't talk
about variables.  So the current wording is not vulnerable to the above
issues. 

*	496.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#496>  identification of context changes, wording suggestion on
checkpoint

*	CLOSE:  This deals with the success criterion that we removed. 

*	774.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#774>  word to replace "page" that applies across technologies?

*	CLOSE:  we have done this. 

*	1413.
<http://trace.wisc.edu/bugzilla_wcag/issuereports/consistent-behavior_issues
.php#1413>  Ease of configuring presentation is important

*	What the success criterion does not say is how easy this should be
for the average user. This will impact usability.
*	CLOSE:  This deals with usability which is outside of our scope. 

 

 

 

 


 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 

  _____  
Received on Wednesday, 14 December 2005 21:23:33 GMT

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