My son (9 yrs old) used plain JavaScript to make a game, and wants your feedback

I don't know if it's just me (checked in Firefox and Chrome), but the black text on the red buttons is really hard to read. I'd suggest using white, unless you had some reason to use black.

this is brilliant.

most of the feedback i'd want to give has already been given though... e.g. the attack charging confused me a bit until i worked it out by inference.

the animations are probably the highlight of this for me. they add some character nicely. adding more elements to show the attacks in progress beyond the colour changes would be a nice way to improve this.

i would suggest removing 0 from the rng for the math problems. occasionally you can get 0 + number which feels like a cheat almost. also maybe forcing the numbers to always be in double digits for the addition problems? he seems to be aware how to do this from looking at how the divide by zero is avoided.

another small thing would be to disable new input whilst the attack sequence is running... although again others have mentioned that.

----

overall this is impressive and interesting to see. i taught myself to write code starting when i was 8 using qbasic and its help file, then starting with visual basic when i was 11 and C when i was 12 - it was a different time, and different tools with different challenges, but i think any early start is helpful, especially if you have to work things out for yourself.

this game reminds me of some of my own early efforts, although rather than wrangling the complexity of a modern browser environment and language, i was wrangling with the lack of documentation and learning materials for logic, maths and graphics.

today i am the technical director of a games company with a cv littered with AAA, mobile and VR games. if your son eventually decides to choose this sort of career, i expect this kind of early work will pay huge dividends.

good work.

> Using the Orca screen reader, the game is almost completely playable.

Interesting! I tried to guide him towards the simple approach - eg: alert() is way simpler than making some sort of modal with HTML/CSS, etc. But now that I think about, that approach (i.e. just use what the browser provides) also results in a more accessible result.

I appreciate the detailed feedback here. This is awesome! I'm going to leverage this to have a discussion about accessibility with my son. It's something we haven't taken active consideration for through this process.

This is awesome, and the graphics remind me of my mspaint.exe graphics I used to load into Game Maker 4.0 in 2001 to make games as an 11 year old :)

It gave me a lifelong obsession with programming, and I'm still a principal engineer today

Let me know her feedback :)