Skip to content

🎨 Palette: [UX improvement] Link Hotkey Inputs to Header #430

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
google-labs-jules wants to merge 2 commits into
base: main
Choose a base branch
from
Open

🎨 Palette: [UX improvement] Link Hotkey Inputs to Header #430

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4f168e4
Palette: Settings Hotkey accessibility improvement
google-labs-jules[bot] Jul 8, 2026
2890b08
Revert Hotkey LabeledBy changes and update memory instructions
google-labs-jules[bot] Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .jules/palette.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,6 @@
## 2026-05-15 - ProgressRing Visibility Binding
**Learning:** In WinUI 3, a `ProgressRing` automatically hides its visuals when `IsActive="False"`. It is not necessary to explicitly bind its `Visibility` property using a boolean-to-visibility converter unless the layout space it reserves needs to be reclaimed.
**Action:** When adding simple visual feedback using a `ProgressRing` alongside a button (e.g., in a `StackPanel`), simply bind the `IsActive` property to the async command's execution state without a redundant `Visibility` binding.
## 2026-05-18 - Input Field Accessibility Linkage
**Learning:** In WinUI 3 XAML settings or forms, input fields (like `ComboBox` or `TextBox`) that are grouped under a visual `TextBlock` header lack context for screen reader users navigating directly to the inputs.
**Action:** Explicitly link interactive controls to their visual headers to properly support screen readers. Assign an `x:Name` to the descriptive `TextBlock` and set `AutomationProperties.LabeledBy="{Binding ElementName=HeaderName}"` on the interactive control ONLY IF no per-field `AutomationProperties.Name` already exists for those controls.