Confirmed users
1,396
edits
Accessibility/WebAccessibilityAPI: Difference between revisions
→Content traversal
| Line 939: | Line 939: | ||
}; | }; | ||
</pre> | </pre> | ||
===Virtual cursor=== | ===Virtual cursor=== | ||
| Line 960: | Line 952: | ||
Whenever the virtual cursor position is changed then ''cursor_moved'' event is fired. | Whenever the virtual cursor position is changed then ''cursor_moved'' event is fired. | ||
Questions/concerns | ===Questions/concerns=== | ||
* Do we need *is* method right on AccessibleElement or should we have Role interface having that method or should AccessibleElement return role taxa as a role. | |||
* Do we need to have "inContextOf" on AccessibleElement to check what the accessilbe belongs to. Note, native implementation doing some cache may be faster than tree traversal. If we need it then it's worth to consider *is* method too. | |||
* Do we need isAnyOf() method additionally? | |||
* Do we need to compare() method to compare two positions | |||
* Ensure that the virtual cursor is survivable. If it ends up in the hidden sub-tree for example. If subtee gets destroyed then cursor should be moved. If AccessiblePos doesn't have matching function then it's unclear where it should be moved. | * Ensure that the virtual cursor is survivable. If it ends up in the hidden sub-tree for example. If subtee gets destroyed then cursor should be moved. If AccessiblePos doesn't have matching function then it's unclear where it should be moved. | ||
* Also take into account walking to/from parent/child frames | * Also take into account walking to/from parent/child frames | ||
* Should it be outlined as moved? | * Should it be outlined as moved? | ||
* Yura: we should have async API for search. | |||
==Text== | ==Text== | ||