Correct F99 - keyCode is not an attribute

patrickhlauke · patrickhlauke · commit b8b5569ffa61 · 2025-05-01T08:48:05.000+01:00
Closes #4344
diff --git a/techniques/failures/F99.html b/techniques/failures/F99.html
@@ -31,7 +31,7 @@ <h2>Description</h2>
     <p>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.</p>
 
     <p>The success criterion does not apply when single key shortcuts are only active when interface elements have the focus, for example, a <code class="language-html">select</code> element. Here, pressing a letter key is used for fast navigation within the select options.</p>
-    <p>Viewing page scripts and searching for typical keyboard event handlers like <code class="language-javascript">document.addEventListener('keydown' ...) </code> or the presence of the <code class="language-javascript">.keycode</code> attribute
+    <p>Viewing page scripts and searching for typical keyboard event handlers like <code class="language-javascript">document.addEventListener('keydown' ...) </code> or the handling of event properties like <code class="language-javascript">key</code>, <code class="language-javascript">code</code>, <code class="language-javascript">charCode</code>, or <code class="language-javascript">keyCode</code>
       may establish the presence of scripts that intercept keyboard shortcuts without modification keys like <kbd>ALT</kbd> or <kbd>Ctrl</kbd> being held down at the same time. As there are several ways of implementing character key events, this method is not considered reliable.</p>
     <p>Some browsers employ single key shortcuts with <kbd>Shift</kbd>. For example, Firefox opens a page search when pressing <kbd>Shift</kbd> + <kbd>/</kbd> and a search in page links when pressing <kbd><kbd>Shift</kbd> + <kbd>'</kbd></kbd>. In these cases, it will be necessary to press <kbd>Esc</kbd> or click an empty part of the page to remove the focus from the browser input.</p>
   </section>

-Original file line number
+Diff line change
     <p>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.p>
     <p>The success criterion does not apply when single key shortcuts are only active when interface elements have the focus, for example, a <code class="language-html">selectcode> element. Here, pressing a letter key is used for fast navigation within the select options.p>
 -    <p>Viewing page scripts and searching for typical keyboard event handlers like <code class="language-javascript">document.addEventListener('keydown' ...) code> or the presence of the <code class="language-javascript">.keycodecode> attribute
 +    <p>Viewing page scripts and searching for typical keyboard event handlers like <code class="language-javascript">document.addEventListener('keydown' ...) code> or the handling of event properties like <code class="language-javascript">keycode>, <code class="language-javascript">codecode>, <code class="language-javascript">charCodecode>, or <code class="language-javascript">keyCodecode>
       may establish the presence of scripts that intercept keyboard shortcuts without modification keys like <kbd>ALTkbd> or <kbd>Ctrlkbd> being held down at the same time. As there are several ways of implementing character key events, this method is not considered reliable.p>
     <p>Some browsers employ single key shortcuts with <kbd>Shiftkbd>. For example, Firefox opens a page search when pressing <kbd>Shiftkbd> + <kbd>/kbd> and a search in page links when pressing <kbd><kbd>Shiftkbd> + <kbd>'kbd>kbd>. In these cases, it will be necessary to press <kbd>Esckbd> or click an empty part of the page to remove the focus from the browser input.p>
   section>