Missing Keyboard Navigation Support

[kasya]

Some interactive elements rely solely on onClick handlers and do not provide corresponding keyboard event handlers (e.g., onKeyDown), making them inaccessible to keyboard-only users.

Keyboard-only users are unable to interact with these elements, violating WCAG 2.1 keyboard accessibility requirements.

Acceptance Criteria

• All clickable elements must support keyboard interaction.
• Use onKeyDown with Enter or Space key detection.
• Provide visible focus indicators.
• Ensure keyboard navigation follows a logical tab order.

Occurrences Found (8+)

• ModuleList.tsx
• ToggleableList.tsx
• Search.tsx
• SortBy.tsx
• ProgramActions.tsx
• Release.tsx
• Card.tsx
• ShowMoreButton.tsx

Are you going to work on implementing this?

• Yes
• No

[mirnumaan]

I would like to work on this issue too. Thank you !

@kasya

[Utkarsh-0304]

can I work on this @kasya

[ishanBahuguna]

@kasya i would like to work on this

[kasya]

@Utkarsh-0304 @ishanBahuguna Thanks for your interest guys! But this is a good first issue. We plan to leave these out for new contributors. Both of you had several meaningful contributions to the OWAS Nest before and I feel like both are capable of working on bigger tasks 👍🏼

So I'll keep this available for newcomers

[sameersharmadev]

Hey @kasya ! I'm a new contributor for owasp, and I would like to work on this :)

[Aditi1Sahu]

Can you assign this to me? @kasya