Replies: 2 comments
-
|
Hi Bert, Unfortunately, IPlug2 doesn't currently support screen readers with the default GUI, But if you disabled the GUI, I think that the screen reader will work well with Reaper's native Win32 sliders. The IPlugConvoEngine example has no GUI. https://github.com/iPlug2/iPlug2/tree/master/Examples/IPlugConvoEngine I'm working on iPlug3, for which I am thinking about accessibility from the start. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Oli. Lovely to hear accessibility will be in there for v3.
For a workaround, for my first ever plugin, I implemented a key handler on the main window and replicated tab/shift-tab movement around some knob controls I’ve placed on the plugin. I also made use of tolk.dll, which is a library that allows me to call a Speak(“”) call which comes out from the screen reader (I’m using NVDA) to speak values after processing a cursor up or cursor down key press and updating the param value.
Pleasantly, I can also capture the enter key where I make the edit value edit box appear and this works without further effort with NVDA.
I’ve probably got to write a key handler for each type of control but I don’t think this is actually too arduous.
Although I’m a C++ coder, I don’t know anything about how to make an application screen reader friendly from the ground up.
But happy to help if I can e.g. Testing or discussing usability.
Best, Chris
From: Oli Larkin ***@***.***>
Sent: 27 February 2026 22:32
To: iPlug2/iPlug2 ***@***.***>
Cc: Chessel85 ***@***.***>; Author ***@***.***>
Subject: Re: [iPlug2/iPlug2] Enabling keyboard access to controls for screen reader users (Discussion #1332)
Hi Bert,
Unfortunately, IPlug2 doesn't currently support screen readers with the default GUI, But if you disabled the GUI, I think that the screen reader will work well with Reaper's native Win32 sliders. The IPlugConvoEngine example has no GUI. https://github.com/iPlug2/iPlug2/tree/master/Examples/IPlugConvoEngine
I'm working on iPlug3, for which I am thinking about accessibility from the start.
—
Reply to this email directly, view it on GitHub <#1332 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQOFDPWJURNGIER4ULB5YKT4ODAXTAVCNFSM6AAAAACV6SB4XGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJVGE2TONQ> .
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I've recently started with iPlug2. I'm building on windows 11 using MSVC2022 targeting Reaper.
I'm blind and want to provide keyboard access to the controls on my plugin.
For example, I have written a basic delay plugin that works which has 4 knob controls. I'd like the user to be able to focus on the GUI and use tab to move around the four knobs and use cursor keys to change the values. I use NVDA as my screen reader so want feedback via this.
Is there an easy way to achieve this? Or even a difficult way? AI's just spout rubbish at me on this topic.
Best, Chessel
Beta Was this translation helpful? Give feedback.
All reactions