🎨 Palette: [UX improvement] Add focus visible styles to interactive elements

[dieterolson]

💡 What: Added focus-visible styling (focus-visible:ring-2 focus-visible:ring-blue-500) to inputs, selects, and textareas that previously only had focus:outline-none.
🎯 Why: Keyboard users need clear visual indicators of which element has focus. Without a focus ring, users navigating via keyboard cannot see where they are on the page.
📸 Before/After: Replaced focus:outline-none with standard focus-visible:ring-2 focus-visible:ring-blue-500.
♿ Accessibility: Restores visible focus rings for keyboard navigation to improve WCAG compliance (Focus Visible).

---

PR created automatically by Jules for task 8102073924590629122 started by @dieterolson

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[github-actions]

⚠️ SPEC.md Update Required

Source files were modified in this PR but SPEC.md was not updated.

Per the Specification-Driven Development Policy:

• Any PR that adds, removes, or changes functionality must update SPEC.md
• Update the relevant sections (features, architecture, tests, dependencies, etc.)
• Bump the Spec Version if making substantive changes

To resolve:

1. Update SPEC.md to reflect your changes, OR
2. Add the spec-exempt label if this PR genuinely doesn't affect the spec (e.g., pure refactor with no behavior change)

This check is enforced by the spec-check CI workflow.

[github-actions]

Performance Benchmark Results

No benchmark results available.

[dieterolson]

Consolidated into comprehensive PR #4429.