Problem: on the options screens of Ozone, RX and possibly other iZotope products, there's a setting to change the amount of keyboard support. Its default state is Minimal, so understandably, you might want to explore what else is available. The next entry down is Full, which is probably the one most screen reader users will want. However, the final option is None, and unfortunately this setting takes effect as soon as we arrow onto it, thereby making it impossible to move back to a prior option. DOH! I've made sure iZotope are aware of this issue and suggested better UX approaches, hopefully we'll see improvement before too long. In the meantime, here are instructions on how you can set keyboard support to full using the back-end resource files. I'm using Ozone 10 Standard or Advanced in the methods below, but it's probably only a short leap to apply them to other current iZotope offerings. Mac folk will need to read the first tip below and do this manually, but for Windows users, I've uploaded a set of premade .reg files. If you're not comfortable fiddling about with the registry, just run whichever file is appropriate to your situation, say Yes to add it to the registry, restart Ozone and you should be back in business. On mac, entering this command in Terminal will set keyboard support to full: defaults write com.izotope.ozoneproms.plist "Params.Global.Enum.Global Keyboard Support" -int 2 On windows, go here in RegEdit: \HKEY_CURRENT_USER\SOFTWARE\iZotope\OZONEPROMS Then set the value of the following entry to '2', keeping the base in hex as it was: Params.Global.Enum.Global Keyboard Support These instructions are for the Ozone 10 mothership (i.e the plug-in that shows up as Ozone 10 in your DAW), but each component plugin also has its own keyboard support setting. If needed, you could repeat the steps above, but everywhere it says 'ozoneproms' you would replace it with the plugin name. You'll find their names listed as titles of the plists or reg entries. Examples: ozoneprodyn ozoneprodyneq ozoneproeq Shout out to my man Jack at iZotope for the recovery tips, and for making sure this issue got a bump up in their tracker. Last update: 13th April 2023 by Scott