- From: Ian B. Jacobs <ij@w3.org>
- Date: Tue, 24 Sep 2002 13:58:43 -0700
- To: Richard Schwerdtfeger <schwer@us.ibm.com>
- CC: Philippe Le Hegaret <plh@w3.org>, Ray Whitmer <rayw@netscape.com>, w3c-wai-ua@w3.org, w3c-wai-ua-request@w3.org
Richard Schwerdtfeger wrote: > Ian, > > Regarding the proposed wording to address state information I believe it is > important that we define the correct terminology as it crosssections > accessibility infrastructure terminology. Note: we may want to extend > content value to include text of a document element such as a text input > field. > > I propose using the following definitions to the working group and then > expanding on Ian's proposed changes to incorporate these definitions: > > > Content state - Document content has a condition of being in a stage or > form during its use known as its "state." The state of document content is > ususally defined in discrete pre-defined values as should be known by > assistive technologies designed to support the document. Examples of > possible object states are: has focus, selected, visible, is selecteable, > checked, focused, activated, pressed, expanded, collapsed, iconified, > editable, multi-line, resizable, vertical, horizontal, collapsible, > expandable, and enabled. > > Content selection - A collection of document content often selected by the > user through some means. So "is selected" refers to a state of a piece of content, whereas "the selection" refers to the set of all things selected? > Content value - An amount assigned to document content. Some document may > have an assigned value that may change during the course of its use. An > example of a the use of content value is the currently value of an HTML > selection object. I'm mostly interested in hearing from Ray and Philippe whether this aligns with the DOM model. Thanks Rich! - Ian -- Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs Tel: +1 718 260-9447
Received on Tuesday, 24 September 2002 17:03:23 UTC