W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2018

Re: Response to Issue 659/660/386

From: Alastair Campbell <acampbell@nomensa.com>
Date: Fri, 5 Jan 2018 17:18:29 +0000
To: James Nurthen <james.nurthen@oracle.com>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <687575AA-560C-442E-AA76-4ECD872788E0@nomensa.com>
> 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?)


Received on Friday, 5 January 2018 17:19:07 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:21 UTC