Add "activate element" user intent

index.bs

@@ -38,6 +38,12 @@ table tbody th:first-child { border-left: solid; }
 table td, table th { border-left: solid; border-right: solid; border-bottom: solid thin; vertical-align: top; padding: 0.2em; }
 </style>
 
+<pre class=anchors>
+spec: HTML; urlPrefix: https://html.spec.whatwg.org/multipage/
+    type: dfn
+        text: focused area of the document; url: document-sequences.html#focused-area-of-the-document
+</pre>
+
 Introduction {#intro}
 =====================
 
@@ -838,10 +844,18 @@ The following <dfn>table of standard user intents</dfn> enumerates the user inte
   <tr>
     <td>"`pressKeys`"
     <td>[=press keys=]
+  <tr>
+    <td>"`activateElement`"
+    <td>[=activate element=]
 </table>
 
 A [=remote end=] has a <dfn for="remote end">table of extension user intents</dfn>, which is a mapping of zero or more string names of user intents and algorithms for simulating the named intents. Extension user intents' names must contain a "`:`" (colon) character, denoting an implementation specific namespace.
 
+A [=remote end=] has a <dfn for="remote end">virtual cursor</dfn>, which describes the location of the user's focus.
+
+Note: The [=virtual cursor=] is not necessarily synchronized with any given
+applications' concept of "focus" (e.g. [=focused area of the document=]).
+
 <div algorithm>
 
 Note: Each string in `KeyCombination` represents a "raw key" consisting of a
@@ -869,6 +883,23 @@ To <dfn>press keys</dfn> given |command parameters|:
 
 </div>
 
+<div algorithm>
+
+Note: Remote ends which do not implement [=press keys=] might choose to
+implement other intents to facilitate navigation. Such implementations could
+possibly meet clients' needs for traversal and basic interaction, but they
+would be unable to facilitate the filling of form fields. For clients of such
+implementations who are targeting web applications, the following intent could
+be used in conjunction with the keyboard simulation faculties of [[WEBDRIVER]]
+or [[WEBDRIVER-BIDI]] in order to meet such needs.
+
+To <dfn>activate element</dfn> given <var ignore>command parameters</var>:
+
+1. Perform the default action for the item in the [=virtual cursor=].
+2. Return [=success=] with data null.
+
+</div>
+
 ### Definition ### {#module-interaction-definition}
 
 [=Remote end definition=]: