i am making a phone game, and i need opinions on my menu accessibility concept.
the game part of the phone game takes advantage of touch and swipe controls in a way that it can't just be ported to traditional controls:
if anyone wants to make a good version of the game for button or mouse controls, some heavy changes are needed — like a less extreme version of demaking a 3D console game as a 2D handheld game.
my accessibility concept is making custom menu Controls that intentionally work only with touch and not with keyboard
- to communicate instantly that the game will not work with button controls.
instead of being disappointed that the menu works with buttons but not the actual game, the player will already expect the game to not work with buttons because the menu also does not work with buttons
- to have more room to make the menu look visually great when using it with touch:
if the menu has to work with buttons i'd need to add visuals for hover and focus state — which looks and feels great for use with keyboard/controller, but unnecessary and heavy with touch. so making a button-incompatible menu gives me opportunity to improve presentation by not making these unnecessary visuals
¿is this a good menu accessibility concept for my phone game?
