Accessibility/IA2 1.3: Difference between revisions

Jump to navigation Jump to search
m
Line 28: Line 28:
## HyperlinkEvents - fire hyper link events
## HyperlinkEvents - fire hyper link events
## HypertextEvents - fire hyper text events
## HypertextEvents - fire hyper text events
# Interfaces
# Interfaces (?)
## davidb: Alexander do you mean something like IAccessible2 or more granular?
## davidb: Alexander do you mean something like IAccessible2 or more granular?
# Accessible Tree
# Accessible Tree (?)
## davidb: Alexander, what did you mean here?
## 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 fow which the current support is preserved.
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.
See [https://lists.linux-foundation.org/pipermail/accessibility-ia2/2010-June/001186.html IA2 list] for discussion.
Confirmed users
1,085

edits

Navigation menu