107
edits
Accessibility/Comparisons:States: Difference between revisions
adding TBD roles
(updated per a11y newsgroup discussion) |
(adding TBD roles) |
||
| Line 319: | Line 319: | ||
equivalent to saying that an object is 'hidden'.</td> | equivalent to saying that an object is 'hidden'.</td> | ||
</tr> | </tr> | ||
</table> | |||
== States To Be Discussed / Possibly Unnecessary == | |||
<table border="1"> | |||
<tr> | |||
<td>ANIMATED</td> | |||
<td>ANIMATED (proposed) or add custom state</td> | |||
<td>Image + custom description?</td> | |||
<td>Object's visual representation is changing or moving | |||
rapidly; it is dynamic not static. This state may be applied to an | |||
object during an animated 'effect' and be removed from the object once | |||
its visual representation becomes static. Note: | |||
Some applications, notably content viewers, may not be able to detect | |||
all kinds of animated content. Therefore the absence of this state | |||
should not be taken as definitive evidence that the object's visual | |||
representation is static; this state is advisory.</td> | |||
</tr> | |||
<tr> | |||
<td>EXTSELECTABLE</td> | |||
<td>add custom state</td> | |||
<td>Needed?</td> | |||
<td>Object can extend its selection.</td> | |||
</tr> | |||
<tr> | |||
<td>FLOATING</td> | |||
<td>add custom state</td> | |||
<td></td> | |||
<td>Object is not clipped to the boundary of the parent | |||
(i.e. it does not auto-move with the parent).</td> | |||
</tr> | |||
<tr> | |||
<td>HOTTRACKED</td> | |||
<td>add custom state</td> | |||
<td>Really needed?</td> | |||
<td>Object's appearance has changed for a mouseover.</td> | |||
</tr> | |||
<tr> | |||
<td>MARQUEED</td> | |||
<td>ANIMATED (proposed)</td> | |||
<td>Same as animated</td> | |||
<td>The object is constantly changing and fleeting across | |||
the screen.</td> | |||
</tr> | |||
<tr> | |||
<td>MOVEABLE</td> | |||
<td>add custom state</td> | |||
<td></td> | |||
<td>Object can be moved or dragged around the screen. </td> | |||
</tr> | |||
<tr> | |||
<td>SELFVOICING</td> | |||
<td>add custom state</td> | |||
<td></td> | |||
<td>Object is self-voiced by the application, so an AT | |||
should not speak this object. </td> | |||
</tr> | |||
<tr> | |||
<td></td> | |||
<td>ARMED</td> | |||
<td>What's the difference from pressed? | |||
There's an UA action "press" that will execute the action; does not | |||
actually push down the button until the user says "stop". :-)</td> | |||
<td>The object is armed. Usually used on buttons that have | |||
been pressed but not yet released, and the mouse pointer is still over | |||
the button. </td> | |||
</tr> | |||
<tr> | |||
<td></td> | |||
<td>STALE</td> | |||
<td></td> | |||
<td>Index associated with this object has changed since the | |||
user accessed the object. The information returned for this object may | |||
no longer be synchronized with the application state. </td> | |||
</tr> | |||
<tr> | |||
<td></td> | |||
<td>TRANSIENT</td> | |||
<td></td> | |||
<td>Object is changing or moving rapidly. An assistive | |||
technology should not add a property change listener to an object with | |||
transient state, as that object will never generate any events. | |||
Transient objects are typically created to answer ATK accessibility | |||
method queries, but otherwise do not remain linked to the underlying | |||
object (for example, those objects underneath lists, tables, and trees, | |||
where only one actual UI component does shared rendering duty for all | |||
of the data objects underneath the actual list/table/tree elements). </td> | |||
</tr> | |||
<tr> | |||
<td></td> | |||
<td>TRUNCATED</td> | |||
<td></td> | |||
<td>Object is truncated, such as a numerical value in a | |||
spreadsheet cell. </td> | |||
</tr> | |||
<tr> | |||
<td></td> | |||
<td>SUPPORTS_TYPEAHEAD (proposed)</td> | |||
<td></td> | |||
<td>Object implements some form of | |||
¨typeahead¨ or pre-selection behavior whereby entering | |||
the first character of one or more sub-elements causes those elements | |||
to scroll into view or become selected. Subsequent character input may | |||
narrow the selection further as long as one or more sub-elements match | |||
the string. This state is normally only useful and encountered on | |||
objects that implement [http://gnome.org/%7Ebillh/at-spi-new-idl/html/html/interfaceAccessibility_1_1Selection.html Selection]. | |||
In some cases the typeahead behavior may result in full or partial | |||
¨completion¨ of the data in the input field, in which | |||
case these input events may trigger text-changed events from the source.</td> | |||
</tr> | |||
<tr> | |||
<td></td> | |||
<td>OPAQUE</td> | |||
<td></td> | |||
<td>Object paints every pixel within its rectangular | |||
region. A non-opaque component paints only some of its pixels, allowing | |||
the pixels underneath it to "show through". A component that does not | |||
fully paint its pixels therefore provides a degree of transparency. </td> | |||
</tr> | |||
<tr> | |||
<td></td> | |||
<td>SENSITIVE</td> | |||
<td></td> | |||
<td>Object can be interactive, although it may currently be | |||
read-only or not enabled (grayed out). STATE_SENSITIVE usually | |||
accompanies STATE_ENABLED for user-actionable controls, but may be | |||
found in the absence of STATE_ENABLED if the current visible state of | |||
the control is "disconnected" from the application state. In such | |||
cases, direct user interaction can often result in the object gaining | |||
STATE_SENSITIVE, for instance if a user makes an explicit selection | |||
using an object whose current state is ambiguous or undefined.</td> | |||
</tr> | |||
</table> | </table> | ||