Screenreader does not read subsequent consecutive frames

• Sep 19, 2019 - 20:58
Reported version
3.2
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore
Tags
accessibility

1) run NVDA
2) score with title frame
3) insert another vertcial frame before the first measure
4) add text
5) use Alt+left/right to navigate

Result: the first frame encountered during navigation is read, but not the second

Comments

• Sep 30, 2019 - 22:16
Status PR created ⇒ fixed

Fixed in branch master, commit 6eb27cbdbe

_fix #294677: screenreader does not read consecutive frames

The screenreader info code tries to optimize during navigation and not read info that has not changed.
Unfortunately this is a little too effective,
we end up optimizing away information about consecutive frames.
This commit fixes this by limiting the optimization to elements with bar and beat info,
which is what we are trying to optimize.
So frames and any other elements whose status bar info does not change from element to element
will no longer be optimized.
The code accomplishes this by clearing the oldcAcessibilityInfo for elements with no barsAndBeats info,
then checking for empty oldAccessibilityInfo before reusing it.
This lso has the benefit of forcing a rebuild of the accessibility info
if it ever accidentally gets cleared for any other reason._

Reply

Fix version
3.3.0