New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved Handling of Elipsis #4085
Comments
Comment 2 by jteh on 2014-04-21 01:51 There are always going to be use cases which aren't covered by a given level. We need to be careful in considering adding symbols to lower levels, as too many would rather defeat the point. Nevertheless, we'll need to see feedback from others concerning this particular case. |
Comment 3 by briang1 on 2014-04-21 09:32 |
Comment 4 by camlorn on 2014-04-25 00:29 |
The elipsis appears in so many dialogs and buttons that I suppose one could consider as essential for default reading. Since my punctuation and symbol level settings are probably non-default, could someone please mention the default level at which ... is spoken (the ticket body seems to suggest None)? |
@bhavyashah, my … and ... are set to none. Should this be a topic that is further discussed? Personally, I do not think it should be, as @jcsteh pointed out in #4085 (comment)
|
@ehollig Thanks for the clarification. Also, upon second thought, I agree with @jcsteh's #4085 (comment). Unless we still have active NVDA users on GitHub who would like to advocate for the original proposal, I would suggest closing this ticket for the time being. |
Closing for now. We can reopen if this topic is brought up again. |
Reported by mhorspool on 2014-04-21 01:37
Announcement of the ellipsis is critical when navigating the Windows environment because it alerts the user that a dialog is about to appear. NVDA currently does not announce the ellipsis when punctuation is set to 'Some'. Furthermore, it does pass the ellipsis to the synthesizer, rendering a pause. This creates an inconsistent user experience because sometimes the control type is immediately spoken after its label, and sometimes a pause is left between the label and the control type.
I will submit that users who have their punctuation set to 'None' are advanced users, and that 'none' means just that, 'none'. A pause might actually be useful to them because it alerts them that a dialog is about to appear whilst cutting down on verbiage. However, I would expect "dot dot dot" with no pause at 'Some'. The punctuation level can be changed in the punctuation dialog box but the pause still exists.
I therefore propose that the preservation flag on the ellipsis be set to 'norep' by default. I further propose that its default punctuation level be set to some or above.
I have done this at user level and I now hear "Browse dot dot dot button". Lovely. Rather than "Browse, button" or "Browse dot dot dot, button", which was most irritating.
The text was updated successfully, but these errors were encountered: