CKTIS / HTML
aria-busy — an update is not yet complete
`aria-busy="true"` tells assistive technologies that a region’s changes are incomplete and may be presented later.
Version: WAI-ARIA 1.2
Syntax
<div aria-live="polite" aria-busy="true">Updating…</div>Set string true before a series of changes and false after completion. The default is false. A screen reader may defer exposing changes and treat the completed update as one unit. This is not a guarantee of exact speech timing.
The attribute does not block clicks, disable buttons, start fetching, or draw a progress indicator. Those require application logic and visible feedback. Do not leave a region busy after failure; in asynchronous code restore the state in finally and present the error to the user.
The example records false → true → false while updating a count. The button stays enabled, showing ARIA’s boundary. When rebuilding a widget that temporarily loses required owned elements, the busy state can mark that intermediate period.
Examples
<!doctype html><meta charset="utf-8">
<div id="status" aria-live="polite" aria-busy="false"><span>0</span> items</div>
<button id="control">Available action</button><output id="result"></output>
<script>
const status = document.querySelector('#status');
const states = [status.getAttribute('aria-busy')];
status.setAttribute('aria-busy', 'true');
states.push(status.getAttribute('aria-busy'));
try {
status.querySelector('span').textContent = '3';
} finally {
status.setAttribute('aria-busy', 'false');
states.push(status.getAttribute('aria-busy'));
}
document.querySelector('#result').textContent =
states.join(' -> ') + '; region=' + status.textContent +
'; buttonDisabled=' + document.querySelector('button').disabled;
</script>Result
false -> true -> false; region=3 items; buttonDisabled=false
The test checks state ordering, final contents, and no automatic button disabling. It does not measure a screen reader’s speech queue.