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

[tamilr0727-ux]

Description

Adds accessibility-focused test coverage for app/api/og/route.tsx through the new test file app/api/og/route.accessibility.test.tsx.

Changes

• Added tests validating accessibility semantics within the generated Open Graph image markup.
• Verified accessible labels, descriptive associations, and semantic attributes are exposed correctly.
• Added coverage for focusable and interactive elements where applicable.
• Tested accessibility descriptions and screen-reader compatibility behaviors.
• Validated heading structure and logical content hierarchy within the rendered output.

Test Coverage

Implemented 5 test cases covering:

1. Accessible labels and semantic relationships (aria-label, aria-labelledby, aria-describedby, or equivalent attributes).
2. Focus management and visibility expectations for interactive elements.
3. Accessibility descriptions and tooltip announcement support.
4. Keyboard navigation flow and logical tab ordering.
5. Correct heading hierarchy and semantic document structure.

Validation

• All tests pass successfully with vitest run.
• Accessibility behaviors are verified through isolated unit and integration tests.
• No production code changes required.
• Improves confidence that generated Open Graph content maintains accessibility expectations and semantic consistency.

Fixes #4550

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

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 updated README.md if I added a new theme or URL parameter.
• 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.

[Aamod-Dev]

Thanks for the contribution. I went through the changes and the overall approach looks good.

[github-actions]

🎉 Congratulations @tamilr0727-ux! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨