- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Wed, 17 Jul 2019 08:57:55 +0000
- To: Gerard Copinga <gerard@technobility.nl>
- CC: W3C WAI ig <w3c-wai-ig@w3.org>
- Message-ID: <ED10EB30-CFC7-4621-9CBB-6AD58E1051DB@nomensa.com>
Hi Gerard, I agree with your interpretation here: > my assumption is that the video player as a whole is not a User Interface Component; only the buttons and links within the video can be seen as User Interface Components. A UI component is more granular than a whole video player with multiple controls. There might be some exceptions, but my rule of thumb is that a UI component is something you tab to. (E.g. button, set of radio buttons, drop-down select etc.) Therefore a single-character keyboard short-cut (that can’t be remapped) would be an issue, even if it only applies within the video player iframe. However, it is worth checking if the user can turn-off or remap those keyboard short cuts at the YouTube level, which might then apply across embedded players holistically (like caption settings). I haven’t checked, but would be interested to find out. > That would mean that the shortcuts can only work if the focus is on the button (or link) to which the shortcut applies. So the 'k' can only work when the focus is on the play/pause button. That would undermine the whole point of having the short-cut, which is to allow quick access to that feature whilst it is not in focus. The desirable outcome is to allow re-mapping instead (e.g. to cntl-k) so it doesn’t get activated accidentally by voice input. Kind regards, -Alastair From: Gerard Copinga Anyone else have any thoughts on the subject? I am really interested in how other people see this. Especially beacause of the impact it has on evaluating and passing/failing websites that use embedded YouTube players....
Received on Wednesday, 17 July 2019 08:58:21 UTC