That's correct. As noted in this old thread, Decker avoids exposing raw keyboard input (so far) because programs which depended upon it would be unusable on devices like phones and tablets which do not have a physical keyboard.
In the future maybe some compromise is possible, like allowing button widgets to be annotated to trigger when a keyboard key "shortcut" is pressed, but I'd need to give it some careful thought.