From ad30433a08d006a8cd56f8b48baed2360e744613 Mon Sep 17 00:00:00 2001 From: "google-labs-jules[bot]" <161369871+google-labs-jules[bot]@users.noreply.github.com> Date: Tue, 12 May 2026 13:28:57 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=8E=A8=20Palette:=20Add=20keyboard=20inst?= =?UTF-8?q?ructions=20and=20accessible=20score=20to=20Mario=20game?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Added visible text block detailing the Space and Up Arrow keys required to jump. - Added `aria-live="polite"` and `aria-atomic="true"` to the dynamic score counter. - Cleaned up broken dependency `venv` in requirements.txt. Co-authored-by: EiJackGH <172181576+EiJackGH@users.noreply.github.com> --- .Jules/palette.md | 8 ++++++++ requirements.txt | 1 - src/views/mario-game.njk | 15 ++++++++++++++- 3 files changed, 22 insertions(+), 2 deletions(-) diff --git a/.Jules/palette.md b/.Jules/palette.md index 8ee612f..c005e16 100644 --- a/.Jules/palette.md +++ b/.Jules/palette.md @@ -12,3 +12,11 @@ ## 2025-03-23 - Game Key Scrolling **Learning:** Browsers natively scroll the page when users press Space or Arrow keys. When building a web-based game, this creates a frustrating UX where the game viewport jumps around while playing. **Action:** Always call `e.preventDefault()` on keydown events for typical game controls ("Space", "ArrowUp", etc.) when the focus is on a game container or the body. + +## 2025-05-18 - Missing Screen Reader Feedback on Dynamic Scores +**Learning:** For dynamic real-time values like game scores that update frequently without page reloads, screen reader users miss out on crucial context if live regions are not used. Adding `aria-live` is critical. +**Action:** Always include `aria-live="polite"` and `aria-atomic="true"` on scoreboards, progress indicators, or dynamic text containers in custom UI or web games to ensure announcements are properly queued and read out. + +## 2025-05-18 - "Invisible" Controls in Custom Game UIs +**Learning:** Creating custom keyboard event listeners in web interfaces (like space to jump) is often totally undiscoverable to users without explicit onboarding text. +**Action:** Whenever binding custom navigation or game actions to keydown events, verify that instructional helper text is visibly rendered in the UI context so users know what inputs are expected. diff --git a/requirements.txt b/requirements.txt index cfaa995..4ad1501 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,4 +1,3 @@ numpy pandas requests -venv diff --git a/src/views/mario-game.njk b/src/views/mario-game.njk index 67b6bd7..d4d872a 100644 --- a/src/views/mario-game.njk +++ b/src/views/mario-game.njk @@ -52,13 +52,26 @@ font-size: 20px; font-family: Arial; } + + #instructions { + position: absolute; + top: 10px; + right: 10px; + color: rgba(255, 255, 255, 0.8); + font-size: 16px; + font-family: Arial, sans-serif; + background: rgba(0, 0, 0, 0.3); + padding: 5px 10px; + border-radius: 5px; + }
-
Score: 0
+
Score: 0
+