domain-ui-input-accessibility

Plan UI interaction layers, input mapping, and accessibility constraints for Godot Engine projects.

2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/DubDev720/gdref --skill domain-ui-input-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-ui-input-accessibility
Source: https://github.com/DubDev720/gdref/tree/main/godot-skills/godot-secondary/domain-ui-input-accessibility
Command: npx skills add https://github.com/DubDev720/gdref --skill domain-ui-input-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexities of designing user interfaces that are intuitive, accessible to all users, and adaptable to different languages and regions.

Core Features & Use Cases

  • Input Abstraction: Ensures input handling is device-agnostic and action-based.
  • Accessibility Design: Integrates accessibility requirements into the UI flow from the start.
  • Localization Strategy: Plans for text expansion and layout adjustments for internationalization.
  • Use Case: When designing a game's main menu, this Skill helps ensure that navigation works seamlessly with both a keyboard and a gamepad, and that text elements can accommodate different languages without breaking the layout.

Quick Start

Define the input actions and accessibility considerations for the game's main menu.

Frequently Asked Questions about domain-ui-input-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design accessible UI navigation for both keyboard and gamepad in Godot?

Accessible UI navigation for keyboard and gamepad in Godot is designed by abstracting input handling to be device-agnostic and action-based. This Skill helps plan interaction layers and control schemes that ensure menu navigation works seamlessly across multiple input devices.

What is the best way to plan UI localization for text expansion in Godot projects?

UI localization planning in Godot projects involves defining constraints for text expansion and layout adjustments early in the design phase. This Skill provides strategies to accommodate different languages and regions without breaking your interface layout.

How do I integrate accessibility requirements into Godot UI flows?

Accessibility requirements integrate into Godot UI flows by defining constraints during the interaction design phase rather than retrofitting them later. This Skill routes accessibility planning directly into your user interface architecture and menu behavior.

Does this Skill handle input mapping and control scheme planning for Godot Engine games?

Yes, input mapping and control scheme planning for Godot Engine games is a core function. It defines secondary domain skills for interaction patterns and routes them to concrete input system contracts for implementation.

When do I need to define accessibility and localization constraints for UI design?

You need to define accessibility and localization constraints for UI design when initially planning user interaction layers and menu navigation behavior. This ensures internationalization and device-agnostic input are built into the architecture from the start.

Can I use this Skill to plan menu and navigation behavior for multi-device input?

Yes, you can use this Skill to plan menu and navigation behavior for multi-device input scenarios. It focuses on defining interaction patterns that work seamlessly whether the user is navigating with a keyboard or a gamepad.