test(TopRivalriesTicker-accessibility): verify Accessibility Standards & Screen Reader Aria Compliance

[Thacker-Meet]

Description

Fixes # (issue number)

Pillar## Description

Fixes #4597

Adds a dedicated accessibility test suite for TopRivalriesTicker covering screen-reader visibility, content accessibility, keyboard navigation behavior, and structural accessibility verification.

The test suite validates:

• Rivalry content remains accessible to assistive technologies.
• Rivalry labels and VS indicators are rendered and readable.
• Logical content structure is preserved for rivalry information.
• Keyboard tab navigation behaves consistently without introducing unintended focusable elements.
• Decorative icon rendering does not create accessibility regressions.

All tests are isolated, pass successfully with Vitest, and verify accessibility behavior based on the component's actual implementation.

Pillar

• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

• N/A (test-only changes)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have started the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	3433.75 KB	3433.75 KB	0 B
Total CSS	258.05 KB	258.05 KB	0 B

[Aamod007]

Thanks for the accessibility coverage for TopRivalriesTicker. I reviewed the PR description, linked issue #4597, checks, and the actual diff before labeling.

Labels applied:

• level:beginner: the change is a single 97-line test file, components/TopRivalriesTicker.accessibility.test.tsx, with five focused accessibility assertions in lines 40-96.
• quality:clean: the mocks are scoped to the test file, the cases are short, and the assertions stay close to the real accessible content and interaction model.
• type:testing: the PR adds accessibility-oriented Vitest coverage for TopRivalriesTicker, matching the issue.
• type:accessibility: the suite directly checks screen-reader text, keyboard tab behavior, and decorative SVG exposure.

All required checks are green and the PR is not draft or blocked, so I’m approving and adding gssoc:approved.