Repository navigation
Conversation
The composer's reasoning-variant picker was announced as "Variant: Default". Rename its accessible name, tooltip/drawer title and the cycle command's palette entry to "Power" so screen readers announce "Power: Default". Closes #13 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Closes #13
Type of change
What does this PR do?
The composer's model-variant picker announced itself as "Variant: Default". This renames it to "Power" so screen readers say "Power: Default".
The button's visible text is just the selected value (for example "Default"), so only the copy around it changes. The keys and the menu behavior stay the same:
Variant: {{variant}}→Power: {{variant}}(ui.promptInput.variantCurrent)Choose model variant→Choose power(ui.promptInput.chooseVariant)Cycle model variant/Switch to the next model variant→Cycle power/Switch to the next power levelOnly English changed. Following
packages/app/AGENTS.md, the other locales keep their existing translations until a language review. The timeline notice "Switched variant to …" and the TUI aren't part of this issue, so they're unchanged.The screen reader decides whether it says "menu button" or "button menu". The app sets
aria-haspopupon the trigger, and this PR doesn't change that.How did you verify your code works?
bun typecheckpasses inpackages/uiandpackages/app, and the full repobun run typecheckpasses (35/35).main.toHaveAccessibleName("Power: Default")and("Power: High")to the existing keyboard test. That test also covers Tab, Enter, End and Escape. I confirmed the new assertion fails on the old string (Received: "Variant: Default").--no-verifybecause the pre-pushbun run checkfails onmain.script/check-greys.tsreports 172 greys, all inservices/site, which this PR doesn't touch.Screenshots / recordings
There's no visual change. The visible text is still the selected value.
Checklist
🤖 Generated with Claude Code