- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Wed, 27 Apr 2005 17:17:22 -0500
- To: <w3c-wai-gl@w3.org>
- Message-ID: <6EED8F7006A883459D4818686BCE3B3B7AE330@MAIL01.austin.utexas.edu>
A request for clarificaiton. The last of the 6 proposals (all that remains of the Guideline Formerly Known as 4.2) reads as follows: <blockquote> [6] New GL 1.3 Level 1 SC <proposal> The role, state and value of every element of the web content can be programmatically determined. Elements whose states and values can be changed via the user interface can also be changed programmatically. </proposal> </blockquote> As written, the last sentence says that *elements* whose state and values can be changed via the user interface can also be changed programmatically." I'm not sure I understand what's supposed to be programmatically changeable here. As written, what gets changed programmatically are *elements* whose "state and values" have been changed via the user interface. Inn other words, this means that when something happens in the user interface that changes either the "state" of an "element" or its "value" (but not its "role"?), then the "element" itself can (or should?) be changed programmatically. Is that right? Would there ever be a situation in which something could happen at the level of the UI that would result in a change of *role* for the element? If so, does that change have to be available programmatically as well? John The previous sentence talks about "role and state values." "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 Wednesday, 27 April 2005 22:17:27 UTC