When to use UIA vs. AccChecker vs. AccExplorer32

Jun 6, 2008 at 5:34 PM

Dan asked the following question in the UIA Verify forum (http://www.codeplex.com/UIAutomationVerify/Thread/View.aspx?ThreadId=29155):
<o:p>    "Is there a guide or recommendation of the best or most recent tool to use?  Is AccExplorer32 going to be retired?"

I have copied the question to the AccChecker forum (here) - the answer is:

AccChecker and AccExplorer are complimentary.  Although AccChecker has some tree navigation capabilities, it does not display as much information as AccExplorer for the nodes.  The tree navigation capabilities of AccChecker are meant to give you a reasonable idea where in the tree the problem is (if this is not clear from the highlight).  On the other hand, AccChecker provides richer verifications, details on each error/warning, and an API to easily create automated test cases for the verifications you ran manually with AccCheckUI.

So if you want to browse the tree and look for detailed information for each node, AccExplorer is the better choice.

If you want to easily verify an entire UI by pointing a tool and scanning all the nodes, tabbing navigation, rules, states, etc., then AccChecker is the choice.

Also, AccChecker has the “Screen Reader” feature – with this feature you can discover very quickly if your UI’s programmatic access is broken – just scan the text in the “Screen Reader” tab – if you don’t see the texts that you would expect to see by observing the UI, then you know something is wrong.  Or if you see information that should not be there, again something is wrong (for example if you see a push button that has the name “MyBtnControl1”, you immediately will know that this name will not make sense to the user when read by a real screen reader).

Hope this helps.