At the moment, it is very easy to just skip past your score screen on game over and even into another game. A way I suggest combating this is first of all to end the game and fade the sounds out, leaving only the music when you reach your score screen. This will make it easier to hear the score, since if you died, it's more than likely because you were in the midst of a bunch of asteroids, and you still hear them and they're quite loud.

Secondly, a short enforced period of transition between the game over screen and the main menu. That is, when you press OK on the game over screen, A second or two goes by, maybe even with a whoosh or transitional sound, and then you're dropped back onto the menu.

Thanks, I’ll consider these for the next update. Good suggestions here.

I’ll admit that the discoverability of this is crappy as you’re not the first to voice it, but all dialogs including the game-over dialog are tabbable. I.e., unlike with most screen readers, you can tab between the message and the OK button. So to hear your score, just press Tab after the OK button presents and you’re back on the message. This is one of those weird ways that godot-accessibility breaks with convention. I didn’t want to build a full object review system, so I just made lots of things focusable, including field labels. I take your and others’ point that this isn’t obvious, though, and welcome ways that it might be made more so. Part of the issue with Onslaught is that I’m not just building a game, but also a system that makes the underlying engine accessible. So if you have thoughts on how to make it more approachable, I’m happy to hear them. But I can probably improve the game-over experience, so I’ll focus on that for next week.