test(frontend): preserve Toolkit tab ARIA state after filtering

[utksh1]

Summary

Add tests that filtering tools does not break the selected tab, aria-controls, or keyboard navigation.

Scope

• Suggested file: frontend/src/pages/Toolkit.tsx
• Add or extend a focused frontend unit test.
• Do not bundle unrelated visual or production changes.

Acceptance criteria

• The behavior is covered with a deterministic test.
• The user-visible or accessibility outcome is asserted.
• Existing tests remain stable.
• The focused frontend test passes.

Verification

Run the affected Vitest file from frontend/.

[taneesha-reyyi]

Hi @utksh1,

I'd like to work on this issue as part of GSSoC 2026.

Solution Approach:

• Review the existing Toolkit.tsx component and its frontend tests to understand the current filtering and tab selection behavior.
• Add or extend a focused Vitest unit test to verify that filtering the toolkit does not change the selected tab unexpectedly.
• Assert that the correct aria-selected, aria-controls, and related accessibility attributes are preserved after filtering.
• Verify that keyboard navigation (e.g., arrow keys and tab interactions) continues to work correctly after the filter is applied.
• Keep the changes limited to the required frontend test and run the affected Vitest file to ensure the new test is deterministic and all existing tests remain stable.

Could you please assign this issue to me? Thank you!

[mahek-builds]

/assign

[sripoojithareddykakumani]

/assign