From 62b38f75164744c9310af8d595b007c58095dc07 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Wed, 15 Jul 2026 22:19:36 +0000
Subject: [PATCH 1/2] =?UTF-8?q?=F0=9F=8E=A8=20Palette:=20[UX=20improvement?=
 =?UTF-8?q?]=20Screen=20Reader=20Friendly=20Navigation=20Hints?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

💡 What: Replaced symbolic navigation arrows and enter characters (`↑↓`, `⏎`) with readable text (`Up/Down`, `Enter`).
🎯 Why: Screen readers in CLI environments rely on raw text output and fail to announce symbolic characters properly.
📸 Before/After: Not applicable.
♿ Accessibility: Ensures that keyboard navigation hints are correctly announced by screen readers.
---
 .jules/palette.md                               | 3 +++
 src/cli/ui/components/CommandSuggestionList.tsx | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)
 create mode 100644 .jules/palette.md

diff --git a/.jules/palette.md b/.jules/palette.md
new file mode 100644
index 00000000..dde2e50e
--- /dev/null
+++ b/.jules/palette.md
@@ -0,0 +1,3 @@
+## 2024-07-16 - Screen Reader Friendly Navigation Hints
+**Learning:** For complex command-line selection interfaces or overlays using Ink, purely symbolic text (e.g., `↑↓`, `⏎`) fails to be announced properly by screen readers in CLI environments, causing an accessibility regression.
+**Action:** Use visually concise but screen-reader-friendly text (like 'Up/Down', 'Enter') instead of symbols to ensure proper accessibility in CLI navigation hints.
diff --git a/src/cli/ui/components/CommandSuggestionList.tsx b/src/cli/ui/components/CommandSuggestionList.tsx
index 7e66838a..d51fe548 100644
--- a/src/cli/ui/components/CommandSuggestionList.tsx
+++ b/src/cli/ui/components/CommandSuggestionList.tsx
@@ -116,7 +116,7 @@ export const CommandSuggestionList: React.FC<CommandSuggestionListProps> = ({
         </Box>
         <Box>
           <Text color={COLORS.text.muted} dimColor>
-            ↑↓ nav · ⏎ select · esc close
+            Up/Down nav · Enter select · Esc close
           </Text>
         </Box>
       </Box>

From 8eb3bdaac857f4abd17f7bfc8f6b77ad0b04149a Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Wed, 15 Jul 2026 22:25:38 +0000
Subject: [PATCH 2/2] =?UTF-8?q?=F0=9F=8E=A8=20Palette:=20[UX=20improvement?=
 =?UTF-8?q?]=20Screen=20Reader=20Friendly=20Navigation=20Hints?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

💡 What: Replaced symbolic navigation arrows and enter characters (`↑↓`, `⏎`) with readable text (`Up/Down`, `Enter`).
🎯 Why: Screen readers in CLI environments rely on raw text output and fail to announce symbolic characters properly.
📸 Before/After: Not applicable.
♿ Accessibility: Ensures that keyboard navigation hints are correctly announced by screen readers.
---
 tests/integration/prompt_templates.test.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/integration/prompt_templates.test.ts b/tests/integration/prompt_templates.test.ts
index 21905259..f1360d78 100644
--- a/tests/integration/prompt_templates.test.ts
+++ b/tests/integration/prompt_templates.test.ts
@@ -36,7 +36,9 @@ describe('Prompt templates', () => {
 
     expect(planSystem).toContain('You are SalmonLoop.');
     expect(patchSystem).toContain('You are PATCH, a phase-native diff compiler.');
-    expect(autopilotSystem).toContain('You are a senior software engineer running in "autopilot" mode.');
+    expect(autopilotSystem).toContain(
+      'You are a senior software engineer running in "autopilot" mode.',
+    );
     expect(answerSystem).toContain('You are a coding assistant in "answer" mode.');
     expect(researchSystem).toContain('You are a research assistant.');
   });