Accessibility/IA2 1.3: Difference between revisions

Accessibility/IA2 1.3 (view source)

Revision as of 05:13, 12 March 2011

198 bytes added , 12 March 2011

no edit summary

Surkov.alexander

Confirmed users

1,396

edits

@@ Line 3: / Line 3: @@
 =Proposal=
-==Registry API==
-Propose: a way to enable set of features.
-<pre>
-interface IAccessibleApplication2 : public IAccessibleApplication
-{
-  /**
-   * Enable set of features. Return set of features that were enabled.
-   */
-  HRESULT requestFeature(
-    [in] long features,
-    [out] long supportedFeatures]
-};
-</pre>
-Initially proposed features:
-# Events
-## ShowHideEvents - fire show/hide events
-## ReorderEvent - fire reorder event
-## TextEvents - fire text inserted/deleted/modified events
-## TableEvents - fire table events
-## HyperlinkEvents - fire hyper link events
-## HypertextEvents - fire hyper text events
-# Interfaces (?)
-## davidb: Alexander do you mean something like IAccessible2 or more granular?
-# Accessible Tree (?)
-## davidb: Alexander, what did you mean here?
-Server implementation: it's up to the server to define set of base features that's always enabled (e.g. focus events); others are considered as optional and should be enabled on request. In order not to break existing AT, the server should maintain a whitelist of ATs for which the current support is preserved.
-See [https://lists.linux-foundation.org/pipermail/accessibility-ia2/2010-June/001186.html IA2 list] for discussion.
 ==Relations==
@@ Line 236: / Line 203: @@
 See [https://bugzilla.mozilla.org/show_bug.cgi?id=637578 bug 637578] for original idea.
+=Other ideas=
+==Registry API==
+Note: IsWinEventHookInstalled may do all we need. See [https://lists.linux-foundation.org/pipermail/accessibility-ia2/2010-July/001209.html Mick's suggestion].
+Propose: a way to enable set of features.
+<pre>
+interface IAccessibleApplication2 : public IAccessibleApplication
+{
+  /**
+   * Enable set of features. Return set of features that were enabled.
+   */
+  HRESULT requestFeature(
+    [in] long features,
+    [out] long supportedFeatures]
+};
+</pre>
+Initially proposed features:
+# Events
+## ShowHideEvents - fire show/hide events
+## ReorderEvent - fire reorder event
+## TextEvents - fire text inserted/deleted/modified events
+## TableEvents - fire table events
+## HyperlinkEvents - fire hyper link events
+## HypertextEvents - fire hyper text events
+# Interfaces (?)
+## davidb: Alexander do you mean something like IAccessible2 or more granular? - alex: more granular
+# Accessible Tree (?)
+## davidb: Alexander, what did you mean here?
+Server implementation: it's up to the server to define set of base features that's always enabled (e.g. focus events); others are considered as optional and should be enabled on request. In order not to break existing AT, the server should maintain a whitelist of ATs for which the current support is preserved.
+See [https://lists.linux-foundation.org/pipermail/accessibility-ia2/2010-June/001186.html IA2 list] for discussion.