Based on my experience, if the elements on the screen are indexed but unnamed, then AutoInput cannot interact with them. For difficult apps, I use Swapps to do various Tasker things. But you could simply make a voice pattern for listing the elements on the screen. Create a simple scene with a text element and a task that destroys it (in case it exists in BG), creates it, and passes par1 into text1. Then have your voice command do AutoInput UI Query, and pass the data to your scene creator task and it will show you.
Someone asked me something similar a while back, and I think I put up something on my Google site. At Starf1337.net, click Resources, Tasker, and... I think it is "&Click(Text)" or something.
Don't worry, there are no ads or any crap on my site, it is just a repository.
-Adam