Bug reports and suggestions for improving accessibility

• May 31, 2024 - 13:33

Hi everyone!
I'd like to report a few bugs and make some suggestions to improve accessibility.
Please tell me where this can be done?
Perhaps there is a link to a special form for reporting this?

Comments

mercuree

• May 31, 2024 - 13:46

You can do it right here

Diane Powell Walter

• Jun 1, 2024 - 00:22

The iOS app screws up on some iPhones: The entry pages are made with jumbo letter size which prevents the user from reading the score.

Attachment	Size
IMG_6155.jpg	530.28 KB

TheHutch

• Jul 8, 2024 - 19:08

Diane,

Mobile apps are not supported here at musescore.org. You need to go to musescore.com to report this issue.

vlad-mus

• Jul 2, 2024 - 13:58

Bug report #1
Topic: Accessibility issue when removing gradual tempo change without using mouse.

NVDA screen reader is used.

Create a score in the new score window.
Adding an instrument to a new score.
Editing notes.
Adding a gradual tempo change.
Adding a dynamics.
Using the Alt + horizontal arrow key combination helps to find the dynamics, but does not help to find the gradual tempo change to delete it.

Link to video demonstration:
Bug_report_№1_(2024-07-02_15-20-26).mp4
https://disk.yandex.ru/i/cjJ6Sj-5f90Xeg

DanielR

• Jul 9, 2024 - 09:11

Bug report #1 has been reposted on Github's MuseScore Issues:
https://github.com/musescore/MuseScore/issues/23522

@vlad-mus
If you open a free account on Github, you can add more details to this issue on Github. For example: which Mu4 version, and details of OS used.

vlad-mus

• Jul 8, 2024 - 15:17

Bug report #2
Topic: Accessibility issue in the names of some signs in a master palette of signs

NVDA screen reader is used.

Creating a score in the new score window.
Adding an instrument to a new score.
Editing notes.
Opening the master palette with the key combination Shift + F9
Selecting one of the following categories with a problem:

* Accidentals;
* Grace notes;
* Noteheads;
* Layout;
* Beam properties.
6. Some signs from these categories have problems with their names. Instead of the name of the sign we hear: "Akcion icon".

Link to video demonstration:
Bug_report_№2_(2024-07-08_17-05-06).mp4
https://disk.yandex.ru/i/n88Vurc4RS_Y2g

DanielR

• Jul 9, 2024 - 09:20

Bug report #2 has been reported on Github's MuseScore Issues page:
https://github.com/musescore/MuseScore/issues/23523

@vlad-mus
Please add to the Github Issue any missing information (version of MuseScore Studio, Windows version).

DanielR

• Jul 9, 2024 - 09:28

"I'd like to report a few bugs and make some suggestions to improve accessibility.
Please tell me where this can be done?
Perhaps there is a link to a special form for reporting this?"

To be clear:
a) This Support forum on musescore.org allows users to validate whether their apparent fault is a real bug. But in general these forums are read only by fellow-users, not by developers.
b) If there is a genuine bug, the only way to get the attention of the MuseScore developers is then to raise a new Issue on Github (you need a free Github account before you can post there):
https://github.com/musescore/MuseScore/issues/new/choose

vlad-mus

• Jul 9, 2024 - 13:48

Thank you very much!
Now I will try to publish issues on GitHub.
If you can edit issues for Bug report #1 and Bug report #2 on GitHub, please add version 4.3.2 for MuseScore version and Windows 10 (64 bit).

DanielR

• Jul 9, 2024 - 21:04

"If you can edit issues for Bug report #1 and Bug report #2 on GitHub, please add version 4.3.2 for MuseScore version and Windows 10 (64 bit)."

No problem, both issues have now been updated with the info. Thank you!