Best Answers
Hi Sam ,
Accessibility Mode:
It is an interface available in Application Modeller which can be used for Windows and Web based applications. It is dependent upon how the application has been built.
Why Accessibility Mode:
If Application Navigator is taking too much time to identify the element or in some cases if it doesn't display element "Using MS tools to evaluate elements attributes to potentially modify an Active accessibility within application modeller so that it can be used".
When spied with Accessibility mode it will take some time to load the entire tree view as shown below. Most of the attributes might be blank and we can uncheck them and based on the selection we can uncheck some of the parent elements to uniquely identify the element. To uniquely identify the element, use match index.
why this mode couldn't be used and shown in web-based applications and websites?
Interface Delays:
Application modeller for accessibility interface can be extremely large containing all the elements .Its therefore can be extremely slow for a automation tool to navigate from one element to another .
The above scenario would force the developer to introduce large delays on wait stages such as intelligent wait or absolute wait need to be introduced for the functionality to work .
Some applications are not AA interface maybe they are built using a platform that is not compatible with AA or the element not built in accessible way or functionality disable in some other way.
In this type of situation may be its better to go with Surface Automation .
Hope this helps
Regards,
Satish Gunturi,
Senior Consultant,
Ignite IPA Pvt Ltd
------------------------------
Satish Gunturi
------------------------------
Hi Sam ,
Accessibility Mode:
It is an interface available in Application Modeller which can be used for Windows and Web based applications. It is dependent upon how the application has been built.
Why Accessibility Mode:
If Application Navigator is taking too much time to identify the element or in some cases if it doesn't display element "Using MS tools to evaluate elements attributes to potentially modify an Active accessibility within application modeller so that it can be used".
When spied with Accessibility mode it will take some time to load the entire tree view as shown below. Most of the attributes might be blank and we can uncheck them and based on the selection we can uncheck some of the parent elements to uniquely identify the element. To uniquely identify the element, use match index.
why this mode couldn't be used and shown in web-based applications and websites?
Interface Delays:
Application modeller for accessibility interface can be extremely large containing all the elements .Its therefore can be extremely slow for a automation tool to navigate from one element to another .
The above scenario would force the developer to introduce large delays on wait stages such as intelligent wait or absolute wait need to be introduced for the functionality to work .
Some applications are not AA interface maybe they are built using a platform that is not compatible with AA or the element not built in accessible way or functionality disable in some other way.
In this type of situation may be its better to go with Surface Automation .
Hope this helps
Regards,
Satish Gunturi,
Senior Consultant,
Ignite IPA Pvt Ltd
------------------------------
Satish Gunturi
------------------------------
