With regards to the "Click static text" issue, it might be that the text itself doesn't have a clickable action associated with it. Button components have 2 visible elements to it, the outer bounding box, and the text inside it. In typical usage, a mouse click within the bounding box triggers the action of the button. The click action can be associated with the inclosed text, the bounding box, or both. If the text has no clickable action, it seems reasonable that "missing value" would be returned, even if it is able to find the text itself. Automator may have incorrectly assumed the click action was associated with the text instead of the bounding box, or if your program is particularly nasty, the click action may be just associated with a certain x y position on the screen. Somehow you have to get the name of the actual button box,		 and script a click action on that box rather than the text.
i've looked everywhere in "accessibility inspector", suspecting that it may be hidden neatly behind something. but i don't think you can move anything out of the way in accessibility inspector. but, i've found some pretty thorough scripts that extrapolate every possible UI element (or so they say ....) and gone through every single one of them and not found the secret button i'm looking for. so i don't know