Prevent "pile up" of object responses when moving a vector.

[pixelzoom]

In phetsims/qa#1373 (comment), @KatieWoe reported:

In Vector Addition, with Jaws, when moving a vector the screen reader reads out every point along the path, not just the one you landed on. You can interrupt it by moving something after its started. This doesn't seem to happen when moving the tip or the graph, just the whole vector.

IMG_5993.MOV

[pixelzoom]

In phetsims/qa#1373 (comment), @Nancy-Salpepi reported:

I am seeing the same issue as @KatieWoe with Vector Addition. The behavior is different from 1.2.1, which wasn't sounding great either. VO was picking and choosing when it would give values when moving the vector. Most of the time it wasn't saying anything. I can't remember what it sounded like back then vs. now and have updated my computer since.

VA.mp4

---

In phetsims/qa#1373 (comment), @vperezcadavid99 reported:

I confirmed this issue too for vector addition with NVDA.
Even when interacting with other elements of the simulation, deleting, or changing screens, the description continues.

20260318_171942.mp4

[pixelzoom]

In phetsims/qa#1373 (comment), I responded:

In Vector Addition, with Jaws, when moving a vector the screen reader reads out every point along the path, not just the one you landed on. ...

I don't think this behavior change in Vector Addition is due to the aria-live change. It's due to the change that made queuing default to interruptable: false. I looks like @jessegreenberg attempted to correct for this for the vector tip by adding interruptable: true to VectorTipNode.doAccessibleResponse in 315205e. But it also needs to be corrected when dragging the entire vector in VectorNode.doAccessibleObjectResponse. Adding alertDelay: 1000 to both VectorNode and VectorTipNode, as we did for movables in Calculus Grapher, would also improve the experience by preventing a "pile up" of responses when using the arrow keys.

[pixelzoom]

Fixed in 98f048f. @KatieWoe please have a look, verify that this addresses the problem -- with JAWS, NVDA, and VoiceOver. Then assign back to me.

[KatieWoe]

Looks good for Jaws, NVDA, and VO

[pixelzoom]

Thanks @KatieWoe. This is not something that requires an MR. So I'll change the label to "fixed-awaiting-deploy" so that those involved in the next release will be aware of it, and can decide whether to include it in testing.