NPSS Physics Runtime and Game Engine Editor: Accessibility Framework Integration
18.1K reputation · 03 Oct 2022, 21:03 UTC
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?