PixiJS Canvas and HTML ARIA Live Regions: Mapping Dynamic Scene Graph Changes

When building interactive visualizations with PixiJS, developers rely on the pixi-accessibility plugin to expose sprite roles and labels through ARIA attributes. The plugin works well for static sprites but does not automatically propagate changes in the scene graph—such as adding, removing, or updating containers—to ARIA live regions that screen readers rely on for dynamic content announcements. This leaves an unresolved decision: should PixiJS core (or its accessibility plugin) take responsibility for mapping scene‑graph mutations to live‑region updates, or should that mapping remain an explicit developer task?

Consider the trade‑offs of automatic live‑region integration versus manual invocation: performance overhead, version compatibility with PixiJS releases, and the complexity of handling nested containers versus flat sprite lists. The goal is to ensure that assistive‑technology users receive timely, accurate announcements without requiring developers to write repetitive ARIA‑update boilerplate.

• Should the accessibility plugin automatically generate and update ARIA live regions for any scene‑graph change?
• If automatic updates are not feasible, what minimal API should the plugin provide for developers to trigger live‑region announcements?
• How can version‑specific compatibility be maintained when PixiJS introduces new container types or rendering features?