obsproject / obsproject/obs-studio

Screen readers fail to report the items in the list of added audio/video filters

Open
#11,400 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/accessibility
Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

30.2.3

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/niO15nP3SIxPJp7D

OBS Studio Crash Log URL

No response

Expected Behavior

The screen reader should report the filter's name or if it is enabled/disabled.

Current Behavior

The screen reader does not report the filter's name or if it is enabled/disabled.

Steps to Reproduce
  1. Launch a screen reader like NVDA or Narrator.
  2. Launch OBS Studio.
  3. Create a scene and add at least one source to it.
  4. From the context menu for the added source, select "Filters".
  5. In the "Filters" dialog/window, add a few filters.
  6. Move the focus to the list of filters and use up/down arrow to move between the filters in the list.
Anything else we should know?

This is an accessibility bug with OBS Studio. Screen readers like NVDA and Narrator fail to read the items in the list of added audio/video filters. The focus is in the list, pressing up/down arrow moves between the added filters, but screen readers do not read the name of the selected filter and if it is enabled or disabled.

Can the problem be fixed? The problem was partially fixed some time ago for the "Sources" list in the main OBS Studio window. I say "partially", because screen readers now report the name of each source, but not if it is enabled or not (but the last one should go into another report, probably).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in OBS Studio's Filters dialog with NVDA or Narrator, following the listed steps and checking the added audio/video filter list. Trace the Filters dialog and its list implementation, then verify that moving through filters announces each name and whether it is enabled or disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
accessibility, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.