Conversation

Notices

1. Embed this notice
   13 barn owls in a trenchcoat (hauntedowlbear@eldritch.cafe)'s status on Thursday, 28-Dec-2023 01:36:18 JST 13 barn owls in a trenchcoat

   I'm not here to dunk on specific tutorial writers, as the piece about PyGame that I found this in is both pretty old and generally okay at its job, but offering a choice between WASD and arrow keys really isn't what I'd consider to be an example of accessibility.

   Further, the way they defined WASD in the code examples that follow would make their directional control schema entirely useless on non-QWERTY keyboards.

   Like, absolutely, yes, encourage new developers to consider that not everyone's configuration is the same as their own.

   But this kind of feels like the concept of accessibility is being missold here.

   • Embed this notice
     13 barn owls in a trenchcoat (hauntedowlbear@eldritch.cafe)'s status on Thursday, 28-Dec-2023 01:55:39 JST 13 barn owls in a trenchcoat

     in reply to

     • lawless polymorph

     @typeswitch Yeah, I've found precious few that work on AZERTY.

     I was delighted when Godot introduced physical key mapping, because it's been a problem plaguing game control mapping for a long time.

   • Embed this notice
     lawless polymorph (typeswitch@gamedev.lgbt)'s status on Thursday, 28-Dec-2023 01:55:41 JST lawless polymorph

     in reply to

     @HauntedOwlbear speaking of things not working properly on non-QWERTY keyboards ... I've found exactly one game, in all these years, that is aware of non-QWERTY keyboards, to the point of changing the displayed letters for keyboard shortcuts in help/tutorial screens (it was factorio).