PixiJS Rendering Pipeline and @pixi-accessibility/core Plugin: Pointer Event vs Assistive‑Tech Gesture Handling

The goal is to define a consistent interaction model when using PixiJS together with the @pixi-accessibility/core plugin so that pointer events (click/touch) and assistive‑tech gestures are handled uniformly across keyboard navigation, screen‑reader announcements, and touch input.

Currently the plugin provides ARIA roles, labels, tabindex and a focus proxy for Sprites, but it does not automatically intercept raw PixiJS pointer events. Developers must decide whether to forward those events through the plugin’s accessibility layer or let PixiJS process them directly, which leads to inconsistent behavior where a Sprite may receive focus via keyboard yet ignore touch, or vice‑versa.

This unresolved decision leaves developers without a default behavior, requiring them to weigh performance overhead, synchronization complexity, and the risk of mismatched assistive‑tech feedback.

Should the plugin automatically intercept pointer events to forward them to the accessibility layer? Should a configuration flag enable developers to choose between raw PixiJS handling and accessibility‑mediated handling? What are the performance implications of each approach on low‑end devices?