Zugängliche Unity-Spieloberflächen

Gameplay UI and Accessible Controls

Inspect the project's uGUI/UI Toolkit stack, input modules, event system, target devices and localization. Keep its established framework; choose a different one only for a concrete unmet requirement.

• Bind HUD presentation to authoritative gameplay state. Subscribe/unsubscribe with screen lifetime and update only changed values; do not make health, inventory or cooldown rules depend on a visual widget.
• Define focus ownership across mouse, keyboard and controller. Set a useful first selection, prevent navigation into hidden/disabled controls and restore focus after closing dialogs or nested menus.
• Coordinate action maps and pointer/cursor state with pause and menus. Prevent gameplay firing behind a modal, and keep Cancel/Pause reachable even when rebinding or a device disconnects.
• Verify reference scaling, anchors/layout rules and safe areas at intended aspect ratios. Test long localized text, missing glyph fallback and text size changes without hiding critical controls.
• Communicate essential state through more than color alone; pair audio cues with appropriate visual feedback. Offer relevant motion, subtitle and remapping controls without claiming compliance from a static screenshot.
• Profile frequent HUD changes separately from static content. With uGUI, investigate Canvas rebuilds and layout churn; with UI Toolkit, inspect the installed runtime's supported profiling tools.

Verify a complete controller-only menu path, pause/resume, dialog focus return, device switching, resolution/safe-area changes and representative localized strings. Check HUD values against actual game state.

Reference: Unity UI systems. The source's sample tooling is not a dependency of this skill.