NPSS Physics Runtime and Game Engine Editor: Accessibility Framework Integration

Question

The NPSS physics runtime utilizes Qt widgets for its primary configuration UI, which supports native accessibility roles and screen-reader compatibility. However, when integrating NPSS parameters into a game engine editor, the current implementation relies on ImGui-based overlays for property panels.

Because ImGui does not natively provide the same accessibility roles or focus ordering as the Qt framework, there is a disconnect in the user-facing workflow. This creates an inconsistency for developers relying on assistive technologies when switching between the core NPSS configuration tool and the engine-integrated property panels.

There is an unresolved design decision regarding the best approach to unify this experience without compromising the performance of the editor overlay.

Should the editor-side property panels be migrated to the Qt accessibility framework to ensure parity?
  Alternatively, can the ImGui layer be augmented with custom annotations to expose consistent role and state information to assistive technologies?

Tasadduq Burney · Answer

Accessibility Gap Between NPSS Qt UI and ImGui Editor Overlays
The NPSS physics runtime provides a configuration UI built with Qt widgets, which natively supports accessibility roles, focus ordering, and screen-reader integration. When parameters are exposed inside a game engine editor, the implementation uses ImGui-based overlays. ImGui does not expose the same accessibility metadata, creating a disconnect for developers using assistive technologies.
Likely Explanation vs Confirmed Facts

Confirmed: Most game engines require explicit accessibility layers because physics engines (e.g., PhysX, Bullet) do not natively expose accessibility data.
  Likely: NPSS has a component-based architecture where accessibility can be added as a separate system without modifying the physics core.

Practical Steps for This Case

Identify the target platform(s) and whether the editor is native (Qt, WPF) or web-based. This determines the accessibility API (e.g., Microsoft UI Automation, macOS Accessibility, ARIA).
  If the editor remains ImGui-based, wrap each property control with an accessible name, role, and state using platform-specific annotations or a thin accessibility bridge layer.
  If migrating toward Qt parity, replace ImGui panels with Qt widgets for parameter editing, or use Qt's accessibility bridge to expose existing ImGui controls.
  Implement a central accessibility manager that queries the physics runtime for object metadata (position, velocity, mass) and exposes it via a standardized interface for assistive technologies.
  Provide keyboard traversal and high-contrast theme support across both UI toolkits.
  Test with NVDA or VoiceOver, verifying that all physics parameters are readable and editable via keyboard alone.

Missing diagnostic detail: Which platform(s) does the NPSS editor target, and is the game engine integration built on Unity, Unreal, or a custom solution? This changes whether the recommendation leans toward Qt migration, ImGui annotations, or a cross-platform abstraction layer.

NPSS Physics Runtime and Game Engine Editor: Accessibility Framework Integration

1 answer

Accessibility Gap Between NPSS Qt UI and ImGui Editor Overlays

Likely Explanation vs Confirmed Facts

Practical Steps for This Case

Your perspective belongs here.

1 question comment

Bridging ImGui and Qt for Consistent Accessibility