Kernel connection failure in the IPython Console component leaves assistive technology status unannounced

Spyder's IPython Console relies on a persistent IPython kernel process. When the kernel crashes or the socket connection is lost, the console becomes non-interactive and execution controls are disabled. Today this transition is conveyed primarily through visual cues in the console and status bar, creating an unresolved decision about how the same state should reach screen reader and keyboard-only users.

The open question is whether Spyder should map kernel connection state to native accessible objects and live-region announcements, or instead expose a separate simplified accessible status view. Because custom panes and shortcuts change across major Spyder releases, and Qt accessibility behavior varies by platform and version, any solution must account for environment-specific differences.

What is the intended accessibility contract for kernel disconnection in the IPython Console? Should the disabled execution controls and non-interactive console state be announced automatically, or surfaced only through a dedicated accessible status pane? What validation approach works across supported Qt versions without relying on visual inspection?