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

GL 2.5 Issues summary with recommendations

From: David MacDonald <befree@magma.ca>
Date: Mon, 12 Dec 2005 15:22:15 -0500
Message-Id: <200512122022.jBCKMFJX012404@mail1.magma.ca>
To: <w3c-wai-gl@w3.org>, "'John M Slatin'" <john_slatin@austin.utexas.edu>
Cc: "'Gregg Vanderheiden'" <gv@trace.wisc.edu>, <wendy@w3.org>, <caldwell@trace.wisc.edu>
I had an action item to review all of the bugs for GL 2.5 and make
recommendations to the group. I have done that below.

 

----------------------------------------------------------------------------
----------------------

Bug #1771

2.5.4: "Context-sensitive help" should be defined in the glossary. How
"context-sensitive" does the help have to be in order to meet this sc?
Specific to the delivery unit? To the group of inputs containing the item
which has focus? To the individual input item in the user interface?

 

Proposed Action:

 

(1) Add this definition to the Glossary of the GL Doc;

 

Context Sensitive Help:

 

"Help text that provides information related to the function currently being
performed without requiring the user to use a table of contents, index, or
keyword search."

 

Adapted from:  <http://www.techcommunicators.com/dkmanual/glossary.html>
www.techcommunicators.com/dkmanual/glossary.html 

(2) Change the intent section

Current intent section:

The intent of this success criterion to help users avoid making mistakes.
Because of their disabilities, or aging, these users may be more inclined to
make mistakes than users without disabilities. [there is also a typo, the
first sentence is missing the word "is"]

Proposed intent section:

The intent of this success criterion is to help users avoid making mistakes.
Some users with disabilities, or who are aging, may be more inclined to make
mistakes than users without disabilities. Context sensitive help will
provide easy to access information about what is expected of user during a
particular task such as entering information into an input item (or input
group) on the page, without losing track of what they are doing. This will
be of particular help to those with cognitive disabilities. 

(3) Add a general technique for applying Context Help to a group of inputs
containing the item which has the focus.

(4) Close the bug and report the resolutions to the creator of the bug

 

 

----------------------------------------------------------------------------
----------------

Bug #1652

 

It's just funny that the word "them" in this title could apply to either the
mistakes or the users...grammatically and/or semantically.
[Comment on "2.5: Help users avoid mistakes and make it easy to correct
them."]

 

Proposed action: 

Although the pronoun "them" correctly refers to the noun "mistakes, this bug
does perhaps point to another problem with the current wording of the GL.
The Guideline as written does not seem to make clear logical sense. The
first part of the sentence is telling the web designer that they should
construct the site so as to avoid mistakes and the second part of the
current guideline seems to assume that the user will make mistakes. If a
person avoids mistakes, they would not have to correct them.

 

Current wording of the Guideline 

"Help users avoid mistakes and make it easy to correct them"

 

Proposed wording of the Guideline 

 

"Help users avoid mistakes, and if mistakes occur, make it easy to correct
them"

 

I think this will clean up the ambiguity that the bug reports and it will
also make the GL more logically coherent.

 

Suggest we adopt the proposed wording of the GL and close the bug and report
back to the person who filed the Bug . 

----------------------------------------------------------------------------
--------------------------------------------------

 


Bug 1743. GL 2.5 L3 SC 1 - should not say "additional" 


Description:  <http://www.at-links.gc.ca/WCAG2_0comments.htm>
www.at-links.gc.ca/WCAG2_0comments.htm 

Guideline 2.5 - Level 3 - 1: Additional? There is no mention of context-
relevant assistance mentioned anywhere in this guideline. Should define what
is meant by additional and in addition to what. [TWG]

Proposed Actions:

It is overcome by events. The GL no longer uses the word "additional" and
the "How to meet." explains it well. Close the bug and report back to the
bug creator

----------------------------------------------------------------------------
----------------------------------------------------------------------------
------------------------------

Bug 565

The U.S. Access Board writes: What types of errors is this guideline
addressing? Is this something that is a special problem for people with
disabilities, or is it a usability issue for all users? Also, using the term
"graceful" is very subjective.

Comment 2, (Ben Caldwell): Discussed at the May 6, 2004 telecon and assigned
action items.

Comment 3, (Doyle Burnett): See -
 <http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0390.html>
lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0390.html

Comment 4, (wendy chisholm): Andi writes:
examples added (to proposed wording)
<http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0268.html>
lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0268.html

Proposed wording adopted in 19 November 2004 Working Draft:
<http://www.w3.org/TR/2004/WD-WCAG20-20041119/#minimize-error>
www.w3.org/TR/2004/WD-WCAG20-20041119/#minimize-error

Comment 5, (Andi Snow-Weaver): Team C will propose a definition of "input
error" just to ensure that this 
success criteria is testable.

Proposed Action: Recommend closing this issue. Write back the Access Board
that this is a problem for people with disabilities as outlined in the "How
to Meet." doc. People with disabilities such as blindness, cognitive
difficulties, hand tremors etc., are more likely to make errors during
interaction with a web site than people who do not have disabilities, and
the consequences of mistakes are often higher because of compounded
difficulty recovering from the error. The committee does not believe this is
not simply a usability issue. Other items in the bug have been overcome by
events, because of rewording in subsequent drafts.


----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------------


Note: I have written most of the Technology Independent Techniques for this
Guideline and am willing to transfer them to any W3C document.
http://www.eramp.com/david/general/    There are 10 numbered techniques.
Once on the page, just click a number.


----------------------------------------------------------------------------
------------------------------------------------


I have a suggestion that might apply to all the Advisory items in the How to
Meet .Doc


The advisory section says


 "Although *not required* for conformance, the following additional
techniques should be considered." 


By saying the advisory techniques are "not required," are we not implying
that the core techniques are "required"? It seems to imply a requirement of
the core techniques.


----------------------------------------------------------------------------
-------------------------------------

 

Best

David MacDonald

 

.Access empowers people
            .barriers disable them.

 <http://www.eramp.com> www.eramp.com

 
Received on Monday, 12 December 2005 20:23:14 GMT

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