Guidelines
Describe the bug
First of all, thank you for developing FreeTube; it runs surprisingly well for an Electron app with a screen reader. However, I encountered a couple of specific accessibility issues regarding button labels and player navigation.
Note for developers who may not be familiar with screen readers: A screen reader is an assistive technology used by blind and visually impaired users to read interface elements aloud. Anyone can test this on Windows by pressing Win + Ctrl + Enter to turn on the built-in Windows Narrator, or by using third-party tools like NVDA. When navigating using the Tab key, focus lands on interactive elements so they can be read aloud.
Here are the issues found while navigating with the Tab key:
- Unlabeled button after search input: The interactive button located right after the search input field lacks an accessible label (
aria-label or title), making it completely silent or announced only as "Button" without any context.
- Incorrect/Single-letter label for the Account menu button: The button that opens the account menu is announced only as "t" by screen readers instead of a descriptive name like "Account Menu".
Feature Request / Improvement:
- Video Player Structure: Currently, navigating the video player controls can be cumbersome. It would greatly improve accessibility if the video player could be structured as an embedded object or landmark (similar to standard YouTube embeds). This would allow screen reader users to easily jump to and control the player using quick-navigation shortcuts.
Steps to Reproduce:
- Enable a screen reader (such as Windows Narrator or NVDA) on Windows 10.
- Open FreeTube and press the
Tab key to navigate through the interface.
- Notice the unlabeled button right after the search bar, and check how the account menu button is announced as "t".
Expected Behavior
All interactive buttons should have proper accessible labels (such as aria-label) so screen reader users can identify them correctly. Also, the video player should be structured accessibly to make quick navigation easier.
Issue Labels
accessibility issue
FreeTube Version
0.25.2-beta
Operating System Version
Windows 10
Installation Method
Portable
Primary API used
Local API
Last Known Working FreeTube Version (If Any)
No response
Upload screenshots or videos
No response
Additional Information
Screen Reader used: NVDA (2026.1) / Windows Narrator
Nightly Build
Guidelines
Describe the bug
First of all, thank you for developing FreeTube; it runs surprisingly well for an Electron app with a screen reader. However, I encountered a couple of specific accessibility issues regarding button labels and player navigation.
Note for developers who may not be familiar with screen readers: A screen reader is an assistive technology used by blind and visually impaired users to read interface elements aloud. Anyone can test this on Windows by pressing
Win + Ctrl + Enterto turn on the built-in Windows Narrator, or by using third-party tools like NVDA. When navigating using theTabkey, focus lands on interactive elements so they can be read aloud.Here are the issues found while navigating with the
Tabkey:aria-labelortitle), making it completely silent or announced only as "Button" without any context.Feature Request / Improvement:
Steps to Reproduce:
Tabkey to navigate through the interface.Expected Behavior
All interactive buttons should have proper accessible labels (such as aria-label) so screen reader users can identify them correctly. Also, the video player should be structured accessibly to make quick navigation easier.
Issue Labels
accessibility issue
FreeTube Version
0.25.2-beta
Operating System Version
Windows 10
Installation Method
Portable
Primary API used
Local API
Last Known Working FreeTube Version (If Any)
No response
Upload screenshots or videos
No response
Additional Information
Screen Reader used: NVDA (2026.1) / Windows Narrator
Nightly Build