# accessibility with screen readers

**URL:** <https://forum.fxsound.com/t/accessibility-with-screen-readers/2198>\
**Category:** Get Help\
**Created:** [August 22, 2023, 8:49pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198 "2023-08-22T20:49:46Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 22, 2023, 8:49pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/1 "2023-08-22T20:49:46Z")

</div>

Good morning

I am a blind user  
I am using FxSound using a screen reader  
With a screen reader, I can’t control the audio processing slider  
I’ve tried with nvda screen reader, jaws, and even narrator  
Not all screen readers can move volume control slider

Can you help me please

---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [August 22, 2023, 9:20pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/2 "2023-08-22T21:20:45Z")

</div>

Hello Ahmed,  
A previous user did manage to control the sliders with the NVDA reader using his mouse, but contacted us because he had trouble saving presets.  
He sent this message:

> [@](#):
>
> I just grabbed FXSound just a few hours ago.  
> Totally dig this package.  
> Can’t figure out how to save a preset.  
> When I expand the Save Preset menu item,  
> my screen reader that I use (NVDA - NonVisual Desktop Access) does not read the submenu items underneath.  
> So I won’t know where to save modifications I’ve done.
> 
> I do like being able to use the mouse to manipulate sliders,  
> but would prefer better if they were included in the tab order along with the other controls in the dialog box.  
> That way, Windows keyboard handling then honors the arrows/Home/End/PageUp/PageDown.

This was the response of FxSound’s lead audio engineer:

> [@bvijay](#):
>
> This is a valid requirement and we need to make FxSound more accessible to visually challenged users.  
> I can look at improving the keyboard traversal and tab order of the UI controls  
> to improve the usability and accessibility.  
> Regarding the save preset menu option, once Save New Preset menu option is selected, it brings up a text box with the hint text “Enter your preset name”, but NVDA is not reading this text. Also, through keyboard the focus is not shifting from “Save New Preset” menu option to the preset name edit box. I will look into the fix for this.

> [@bvijay](#):
>
> I have made the UI change in the context menu, so that the preset name edit box automatically gets focused. The edit box has the hint text “Enter your preset name”, but still NVDA doesn’t say it. It just says “edit blank”.  
> After the release is done with this change, we can probably report it this issue to NVDA.

The bug regarding saving presets with NVDA was subsequently addressed in v1.1.17.0:

> [@Version 1.1.17.0 is now live](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/1):
>
> - Added language support for Hungarian, Dutch, and Thai
> - Translation corrections for Vietnamese, Chinese, and Turkish
> - New icon
> - Notifications on Windows 11 can now be disabled in the OS settings
> - Fixed bug power consumption bug in sleep
> - Bug with NVDA screen reader fixed
> - Accessibility fixes for keyboard focus and hint text in preset save

However, the change regarding the control of the sliders was never made.  
So I will send another message to the team in order to address this properly.  
In the meanwhile, feel free to add any other information you wish to share on this issue.

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 23, 2023, 12:14pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/3 "2023-08-23T12:14:23Z")

</div>

> [@doolhoofd](#):
>
> However, the change regarding the control of the sliders was never made.  
> So I will send another message to the team in order to address this properly.  
> In the meanwhile, feel free to add any other information you wish to share on this issue.

Thank you  
I hope the problem is resolved quickly.

I have another question, I want to contribute to translating the program into Arabic  
Can I do that

---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [August 23, 2023, 1:06pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/4 "2023-08-23T13:06:50Z")

</div>

> [@MesterPerfect](#):
>
> I have another question, I want to contribute to translating the program into Arabic  
> Can I do that

Sure, thank you!  
Please give me a little time to get the how-to info compiled.  
You can expect to hear back from me later today.

---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [August 23, 2023, 1:49pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/5 "2023-08-23T13:49:56Z")

</div>

You can find the text that needs translating below.  
Feel free to just paste the entire string here after translation - or, if you already have a Github account, you’re welcome to upload it to [Strings/Strings at main · fxsound2/Strings (github.com)](https://github.com/fxsound2/Strings/tree/main/Strings) yourself as a .txt file in Notepad or Wordpad titled “FxSound.ar.txt”  
Thank you for your help!

> [@Language Options](https://forum.fxsound.com/t/language-options/27/11):
>
> Hello Everyone,  
> I am the developer working on the FxSound code.  
> Many thanks to everyone for offering your help on translating the text in FxSound. It really helps us a lot in making FxSound reach more people and provide them amazing audio quality.  
> The translation requires the following text content in English to be translated and the translated strings should be integrated in code. The identifier before each line of text is required to map the English text with non-English text.  
> All the language string files are in GitHub at [Strings/Strings at main · fxsound2/Strings (github.com)](https://github.com/fxsound2/Strings/tree/main/Strings)  
> It will be great if you can reply with the language name for which you are offering your help on translation. This will avoid duplication of efforts on the same language translation.  
> Thanks in advance,  
> Vijay

> [@Language Options](https://forum.fxsound.com/t/language-options/27/11):
>
> JCTRIDX0.  
> Oops! There’s an issue with your playback device settings.  
> Before we can get started, please go through the  
> JCTRIDX1.  
> troubleshooting steps here.  
> JCTRIDX2.  
> if you’re still having problems.  
> JCTRIDX3.  
> Contact us  
> JCTRIDX4.  
> Error in system audio configuration. Unable to run FxSound  
> JCTRIDX5.  
> OK  
> JCTRIDX6.  
> Click here to see what’s new on this version!  
> JCTRIDX7.  
> FxSound in system tray  
> Click FxSound icon to reopen  
> JCTRIDX8.  
> Thanks for using FxSound! Would you be  
> interested in helping us by taking a quick 4 minute  
> survey so we can make FxSound better?  
> JCTRIDX9.  
> Take the survey.  
> JCTRIDX10.  
> Changes to your preset are not saved.  
> Do you want to exit?  
> JCTRIDX11.  
> Changes to your preset are not saved.  
> Do you want to ignore the changes?  
> JCTRIDX12.  
> Output Disconnected  
> JCTRIDX13.  
> Output:  
> JCTRIDX14.  
> Changes to preset %S are saved.  
> JCTRIDX15.  
> New preset %S is saved.  
> JCTRIDX16.  
> Reached the limit on new presets.  
> JCTRIDX17.  
> Preset %S is deleted.  
> JCTRIDX18.  
> Presets are restored to factory defaults  
> JCTRIDX19.  
> Preset file %S already exists in the export path, do you want to overwrite the preset file?  
> JCTRIDX20.  
> FxSound is %S.  
> JCTRIDX21.  
> on  
> JCTRIDX22.  
> off  
> JCTRIDX23.  
> Preset: %S  
> JCTRIDX24.  
> Clarity  
> JCTRIDX25.  
> Ambience  
> JCTRIDX26.  
> Surround Sound  
> JCTRIDX27.  
> Dynamic Boost  
> JCTRIDX28.  
> Bass Boost  
> JCTRIDX29.  
> Enhances and elevates high end  
> fidelity and presence  
> JCTRIDX30.  
> Thickens and smooths audio  
> with controlled reverberation  
> JCTRIDX31.  
> Widens the left-right balance  
> for expansive, wide sound  
> JCTRIDX32.  
> Increases overall volume and balance  
> with responsive processing  
> JCTRIDX33.  
> Boosts low end for full,  
> impactful response  
> JCTRIDX34.  
> Super-low Bass. Increase this for more rumble and “thump”, decrease if there’s too much boominess.  
> JCTRIDX35.  
> Center of your Bass sound. Increase this for a fuller low end, decrease if the bass sounds overwhelming.  
> JCTRIDX36.  
> The low end of your mid-range. Increase this to make vocals sound rich and warm, decrease it to help control instruments that sound loud and muffled.  
> JCTRIDX37.  
> A focal point of the low-mid-range. Increase this to bring out electric guitars and vocal volume, decrease it to reduce any “boxy” tones.  
> JCTRIDX38.  
> The center mid-range band. Increase this to drastically boost rhythm instruments and snare hits, reduce it to cut out “nasal” tones.  
> JCTRIDX39.  
> The high-mid-range. Increase this to get more instrumental harmonics, reduce it to improve drums that have too much “clickiness” or orchestral instruments that are piercing.  
> JCTRIDX40.  
> The lower end of the high-end range. Increase this for more vocal clarity and articulation, reduce it and move the frequency wheel up and down to find and cut out overly loud “S” and “T” sounds.  
> JCTRIDX41.  
> The core high-end range. Increase this to make your audio sound more like it’s in an airy, large space, reduce it to help with room noises and unwanted echoing.  
> JCTRIDX42.  
> The highest range of average human hearing. Increase this to give your sound more of a crisp tone, with lots of overtones. Reduce it to remove hiss or painfully high sounds.  
> JCTRIDX43.  
> This wheel allows you to adjust which frequencies this EQ band is affecting  
> up or down to target different frequencies/pitches. The EQ slider above  
> controls the volume of this EQ band. Increase or decrease to boost or cut  
> a portion of your audio’s frequencies, without modifying the rest of your sound.  
> JCTRIDX44.  
> SUBSCRIBE NOW  
> JCTRIDX45.  
> Yes  
> JCTRIDX46.  
> No  
> JCTRIDX47.  
> Export Presets  
> JCTRIDX48.  
> Export  
> JCTRIDX49.  
> Select the presets to export…  
> JCTRIDX50.  
> Presets are exported successfully!  
> JCTRIDX51.  
> Presets successfully imported  
> JCTRIDX52.  
> Duplicate presets not imported  
> JCTRIDX53.  
> Import Presets  
> JCTRIDX54.  
> Import  
> JCTRIDX55.  
> Select the folder which contains the presets…  
> JCTRIDX56.  
> Folder:  
> JCTRIDX57.  
> Preset files not found in the selected folder.  
> JCTRIDX58.  
> Settings  
> JCTRIDX59.  
> Donate  
> JCTRIDX60.  
> General  
> JCTRIDX61.  
> Help  
> JCTRIDX62.  
> General Preferences  
> JCTRIDX63.  
> Launch on system startup  
> JCTRIDX64.  
> Automatically switch to newly connected output device  
> JCTRIDX65.  
> Hide help tips for audio controls  
> JCTRIDX66.  
> Disable keyboard shortcuts  
> JCTRIDX67.  
> Reset presets to factory defaults  
> JCTRIDX68.  
> Turn FxSound On/Off (Ctrl + Alt + Q)  
> JCTRIDX69.  
> Open/Close FxSound (Ctrl + Alt + E)  
> JCTRIDX70.  
> Change Preset (Ctrl + Alt + A / D)  
> JCTRIDX71.  
> Change Playback Device (Ctrl + Alt + W / S)  
> JCTRIDX72.  
> Language  
> JCTRIDX73.  
> Disable debug logging  
> JCTRIDX74.  
> Version  
> JCTRIDX75.  
> Support  
> JCTRIDX76.  
> Maintenance  
> JCTRIDX77.  
> Changelog  
> JCTRIDX78.  
> Quick tour  
> JCTRIDX79.  
> Submit debug logs  
> JCTRIDX80.  
> Help center  
> JCTRIDX81.  
> Feedback  
> JCTRIDX82.  
> Check for updates  
> JCTRIDX83.  
> Open  
> JCTRIDX84.  
> Exit  
> JCTRIDX85.  
> Turn Off  
> JCTRIDX86.  
> Turn On  
> JCTRIDX87.  
> Preset Select  
> JCTRIDX88.  
> Playback Device Select  
> JCTRIDX89.  
> Enter your preset name  
> JCTRIDX90.  
> Enter new preset name  
> JCTRIDX91.  
> Overwrite Existing Preset  
> JCTRIDX92.  
> Save New Preset  
> JCTRIDX93.  
> Undo Preset Changes  
> JCTRIDX94.  
> Rename Preset  
> JCTRIDX95.  
> Delete Preset  
> JCTRIDX96.  
> Download Bonus Presets  
> JCTRIDX97.  
> FxSound is unable to play processed audio through the selected output device.  
> Another application could be using it in exclusive mode or the device could be  
> disconnected. To disable exclusive mode follow these  
> JCTRIDX98.  
> steps.  
> JCTRIDX99.  
> Click here to save new presets, overwrite old ones, or reset your settings.  
> JCTRIDX100.  
> Settings file not found!

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 23, 2023, 5:05pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/6 "2023-08-23T17:05:20Z")

</div>

> [@doolhoofd](#):
>
> You can find the text that needs translating below.  
> Feel free to just paste the entire string here after translation - or, if you already have a Github account, you’re welcome to upload it to [Strings/Strings at main · fxsound2/Strings (github.com)](https://github.com/fxsound2/Strings/tree/main/Strings) yourself as a .txt file in Notepad or Wordpad titled “FxSound.ar.txt”  
> Thank you for your help!

This was fun, I just finished translating all phrases into Arabic, and I opened a pull request on github

> <https://github.com/fxsound2/Strings/pull/11>
>
> All FxSound phrases have been translated into Arabic

It remains only to approve the withdrawal request from the administrator

---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [August 23, 2023, 6:23pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/7 "2023-08-23T18:23:03Z")

</div>

> [@MesterPerfect](#):
>
> It remains only to approve the withdrawal request from the administrator

Awesome! 👍 ❣  
I forwarded it to the team, you should be getting confirmation very soon.

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 23, 2023, 6:36pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/8 "2023-08-23T18:36:49Z")

</div>

> [@doolhoofd](#):
>
> I forwarded it to the team, you should be getting confirmation very soon.

thank you

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [August 24, 2023, 2:33pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/9 "2023-08-24T14:33:48Z")

</div>

Thank you @MesterPerfect for helping us with the Arabic translation. We have merged your translation file in GitHub.  
We will integrate the translation in FxSound in the coming releases. We will also have to make some UI changes for right alignment of text for Arabic.

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [August 24, 2023, 2:42pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/10 "2023-08-24T14:42:05Z")

</div>

Hello @MesterPerfect  
Thanks for pointing out the issues in the slider control. I am sorry that I didn’t address the slider control function when making the accessibility related fixes recently.  
As I understand the slider control is not working with arrow keys on the keyboard. Please let me know if there is any other limitation that you want us to get fixed.

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 24, 2023, 4:45pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/11 "2023-08-24T16:45:29Z")

</div>

> [@bvijay](#):
>
> Thank you @MesterPerfect for helping us with the Arabic translation. We have merged your translation file in GitHub.  
> We will integrate the translation in FxSound in the coming releases. We will also have to make some UI changes for right alignment of text for Arabic.

Thank you  
I’m looking forward to using fxSound in Arabic

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 24, 2023, 4:53pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/12 "2023-08-24T16:53:07Z")

</div>

> [@bvijay](#):
>
> Thanks for pointing out the issues in the slider control. I am sorry that I didn’t address the slider control function when making the accessibility related fixes recently.  
> As I understand the slider control is not working with arrow keys on the keyboard. Please let me know if there is any other limitation that you want us to get fixed.

Thank you for your help  
Yes, I can’t control the slider with the keyboard arrows

Also, I will check accessibility with the program to make sure there are no other problems  
I will respond within hours

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 25, 2023, 8:14pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/13 "2023-08-25T20:14:04Z")

</div>

> [@bvijay](#):
>
> Thanks for pointing out the issues in the slider control. I am sorry that I didn’t address the slider control function when making the accessibility related fixes recently.  
> As I understand the slider control is not working with arrow keys on the keyboard. Please let me know if there is any other limitation that you want us to get fixed.

Hello again,  
I have tested the program with accessibility  
I have not encountered any additional problems other than this screen

![import and export](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/f/f15b423a2284e84ab3ef33e69f6e53b2dd92ddc8.jpeg)

It cannot be used by screen readers  
If they can be fixed that would be great

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [August 28, 2023, 5:34pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/14 "2023-08-28T17:34:32Z")

</div>

Sorry for the trouble that you are facing with the Import Presets screen. Thanks for testing it and pointing out the issue.  
I will address it and get it fixed in the coming releases.

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 31, 2023, 12:38am UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/16 "2023-08-31T00:38:28Z")

</div>

```
  [quote="bvijay, post:14, topic:2198"]
  Sorry for the trouble that you are facing with the Import Presets screen. Thanks for testing it and pointing out the issue.
  I will address it and get it fixed in the coming releases.
  [/quote]
  
  thank you 
  I'm looking forward to testing the next release

```

---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [August 31, 2023, 12:48am UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/17 "2023-08-31T00:48:17Z")

</div>

Hi @MesterPerfect,  
I just wanted to say sorry for the trouble you just experienced.  
Our forum has some odd quirks, one of which being that “the system” automatically rejects a message that quotes the entire text of someone’s post.  
Apologies for that.  
Also, weirdly enough, a full quote does work if, for example, you delete the last full stop with backspace, and then just type in another one yourself; so, there are workarounds.

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [August 31, 2023, 1:29am UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/18 "2023-08-31T01:29:51Z")

</div>

> [@doolhoofd](#):
>
> I just wanted to say sorry for the trouble you just experienced.  
> Our forum has some odd quirks, one of which being that “the system” automatically rejects a message that quotes the entire text of someone’s post.  
> Apologies for that.  
> Also, weirdly enough, a full quote does work if, for example, you delete the last full stop with backspace, and then just type in another one yourself; so, there are workarounds.

Never mind, I love forums and I’m used to errors like this

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [September 20, 2023, 3:45pm UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/19 "2023-09-20T15:45:34Z")

</div>

Hi @MesterPerfect  
We have a new release available as beta at [https://www.dropbox.com/scl/fi/zvyq13igjfwe8ffc20irm/fxsound\_setup.exe?rlkey=ni6rbadrjchpj3h7icsc82bhb&dl=1](https://www.dropbox.com/scl/fi/zvyq13igjfwe8ffc20irm/fxsound_setup.exe?rlkey=ni6rbadrjchpj3h7icsc82bhb&dl=1)  
The arrow key allows the equalizer and effects sliders to move in this release. Also, please note that the button positions have changed in this release and all the buttons are moved to the top of the window.  
We couldn’t get the screen reader issue fixed with the Import Presets UI yet.  
Also, the Arabic translation is not yet integrated in this release. We are planning to do it in the next release, since along with the translation integration we also have to make some alignment changes in the UI.

---

<div class="post-metadata">

**Author:** ![MesterPerfect](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/mesterperfect/32/1248_2.png) [@MesterPerfect](https://forum.fxsound.com/u/MesterPerfect)\
**Post date:** [September 26, 2023, 1:19am UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/20 "2023-09-26T01:19:42Z")

</div>

> [@bvijay](#):
>
> We have a new release available as beta at [https://www.dropbox.com/scl/fi/zvyq13igjfwe8ffc20irm/fxsound\_setup.exe?rlkey=ni6rbadrjchpj3h7icsc82bhb&dl=1](https://www.dropbox.com/scl/fi/zvyq13igjfwe8ffc20irm/fxsound_setup.exe?rlkey=ni6rbadrjchpj3h7icsc82bhb&dl=1)  
> The arrow key allows the equalizer and effects sliders to move in this release. Also, please note that the button positions have changed in this release and all the buttons are moved to the top of the window.  
> We couldn’t get the screen reader issue fixed with the Import Presets UI yet.  
> Also, the Arabic translation is not yet integrated in this release. We are planning to do it in the next release, since along with the translation integration we also have to make some alignment changes in the UI.

hi @bvijay  
Yes I have tested all of this and I have pointed out the new problems

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [September 26, 2023, 6:57am UTC](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198/21 "2023-09-26T06:57:52Z")

</div>

Thanks @MesterPerfect. Sorry that there are some new issues with accessibility. I am working on the fixes for these issues.

[Next page](https://forum.fxsound.com/t/accessibility-with-screen-readers/2198.md?page=2)