[
    {
        "role": "user",
        "content": "I%20have%20installed%20vst%20plugins%20for%20reaper%20but%20can%27t%20see%20to%20get%20a%20echo%20or%20reverb%20how%20do%20I%20show%20what%20plugins%20are%20installed%20using%20jaws"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s how to *use JAWS* (or any screen reader) to show which VST plugins are installed in **REAPER**, especially to find echo or reverb effects. I\u2019ll include keyboard-friendly navigation and tips to make the FX plugin list more visible and usable.\n\n---\n\n## 1. Make sure accessibility tools are installed\n\n- REAPER supports screen readers better when using the **OSARA** extension, which improves compatibility using MSAA / UI Automation. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n- Also useful: the SWS extension, which adds many accessibility actions that work with OSARA. ([nolabelnoproducernolimits.com](https://nolabelnoproducernolimits.com/indie/production/reaper/reaper-interface-tweaks/accessibility/?utm_source=openai))  \n\n---\n\n## 2. Open the FX Browser (plugin/effect list)\n\nYou\u2019ll need to open the list of FX (where echo, reverb, etc. are):\n\n- Select a track in REAPER (use arrow keys or keyboard navigation).\n- Press the **FX button** on that track (can be done via keyboard or navigating to the track\u2019s control panel). This opens the FX chain window for that track.  \n- Or use the main menu: *View \u2192 FX Browser*, or press **Shift+F** ([reaper.fm](https://www.reaper.fm/userguide/ReaperUserGuide703c.pdf?utm_source=openai))\n\n---\n\n## 3. Navigate the FX Browser using JAWS\n\nOnce the FX browser is open:\n\n- Use **Tab** and **Shift+Tab** to move through different interface elements (e.g. categories, filter field, plugin list).\n- Use **Arrow keys** to move through the plugin list. JAWS should read out the plugin names as you move focus to them.\n- Look for the \u201cFilter\u201d or \u201cSearch\u201d box; you can type words like *\"reverb\"*, *\"echo\"*, *delay* to narrow down the list.  \n- If the plugin UIs are graphical and not accessible, you can turn on the \u201cDefault VST to Generic UI\u201d option, which swaps in a simpler control set (sliders & named parameters) that work better with screen readers. ([reddit.com](https://www.reddit.com/r/Reaper/comments/18qpk14?utm_source=openai))\n\n---\n\n## 4. Check that installed plugin paths are known\n\nIf you don\u2019t see expected plugins (like reverb), the plugin might not be installed in a folder REAPER is scanning. To fix that:\n\n1. Go to **Options \u2192 Preferences \u2192 Plug-ins \u2192 VST**. ([help.nomadfactory.com](https://help.nomadfactory.com/faqs/f50-The-plug-in-does-not-show-up-in-Reaper-what-can-I-do/?utm_source=openai))  \n2. In the VST settings, make sure your VST directories are listed\u2014both VST2 and VST3 paths if applicable. If not, use *Edit path list \u2192 Add path\u2026* to include the folder(s) where your plugins are installed. ([process.audio](https://process.audio/support/reaper-my-plug-ins-arent-showing-up?utm_source=openai))  \n3. Click **Clear cache / Re-scan** so REAPER re-scans all the VST plugin files. ([process.audio](https://process.audio/support/reaper-my-plug-ins-arent-showing-up?utm_source=openai))  \n4. Close and re-open REAPER (or just restart the project) to make sure the changes take effect. Sometimes the cache must be cleared and rescanned more than once. ([reddit.com](https://www.reddit.com/r/Reaper/comments/1r5f2cj/weird_plugin_issue/?utm_source=openai))\n\n---\n\n## 5. Use the FX list inside tracks for quick view\n\nYou can show the FX inserts directly in the Track Control Panel (TCP) so you can hear JAWS announce which effects are on each track without opening separate windows:\n\n- Right-click in an empty part of the TCP for that track.\n- Choose **\"Show FX inserts in TCP (when size permits)\"**. This displays FX names (like reverb, echo) under track controls. ([reapertips.com](https://www.reapertips.com/post/show-fx-list-inside-tracks-in-reaper?utm_source=openai))  \n- JAWS should be able to read those names as you move through tracks. If not, getting familiar with OSARA/SWS will help. ([nolabelnoproducernolimits.com](https://nolabelnoproducernolimits.com/indie/production/reaper/reaper-interface-tweaks/accessibility/?utm_source=openai))\n\n---\n\n## 6. Toggling visibility of UI\n\nIf the plugin you load has a graphical user interface that's hard for JAWS to read:\n\n- Use the **\"Default VST to generic UI\"** preference in the VST plug-ins settings. This shows plugins in a simpler, more accessible form (sliders and text) which are much more screen-reader friendly. ([reddit.com](https://www.reddit.com/r/Reaper/comments/18qpk14?utm_source=openai))  \n- When loading a plugin into a track, check if there is a **UI toggle** option in the plugin\u2019s FX window to switch between graphical and generic UI.\n\n---\n\nIf you want, I can give you *step-by-step keystrokes* using JAWS on Windows to walk you through this in REAPER. Would you prefer those?"
    }
]