We use a single sign-on Product called "Imprivata OneSign", it reads he screen and when it sees certain fields it fills in people's passwords. One of the methods they are doing this within Internet Exploer is to use the Microsoft UI Automation API.
Whenever Imprivata software calls this API Acrobat (Full and Reader) will go into Accessibility mode and try to call Imprivata DLL's (saw this via Proc Manager) and then it wants to start Tagging each document and do all kinds of other fun stuff. I am looking for an option to not have Acrobat go into this mode whenever it sees the Microsoft Automation API called. As a test we even used a MS UI API simulator application and it it also does it, so it's not just the Imprivata OneSign application.
Any help is greatly appreciated as it's taken our users a ton of time waiting for the tagging to happen, they open hundrets of PDF's a day!
From our research, we have found that once Microsoft UIA (User Interface Automation) is activated it is causing Acrobat to go into Accessibility mode. Which is calling on our DLL for some reason, resulting in Acrobat wanting to tag and index each document. As long as UIA is not activated we do not see this happen. Onesign does use this technology in certain situations. We also tried removing Adobe plug-in Accessibility.api from (C:\Program Files (x86)\Adobe\Reader 10.0\Reader\plug_ins) and this did not help.
Even testing without Onesign installed but with UIA enabled we still see the same behavior. Using the MS Inspect tool (http://msdn.microsoft.com/en-us/library/windows/desktop/dd318521(v=vs.85).aspx) with UIA activated, upon opening a PDF we see the same Acrobat behavior. Deactivating UIA using the MS Inspect tool, the issue goes away.
We are looking to Adobe for a way to turn tagging and indexing off or help to find out why UIA is interfering with this process.