I agree. I have been using games since the early 80s. And it was always that arrow keys that controlled movement. I have no idea where the aswd thing came from, but I always have to remember to test that out to see if those are the controls. I normally go straight to the arrow keys.
Games that required you to keep one hand on the mouse at all times, like doom and quake, moved the movement keys to WASD because they’re arranged in the same shape as the arrow keys, (on a QWERTY keyboard,) but at the extreme left of the board.
That way you could use your left hand for the keys while operating the mouse in your left hand. It also puts a lot of other keys within easy reach, so now even games that don’t require a mouse sometimes use WASD for direction.
Unfortunately this is inconvenient for other keyboard layouts, but a majority of keyboards are QWERTY.
There are three things you can do about this:
Do nothing, this is easiest, since most people use a QWERTY board a majority of people will have no problems with your game.
Bind several different keys to the same function, this isn’t hard, and gives players a choice of keys to use.
You can let the player define their own key bindings. This is the hardest solution, but it is possible using Python. The GameKeys module defines constant values for all the keys, so you can store these values and compare the pressed keys to the stored values.