Is your feature request related to a problem? Please describe.
In many edit boxes in which NVDA is using display model to access innformations the selection isn't announced. Examples of those include #4535 #8946 and #4756.
In most of this cases NVDA recognizes the fact, that the selected text has different color, so fixing it is only a matter of telling, that this color is the highlight.
Describe the solution you'd like
- For the app in question create a configuration profile.
- select text.
- move to the one of selected character with the object review.
- press some defined keystroke and verify that color is picked up correctly.
- Write the color to the config profile and use it when selecting text in this program.
Describe alternatives you've considered
I do not know if it can be retrieved from the config profile. If it cannot be perchaps an easy way to provide this info in the app module easy enough to be doable even for non programmers.
Additional context
It is de facto standard function in the other commercial screen readers which is able to solve many accessibility problems in a really short time and without programming experience.
Is your feature request related to a problem? Please describe.
In many edit boxes in which NVDA is using display model to access innformations the selection isn't announced. Examples of those include #4535 #8946 and #4756.
In most of this cases NVDA recognizes the fact, that the selected text has different color, so fixing it is only a matter of telling, that this color is the highlight.
Describe the solution you'd like
Describe alternatives you've considered
I do not know if it can be retrieved from the config profile. If it cannot be perchaps an easy way to provide this info in the app module easy enough to be doable even for non programmers.
Additional context
It is de facto standard function in the other commercial screen readers which is able to solve many accessibility problems in a really short time and without programming experience.