From lukastyr...@gmail.com on February 17, 2013 23:05:02
What steps will reproduce the problem? 1. Create any app whic uses the tree control, or use the demo.
2. Try to interact with the control using any screen reader (e.g. nvda, jaws).
3. See what happens. What is the expected output? What do you see instead? The screen reader reads node text, level, it's collapsed/expanded state, possibly checked/unchecked attributes. What version of the product are you using? On what operating system? Latest. Please provide any additional information below. Would it be possible to implement iaccessible/msaa interfaces for this control? Because of it's wide adoption by the community, ot would help make a lot of apps more accessible.
Original issue: http://code.google.com/p/virtual-treeview/issues/detail?id=320
From lukastyr...@gmail.com on February 17, 2013 23:05:02
What steps will reproduce the problem? 1. Create any app whic uses the tree control, or use the demo.
2. Try to interact with the control using any screen reader (e.g. nvda, jaws).
3. See what happens. What is the expected output? What do you see instead? The screen reader reads node text, level, it's collapsed/expanded state, possibly checked/unchecked attributes. What version of the product are you using? On what operating system? Latest. Please provide any additional information below. Would it be possible to implement iaccessible/msaa interfaces for this control? Because of it's wide adoption by the community, ot would help make a lot of apps more accessible.
Original issue: http://code.google.com/p/virtual-treeview/issues/detail?id=320