Yeah just tested this again for you steven to be sure. in jaws 10 at least, it certainly does matter, which cursor is active when you first enter that jawsControlF find box, and where the jaws cursor is onscreen. just as, indeed it would, before instituting the findGraphic function within a script, as jackie suggested. I thought for a horrible moment, that they weren't even gunna allow you to have the pc cursor active during the actual find Dialog box exploration before hitting enter, so's you could accurately confirm that the right find stuff was in the edit box, but, this wasn't true, so long as jaws cursor is active before you enter it, and it is above the labelled graphic in question, and graphics verbosity is set to, labelled , then it should, note I say Should, find it. note too, though, that this means, that you gotta hav jawsCursor active, hit the insertControlF hotkey to bring up the jawsFind dialog, then switch the jolly thing back to pc cursor, so's your readCurrentLine etc, hotkeys, relate to pc cursor and will correctly identify the stuff in the edit box of your findGraphic details etc, then hit enter. That's kinda annoying and it would be nice if it by default, just auto set the active cursor back to pc Cursor, as you'd intuitively expect it might do, so that hitting readCurrentLine would read the right stuff in the field you expect it should, instead of staying in jaws Cursor mode and thus reading non-relevant stuff. hth. __________ Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at //www.freelists.org/list/jawsscripts