🎨 Palette: [UX improvement] 악보 뷰 비활성화 버튼의 접근성 개선

[seonghobae]

💡 What: ScoreView.tsx 내에서 프로젝트가 없을 때 비활성화되는 악보 추가/열기/삭제 버튼들에 대해 네이티브 disabled 속성을 제거하고, 대신 aria-disabled="true" 및 title 속성을 추가했습니다. 또한 CSS를 수정하여 aria-disabled 상태에서도 시각적으로 비활성화된 것처럼 보이도록 처리하고, onClick 핸들러가 논리적으로 비활성화된 상태에서는 동작하지 않도록 조건을 추가했습니다.
🎯 Why: 네이티브 disabled 속성을 사용하면 버튼이 키보드 포커스를 받지 못하고 마우스 이벤트(호버 등)가 차단되어, 사용자가 왜 버튼이 비활성화되었는지 안내하는 시각적 툴팁을 볼 수 없으며 스크린 리더도 해당 정보를 읽지 못합니다. 이를 aria-disabled로 변경하여 모든 사용자가 버튼의 비활성화 이유("악보는 활성 분석 프로젝트에 첨부됩니다...")를 명확히 알 수 있게 접근성을 개선했습니다.
📸 Before/After: 프로젝트가 활성화되지 않은 상태에서 버튼들에 마우스를 올리면 툴팁이 나타나고 키보드 탭(Tab)으로 포커스하여 스크린 리더로 설명을 들을 수 있습니다. 버튼의 시각적 형태는 이전의 비활성화 상태와 동일하게 유지됩니다.
♿ Accessibility: 네이티브 disabled 속성을 aria-disabled="true"로 교체하여 키보드 접근성 및 스크린 리더 호환성을 높였고, 기본 브라우저 툴팁(title) 제공으로 인지성을 향상시켰습니다.

---

PR created automatically by Jules for task 10841403664922037094 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.

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head d88b825ef73ccdde4f1bf4e8c98412d8a29f7a8d.

• Head SHA: d88b825ef73ccdde4f1bf4e8c98412d8a29f7a8d

• Workflow run: 29764234964

• Workflow attempt: 1

Coverage evidence

Coverage Decision

• Result: FAIL
• Test evidence: not proven passing
• Docstring evidence: not proven passing when configured
• Failure count: 3

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: d88b825ef73ccdde4f1bf4e8c98412d8a29f7a8d
• Workflow run: 29764234964
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head d88b825ef73ccdde4f1bf4e8c98412d8a29f7a8d.

• Head SHA: d88b825ef73ccdde4f1bf4e8c98412d8a29f7a8d

• Workflow run: 29764234964

• Workflow attempt: 1

Coverage evidence

Coverage Decision

• Result: FAIL
• Test evidence: not proven passing
• Docstring evidence: not proven passing when configured
• Failure count: 3

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]

Loading

[seonghobae]

Closing as closed-obsolete (palette a11y micro-PR storm) by autonomous product-completion loop.

Winner / disposition target: #727

Unique value from this cluster is consolidated there (projectId path guard + npm HIGH CVE pins + Foote novelty kernel sign). Remaining micro-duplicates do not land additional commercial readiness.

[seonghobae]

closed-closed-obsolete (palette a11y micro-PR storm) → #727

[google-labs-jules]

Closing as closed-obsolete (palette a11y micro-PR storm) by autonomous product-completion loop.

Winner / disposition target: #727

Unique value from this cluster is consolidated there (projectId path guard + npm HIGH CVE pins + Foote novelty kernel sign). Remaining micro-duplicates do not land additional commercial readiness.

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

[google-labs-jules]

closed-closed-obsolete (palette a11y micro-PR storm) → #727

Acknowledged.