Lately, I’ve seen some awkward attempts at simulating a text field/activation button combination, such as one would find on a login page. On one such web page, the user types data in a couple of fields and then either presses Enter or clicks a button. I’ve seen some people develop three separate slides for this and use incorrect keys to proceed, actually training users to do something in simulation they would not do in a real system. You can simulate it accurately and all in one slide if you set up your Captivate interactions as follows:

1. Put a Text Entry Box over the first field and instruct users to continue by pressing the Tab key (e.g. “Type me@me.com in the Email field, and then press Tab“). In the Text Entry Box’s properties, assign the Tab key to continue.
2. Put a Text Entry Box over the second field, and instruct users to continue by clicking the button (e.g. “Type abc123 in the Password field, and then click the Sign in button”). In the Text Entry Box’s properties, do not assign a shortcut key. Especially avoid Enter, since that key is overridden by the browser’s controls. Do assign a button and configure it as transparent. Do enable the Password option, which makes the password appear as asterisks more like the real thing. Do enable the Cass-sensitive option, since most passwords are case-sensitive.
3. On the Timeline, make sure the first field interaction ends before the second field interaction begins.

It is easier to understand what I am on about if you see it, so here is an [1] example. The [2] source file is here.