obsproject / obsproject/obs-studio

Revision of the interface for configuring shortcut keys - Make it more accessible

Open
#5,597 1 comment 0 reactions 1 assignee 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 10

Other OS

No response

OBS Studio Version

27.1.3

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/pt-br

OBS Studio Crash Log URL

No response

Expected Behavior

Hi!
I open this issue to request a revision of the interface in the shortcut key settings part of the OBS, regarding the behavior when used with the screen reader.
It's quite complicated to interact with the screen reader to set hotkeys for available actions like scene change and start/stop recording/streaming.
We managed it somehow with NVDA's object navigation, but it often happens that we accidentally assign a key because we are using screen reader shortcuts, or we accidentally assign shortcuts to a wrong action.
It's really confusing this part for interacting with screen readers.
If you can fix this, I'll be grateful!

Current Behavior

Hi!
I open this issue to request a revision of the interface in the shortcut key settings part of the OBS, regarding the behavior when used with the screen reader.
It's quite complicated to interact with the screen reader to set hotkeys for available actions like scene change and start/stop recording/streaming.
We managed it somehow with NVDA's object navigation, but it often happens that we accidentally assign a key because we are using screen reader shortcuts, or we accidentally assign shortcuts to a wrong action.
It's really confusing this part for interacting with screen readers.
If you can fix this, I'll be grateful!

Steps to Reproduce

...

Anything else we should know?

No response

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.