Hi. There's interesting discussion about editable vs unavailable state happening at Mozilla bug - https://bugzilla.mozilla.org/show_bug.cgi?id=733382. I put here some summary of it.
The ATK spec says: "Indicates the user can change the contents of this object" - http://www.pygtk.org/docs/pygtk/atk-constants.html#atk-state-type-constants. That means readonly and disabled text controls shouldn't be exposed as editable. ATs might be interested to know whether the object is potentially editable to put it into navigation order. Also that makes it similar to other 'able' states like expandable or multiselectable except focusable state which is sort of opposite to absent enabled state. So let's consider an exampe: <p contentEditable="true" aria-disabled="true"> Currently: no enabled state, no editable state. This paragraph exposed absolutely identically to plain <p>. Proposed: no enabled state, editable state is presented. AT understand this paragraph is sort of control and can be used for typing when enabled. Please let me know what you think. Thank you. Alex _______________________________________________ gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
