diff --git a/‎The Accessibility Tree - A Training Guide for Advanced Web Development/index.htm‎
Lines changed: 4 additions & 4 deletions b/‎The Accessibility Tree - A Training Guide for Advanced Web Development/index.htm‎
Lines changed: 4 additions & 4 deletions
@@ -1963,11 +1963,11 @@ <h3>
 A native active element such as a standard link or button is already keyboard accessible, and will automatically process the onClick handler when attached, even when Enter is pressed using the keyboard.
 </p>
 <p>
-However, a simulated active element such as a DIV or SPAN will not trigger an onClick handler when Enter is pressed using the keyboard. Instead, tabindex must be used to manage focus movement, and a redundant onKeyUp or onKeyPress must be added in addition to the onClick handler, in order to ensure accessibility for both sighted mouse users and keyboard only users.
+However, a simulated active element such as a DIV or SPAN will not trigger an onClick handler when Enter is pressed using the keyboard. Instead, tabindex must be used to manage focus movement, and a redundant onKeyDown or onKeyUp must be added in addition to the onClick handler, in order to ensure accessibility for both sighted mouse users and keyboard only users.
 </p>
 <p>
 <i>
-(The reason why onKeyUp is preferable to onKeyDown in such cases, is because onKeyDown will fire repeatedly when a key is held down, but onKeyUp will not.)
+(Note: onKeyDown will fire repeatedly when a key is held down, but onKeyUp will not.)
 </i>
 </p>
 <p>
@@ -2015,7 +2015,7 @@ <h3>
 <ul><li>
 When JAWS is in Virtual Cursor Mode for navigating web content, JAWS will activate the onClick event when the Enter key is pressed on an element.
 </li><li>
-When JAWS is in Applications/Forms Mode however, JAWS will activate the onKeyDown/onKeyPress/onKeyUp events instead, and not the onClick.
+When JAWS is in Applications/Forms Mode however, JAWS will activate the onKeyDown/onKeyUp events instead, and not the onClick.
 </li></ul>
 <p>
 For native active elements such as standard links and buttons, this usually causes no problems.
@@ -2068,7 +2068,7 @@ <h3>
 <ul><li>
 When NVDA is in Browse Mode for navigating web content, NVDA will activate the onClick event when the Enter key is pressed on an element.
 </li><li>
-When NVDA is in Applications Mode however, NVDA will activate the onKeyDown/onKeyPress/onKeyUp events instead, and not the onClick.
+When NVDA is in Applications Mode however, NVDA will activate the onKeyDown/onKeyUp events instead, and not the onClick.
 </li></ul>
 <p>
 When NVDA is in Browse Mode, it reads all offscreen content, even if other content is overlayed across it.