RE: Re issue 330: proposed wording to replace "programmatically identified"

The exercise of replacing difficult terms such as "programmatically
determined" with the proposed definition led to some interesting
results.  In most cases it seemed to work well. However, in the case of
Guideline 3.2 L2 SC1, the experiment
yielded the following:
<blockquote>
<include definition in success criterion>
 
1. Any extreme change of context is implemented in machine-readable form
(e.g., in markup, metadata, or a data model).
 
</include definition in success criterion>
</blockquote>
I'm concerned that this doesn't indicate clearly enough the *result*
we're looking for: providing advance notice of extreme changes of
context and/or making it clear that users shouldn't be subject to
*involuntary* changes of context such as meta redirect/refresh (both of
which can be accomplished through valid HTML 4.01 markup or in metadata)
 
I don't have a proposal at this point, but it seems like  something we
need to work on.
 
John
 

	-----Original Message-----
	From: w3c-wai-gl-request@w3.org
[mailto:w3c-wai-gl-request@w3.org] On Behalf Of John M Slatin
	Sent: Monday, August 09, 2004 8:42 am
	To: w3c-wai-gl@w3.org
	Subject: Re issue 330: proposed wording to replace
"programmatically identified"
	
	

	-         This is the second of several messages proposing new
wording for success criteria that contain one of the following phrases,
which were discussed during the 5 August WCAG WG call: 

	 

	The terms were listed in the agenda [1].

	1.    Derived programmatically (GL 1.3 L1 SC1 and SC2)

	2.    Programmatically identified (GL 3.2 L2 SC1)

	3.    Programmatically determined (GL 3.1 L2 SC2, and SC6)

	4.    Programmatically located (GL 3.1 L1 SC2 and GL 3.1 L2 SC1)

	 

	As I understood the discussion, people who participated in the
call agreed about the following (I don't remember whether there was
formal consensus):

	1.    The four terms should be reduced to two:

	a.     Proposal: replace "derived programmatically" and
"programmatically identified" with "programmatically determined."

	2.    Proposal: Define programmatically determined to mean "is
available in a standard machine-readable form (e.g., in a standard
markup, data model or metadata)"

	3.    Further attempts to define "programmatically located"
should be deferred until after the 11 August joint call with PFWG.

	 

	Further discussion off-list about potential ambiguities of the
word "standard" led to a further refinement of the definition of
"programmatically determined": Programmatically determined="available in
machine-readable form (e.g., in markup, metadata, or a data model)."

	There was a related discussion off-list about the term
"explicitly associated" (used in 1.1 L1)  The question was whether an
association that could be recognized by humans but not by user agents
would satisfy the intent of "explicitly associated."      The feeling
was that an association that could be recognized only by a human and not
by a user agent was not good enough.

	 

	Based on these discussions, I've taken the affected success
criteria and (1) replaced the now-obsolete terms (derived
programmatically and programmatically identified) with programmatically
determined and (2) replaced programmatically determined with the
definition language. I've done the same thing for 1.1, the only
occurrence of "explicitly associated" in the 30 July WD [2].

	 



	Success criteria that currently contain the phrase
programmatically identified


	Guideline 3.2  L2 SC1


	<current>

	1. Any extreme change of context is implemented in a manner that
can be programmatically identified.

	</current>

	<replace programmatically identified>

	1. Any extreme change of context is implemented in a manner that
can be programmatically determined.

	</replace programmatically identified>

	<include definition in success criterion>

	1. Any extreme change of context is implemented in
machine-readable form (e.g., in markup, metadata, or a data model).

	</include definition in success criterion>

	 
	[1]
http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0318.html
<http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0318.html> 

	[2] http://www.w3.org/TR/WCAG20/ <http://www.w3.org/TR/WCAG20/> 

	
	"Good design is accessible design." 
	John Slatin, Ph.D.
	Director, Accessibility Institute
	University of Texas at Austin
	FAC 248C
	1 University Station G9600
	Austin, TX 78712
	ph 512-495-4288, f 512-495-4524
	email jslatin@mail.utexas.edu
	web http://www.utexas.edu/research/accessibility/
<http://www.utexas.edu/research/accessibility/>