diff --git a/techniques/failures/F99.html b/techniques/failures/F99.html index 6cc68da54e..8fe26f43cc 100644 --- a/techniques/failures/F99.html +++ b/techniques/failures/F99.html @@ -31,7 +31,7 @@
The test procedure suggests asking the author (often the developer of the site) whether keyboard shortcuts are used. If that information is trusted then the procedure can be simpler than pressing all the keys.
The success criterion does not apply when single key shortcuts are only active when interface elements have the focus, for example, a select
element. Here, pressing a letter key is used for fast navigation within the select options.
Viewing page scripts and searching for typical keyboard event handlers like document.addEventListener('keydown' ...)
or the presence of the .keycode
attribute
+
Viewing page scripts and searching for typical keyboard event handlers such as document.addEventListener('keydown' ...)
or the handling of keyboard-related event properties with code such as .key
, .code
, .charCode
, or .keyCode
may establish the presence of scripts that intercept keyboard shortcuts without modification keys like ALT or Ctrl being held down at the same time. As there are several ways of implementing character key events, this method is not considered reliable.
Some browsers employ single key shortcuts with Shift. For example, Firefox opens a page search when pressing Shift + / and a search in page links when pressing Shift + '. In these cases, it will be necessary to press Esc or click an empty part of the page to remove the focus from the browser input.