W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2004

Re issue 330: Proposed wording to replace "derived programmatically"

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Mon, 9 Aug 2004 08:42:31 -0500
Message-ID: <C46A1118E0262B47BD5C202DA2490D1A03317F9B@MAIL02.austin.utexas.edu>
To: <w3c-wai-gl@w3.org>
-         This is the first 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 derived
programmatically


Guideline 1.3 L1 SC1


<current>

1. Structures and relationships within the content can be derived
programmatically. [I]

</current>

<replace derived programmatically >

1. Structures and relationships within the content can be
programmatically determined.

</replace derived programmatically>

 

<include definition in success criterion>

1. Structures and relationships within the content are provided in
machine-readable form (e.g., in markup, metadata, or a data model).

</include definition in success criterion>


Guideline 1.3 L1 SC2


<current>

2. Emphasis can be derived programmatically. [I]

</current>

<replace derived programmatically>

2. Emphasis can be programmatically determined.

</replace derived programmatically>

<include definition in success criterion>

2. Emphasis is provided 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/> 


 

 
Received on Monday, 9 August 2004 13:42:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:17:58 UTC