Microsoft UI Automation is the new accessibility framework for Microsoft Windows, available on all operating systems that support Windows Presentation Foundation (WPF). see - http://msdn2.microsoft.com/en-us/library/ms747327.aspx
I was hoping that xamRibbon will fully support this so that the if we decide to use this in our application then we automatically have an accessible application. However I have noticed that this currently isn't the case. e.g. ButtonTool items aren't accessible but RadioButtonTool are. I had hoped that using the AutomationProperties as extension properties (in xaml) to the control will suface into the UI, but they don't .
Is there anything I can do to make this work from my end? Will the release version fully support UI Automation?
I would be happy to provide further details and examples. If you require them, please let me know.
Hello Hirani -
Thanks for your post. You are correct that we do not have support for WPF's UI Automation in the Preview build of the XamRibbon. At this point it appears that UIAutomation support will not make it into the final release. We are familiar with how UI Automation works - in fact the XamDataGrid, XamDataCarousel and XamCarouselListBox (all released as part of NA for WPF 7.1) all have support for UIAutomation.
We recognize that this is important framework functionality that developers will expect all WPF components to support, but unfortunately we are not able to squeeze this development task into the 7.2 schedule. After much discussion we've made the decision to release the XamRibbon without UI automation support, and add this support in a follow-on hotfix or release.
I hope this helps.
JoeM
"joem" wrote in message news:10776@forums.infragistics.com... Hello Hirani - Thanks for your post. You are correct that we do not have support for WPF's UI Automation in the Preview build of the XamRibbon. At this point it appears that UIAutomation support will not make it into the final release. We are familiar with how UI Automation works - in fact the XamDataGrid, XamDataCarousel and XamCarouselListBox (all released as part of NA for WPF 7.1) all have support for UIAutomation. We recognize that this is important framework functionality that developers will expect all WPF components to support, but unfortunately we are not able to squeeze this development task into the 7.2 schedule. After much discussion we've made the decision to release the XamRibbon without UI automation support, and add this support in a follow-on hotfix or release. I hope this helps. JoeM http://forums.infragistics.com/forums/p/832/10776.aspx#10776
Is there a fix in the works for this yet? Thanks.
Thanks for the quick reply. Any suggested workarounds?
You should contact the support group so you can be notified when the next 8.2 hotfix is released.
I'm sorry but after some further research it seems that the internal version that I was using did include automation support but automation support had not made it into the release version. This should be included in the next hotfix of 8.2 - note this did not make it into the first 8.2 hotfix which is either available right now or will be very shortly but will be in the 2nd hotfix.
We did not provide automation peers for the xamRibbon tools, etc. until the 2008 Vol 2 release. When I run one of the sample applications and use UISpy against that version it does see the ButtonTool as an element, can use the invoke pattern, etc.
I have the same problem, I want to do UI automation testing using on a WPF application that use some infragistics controls. Some of them (Like the Ribbon's buttonTools or ContentPane) does not support UI automation.
For example, when I have a ButtonTool in a Ribbon and I look at the application using UISpy, I do not see a control of type button, I see an image (ControlType = ControlType.Image)
If I set some automation properties (e.g AutomationProperties.AutomationID), these properties are not visible within UI spy of UIAVerify.
Why does Infragistics WPF controls does not implements providers for UIAutomation?
Thanks