Re: Response to Issue 659/660/386

> So if I don't use a form element but use a JS keyboard event handler to perform *exactly* the same functionality my content would fail - but if I use a form element it would pass? The effect on the end user is exactly the same. I can't support anything which requires one method to accomplish something where the result for the end user is the same.

It is (a)nother case of not messing with default user-agent features.

This scenario also fits into the last clause:
“unless the keyboard shortcut for a user interface component is only active when that component has focus.”

Pressing enter to submit a form only works when an input in the form is in focus, therefore that “short-cut” isn’t in scope. (I think that was the reason for including the focus aspect in the first place?)

-Alastair