The keystroke-buffer approach is the right one for layout conversion; a character-level table would fall over on Shift+2 immediately, as you show. The part I would tighten is the fail-open on unknown field types: if UI Automation can't tell whether a field is a password, I'd rather treat it as one (no buffer, thud on Pause) than risk keeping keystrokes from a custom password widget. The console rule of never using Ctrl+C to read a selection is the same kind of conservative default, and it fits the rest of the design well.