Developing a Keyboard Interface: Add clarifying word to explanation of selection following focus(pull #3404)

Minor editorial change to clarify explanation of why it is sometimes good for selection to not follow focus.

Original wording:
>if displaying a new panel causes a network request and possibly a page refresh, the effect of having selection automatically focus can be devastating to the experience for keyboard and screen reader users.

Ads the word "follow" for this new wording:
>However, if displaying a new panel causes a network request and possibly a page refresh, the effect of having selection automatically follow focus can be devastating to the experience for keyboard and screen reader users.

Author: dan-tripp-siteimprove

content/practices/keyboard-interface/keyboard-interface-practice.html

@@ -201,7 +201,7 @@ <h2>Deciding When to Make Selection Automatically Follow Focus</h2>
           And, a screen reader user who perceives the labels on tabs by navigating through them may efficiently read through the complete list without any latency.
         </p>
         <p>
-          However, if displaying a new panel causes a network request and possibly a page refresh, the effect of having selection automatically focus can be devastating to the experience for keyboard and screen reader users.
+          However, if displaying a new panel causes a network request and possibly a page refresh, the effect of having selection automatically follow focus can be devastating to the experience for keyboard and screen reader users.
           In this case, displaying the fourth tab or reading through the list becomes a tedious and time-consuming task as the user experiences significant latency with each movement of focus.
           Further, if displaying a new tab refreshes the page, then the user not only has to wait for the new page to load but also return focus to the tab list.
         </p>