fix(a11y): improve keyboard focus indicators and navigation

[Antra1705]

Description

Replaces the low-contrast :focus-visible box-shadow (12% opacity --accent-muted) with a prominent 2px offset ring using --accent and --bg CSS variables. Adds a high-contrast mode fallback, refactors NativeShareButton hardcoded blue colors to design system tokens, adds .thumb-btn:focus-visible styles to ThumbnailStrip, adds focus rings to DraggableTextOverlays, updates BaseButton with focus-visible:* Tailwind classes, and adds a KeyboardNavigation.test.tsx integration test covering Tab navigation and keyboard activation.

Related Issue

Closes #719

Type of Contribution

• Bug fix
• GSSoC contribution

Participant Info

• GitHub username: @Antra1705
• Contribution level: Advanced

Screen Recording

Screen.Recording.2026-07-14.at.10.04.45.PM.mp4

Checklist

• I have read the contribution guidelines
• My changes follow the project structure
• I have tested my changes in Chrome, Firefox, and Safari
• bun run lint passes (no ESLint errors)
• bunx tsc --noEmit passes (no TypeScript errors)
• New interactive elements have aria-label / accessible names
• No console.log statements left in
• This PR is related to a valid issue
• Screen recording attached above (required for UI/feature/design changes)

[vercel]

@Antra1705 is attempting to deploy a commit to the magic-peach1's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

✅ PR Format Check Passed — @Antra1705

Basic format checks passed. A maintainer will review your code changes.

This does not mean the PR is approved — it just means the format is correct.

[github-actions]

👋 Thanks for your PR, @Antra1705!

Welcome to Reframe — a browser-based video editor built for everyone 🎬

🟠 GSSoC'26 PR detected — thanks for contributing under GirlScript Summer of Code 2026!

What happens next

1. 🤖 Automated checks — build & TypeScript typecheck will run automatically
2. ✅ Vercel preview — a preview deployment will be created (requires maintainer authorization for fork PRs)
3. 👀 Code review — a maintainer will review your changes
4. 🚀 Merge — once approved, your PR will be merged!

Quick checklist

• PR title follows Conventional Commits (e.g. feat: add dark mode)
• Linked the issue this PR closes (e.g. Closes #123)
• Tested the changes locally (bun run dev)
• Build passes (bun run build)

Useful links

• 📖 CONTRIBUTING.md
• 🐛 Open Issues
• ⭐ Star the repo to support the project!

Happy coding! 🎉

[github-actions]

👋 This PR has been inactive for 21 days. It will be automatically closed in 14 days if there's no further activity.

If you need help with this PR, please comment or ping a maintainer.
Make sure your branch is rebased onto main and all CI checks pass.

[Antra1705]

@magic-peach Hi I have raised the pr but the label says need fixes can you please go through the code and tell if it's good to merge or not?