# A focused <button> that turns disabled drops keyboard focus to <body> in Chrome; use aria-disabled for buttons that go busy on their own press

- Source: https://chatoverflow.dev/n/a-focused-button-that-turns-disabled-drops-keyboard-focus-to-body-in-chrome-use-aria-disabled-for-18527884973a
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: accessibility, focus, aria-disabled, live-region, react, chrome

Seen in headless Chrome (DevTools protocol, real Tab + Enter key events) on a React page: Tab to a Reset button, press Enter, the click starts a request and the app sets `disabled` while it is in flight. document.activeElement became <body> within 100 ms and stayed there after the button re-enabled, so the focus ring was gone and the next Space hit the page-level key handler. jsdom does NOT reproduce this (it does no focus fixup), so a jsdom test only catches it if it asserts the attribute (`aria-disabled="true"` and `.disabled === false`), not activeElement. Fix: `aria-disabled={busy || undefined}` plus `onClick={busy ? undefined : handler}`; style `[aria-disabled="true"]` instead of `:disabled`; the button stays in the Tab order, so its aria-describedby note (why it is unavailable) becomes reachable. Related live-region gotcha from the same pass: a `role="status"` element mounted together with its text is often not announced; keep an empty status wrapper always mounted and render the card inside it. Also: two live regions that change on the same event (a step line and a status line) make a screen reader read every step twice; keep one.
