Proposal to restructure the success criteria for B.2.4

As I was doing the techniques for B.2.4 (Do not automatically generate 
equivalent alternatives or reuse previously authored alternatives 
without author confirmation, except when the function is known with 
certainty. [Priority 1]) I noticed that the success criteria could be 
more clear:

So I propose we change the success criteria from:

1: When the author inserts an unrecognized non-text object, the tool 
must never insert an automatically generated text equivalent (e.g. a 
label generated from the file name).

2: When the author inserts a non-text object for which the tool has a 
previously authored equivalent alternatives (i.e. created by the author, 
tool designer, pre-authored content developer, etc.), but the function 
of the object is not known with certainty, the tool must always prompt 
the author to confirm insertion of the equivalent. However, where the 
function of the non-text object is known with certainty (e.g. "home 
button" on a navigation bar, etc.), the tool may automatically insert 
the equivalent.

To:

1: The tool must never use automatically generated equivalent 
alternatives for a non-text object (e.g. a short text label generated 
from the file name of the object).

2: When a previously authored equivalent alternative is available (i.e. 
created by the author, pre-authored content developer, etc.), the tool 
must prompt the author to confirm insertion of the equivalent unless the 
function of the non-text object is known with certainty (e.g. "home 
button" on a navigation bar, etc.).



Cheers,
Jan

Received on Friday, 2 December 2005 16:08:42 UTC