Skip to content

feat: Add keyboard navigation (tab-index mapping) for the Voice Tuning sliders.Β #759

Description

πŸš€ Program

GSSoC

✨ Feature Description

Improve the accessibility of the Voice Tuning panel by explicitly mapping the tabindex and adding onKeyDown handlers so users can adjust the speed and pitch sliders using the arrow keys.

πŸ€” Problem It Solves

Users with motor disabilities who rely on keyboard navigation currently cannot precisely click and drag the HTML range sliders, rendering the tuning features completely inaccessible to them.

πŸ’‘ Proposed Solution

Ensure the <input type="range"> elements are focusable via the Tab key. Implement an event listener so that when focused, pressing Left/Right arrows increments or decrements the value by a predefined step size.

πŸ”„ Alternatives Considered

No alternatives considered, as keyboard accessibility is a mandatory requirement for assistive technologies.

πŸ“Έ Mockups / Examples

When a user hits the Tab key, a clear visual focus ring should appear around the active slider handle.

βœ… Acceptance Criteria

  • Sliders can be reached via the Tab key.
  • Arrow keys successfully adjust the values up and down.
  • The UI visually indicates which slider currently has keyboard focus.

πŸ“‹ Additional Context

Review the WAI-ARIA authoring practices for slider components to ensure full compliance.

🌱 Contributor Checklist

  • I am participating via GSSoC
  • I have read the contribution guidelines
  • I checked for existing issues before creating this

Metadata

Metadata

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions