🎨 Palette: 키보드 포커스 가시성 개선 (focus-visible)

[seonghobae]

💡 What (무엇을 변경했나요?)
HTML 보고서를 생성하는 python/fast_mlsirm/report.py 내부의 CSS 템플릿에서 <main>, .table-wrap, .export-block pre 요소에 할당되어 있던 범용 :focus { outline: none; } 스타일을 :focus:not(:focus-visible) { outline: none; }로 변경했습니다.

🎯 Why (왜 변경했나요?)
기존 방식(:focus { outline: none; })은 마우스 클릭 시 생기는 거슬리는 브라우저 기본 포커스 링을 없애주지만, 키보드(Tab 키 등)를 이용하여 페이지를 탐색하는 사용자들의 포커스 지표까지 완전히 지워버려 심각한 웹 접근성(a11y) 문제를 일으킵니다. 이를 해결하여 마우스 사용자의 시각적 경험을 유지하면서도 키보드 사용자에게 올바른 포커스 인디케이터를 제공하기 위함입니다.

📸 Before/After

• Before: .table-wrap (스크롤이 있는 테이블 컨테이너) 등을 키보드로 포커스할 때 아무런 시각적 피드백이 없어 사용자가 현재 위치를 알 수 없음.
• After: 마우스 클릭 시에는 포커스 링이 없지만, 키보드 포커스 진입 시에는 기본 윤곽선이 나타나며 :focus-visible 커스텀 스타일(테일 컬러 윤곽선)이 정상적으로 렌더링됨.

♿ Accessibility (접근성)

• 마우스 사용자의 방해요소를 줄이기 위한 의도로 추가된 CSS가 키보드 전용 사용자(Screen reader 사용자 포함)의 포커스 인지 능력을 박탈하던 문제를 수정했습니다. (이슈 기반: Palette's Journal: Focus Visible For Scrollable Tables)

---

PR created automatically by Jules for task 17371512451611161829 started by @seonghobae

---

[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.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7b7cee8e-c217-4b6a-ad78-1d62a9c474ce

📥 Commits

Reviewing files that changed from the base of the PR and between 04d0bc2 and 7fceaf5.

📒 Files selected for processing (2)

• python/fast_mlsirm/report.py
• tests/test_report.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[seonghobae]

Closing as a proven duplicate of the existing single-writer diagnostics-report accessibility lane in #1002. Fresh patch comparison shows this PR's entire production change (main, .table-wrap, and export <pre> from blanket :focus suppression to :focus:not(:focus-visible)) and its table regression are already present in #1002, which additionally covers disclosure <summary> focus and the report-title trust boundary. Keeping both open would create competing writers on the same report.py/focus contract. No source from #1256 needs separate integration.

[google-labs-jules]

Closing as a proven duplicate of the existing single-writer diagnostics-report accessibility lane in #1002. Fresh patch comparison shows this PR's entire production change (main, .table-wrap, and export <pre> from blanket :focus suppression to :focus:not(:focus-visible)) and its table regression are already present in #1002, which additionally covers disclosure <summary> focus and the report-title trust boundary. Keeping both open would create competing writers on the same report.py/focus contract. No source from #1256 needs separate integration.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.