🎨 Palette: [UX improvement] Accessible Score Pagination Tooltips

[seonghobae]

💡 What: The UX enhancement added

Replaced native disabled attributes with aria-disabled="true" on the pagination controls (ScoreViewer.tsx), while properly intercepting clicks using e.preventDefault(). Added localized title attributes that explain why the buttons are disabled ("Already at the first page" and "Already at the last page").

🎯 Why: The user problem it solves

Native disabled attributes completely hide elements from screen readers and block all pointer/hover events. This causes a confusing experience for screen reader users (as the button disappears from focus rather than announcing its state) and prevents hover-based tooltips from appearing for sighted mouse users.

📸 Before/After

Before:
The Previous/Next page buttons used disabled={pageNumber <= 1}, preventing keyboard users from focusing them and preventing tooltips from rendering.

After:
The buttons use aria-disabled="true". A sighted mouse user who hovers over a disabled button now sees an informative tooltip ("Already at the first page"), and keyboard users can focus the element and hear its disabled state.

♿ Accessibility: Any a11y improvements made

Maintained full tooltip accessibility and keyboard focus support for visually impaired and mouse users by avoiding native disabled attributes.

---

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

Next included review available in 16 minutes.

Check out review usage here.

View limit details

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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: e3db3cb8-13b1-49e7-9cff-0d4c20d2c747

📥 Commits

Reviewing files that changed from the base of the PR and between 314ddea and dd72585.

📒 Files selected for processing (4)

• apps/desktop/src/features/score/ScoreViewer.test.tsx
• apps/desktop/src/features/score/ScoreViewer.tsx
• apps/desktop/src/locales/en/common.json
• apps/desktop/src/locales/ko/common.json

---

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

[seonghobae]

Complete-succession review: this PR changes only ScoreViewer pagination focusability/aria-disabled, reason-specific EN/KO copy, native title hints, and the corresponding existing test assertions. Canonical Score accessibility owner #731 already contains the same valid product delta and a stricter interaction contract: focusable aria-disabled Previous/Next controls with activation guards, the same first/last-page reasons exposed through aria-describedby + an authored role="tooltip", pointer hover and keyboard focus disclosure, Escape dismissal/re-entry behavior, hoverable tooltip content without an invisible hit target, enabled-control titles, and dedicated regressions/doctoring. #1200 adds no unique test, fixture, contract, localization, security, or buyer-visible behavior beyond that canonical lane. Its title-only unavailable explanation is intentionally not preferred because it is weaker for keyboard/touch disclosure. No checks/reviews/status from #1200 transfer to #731. Closing unmerged as fully succeeded by #731; reopen only if a concrete unique delta is identified.

[google-labs-jules]

Complete-succession review: this PR changes only ScoreViewer pagination focusability/aria-disabled, reason-specific EN/KO copy, native title hints, and the corresponding existing test assertions. Canonical Score accessibility owner #731 already contains the same valid product delta and a stricter interaction contract: focusable aria-disabled Previous/Next controls with activation guards, the same first/last-page reasons exposed through aria-describedby + an authored role="tooltip", pointer hover and keyboard focus disclosure, Escape dismissal/re-entry behavior, hoverable tooltip content without an invisible hit target, enabled-control titles, and dedicated regressions/doctoring. #1200 adds no unique test, fixture, contract, localization, security, or buyer-visible behavior beyond that canonical lane. Its title-only unavailable explanation is intentionally not preferred because it is weaker for keyboard/touch disclosure. No checks/reviews/status from #1200 transfer to #731. Closing unmerged as fully succeeded by #731; reopen only if a concrete unique delta is identified.

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