-
-
Notifications
You must be signed in to change notification settings - Fork 651
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
Default Punctuation of Some Does *NOT* read * (Asterisk) #3614
Comments
Comment 1 by kara_louise on 2013-10-31 02:24 |
Comment 2 by briang1 on 2013-11-01 09:28 |
Comment 3 by jteh on 2013-11-12 04:40 |
Comment 6 by Michael Curran <mick@... on 2013-11-27 01:14
|
Comment 7 by Michael Curran <mick@... on 2013-11-27 01:14
|
Comment 8 by Michael Curran <mick@... on 2013-12-02 00:22
Changes:
|
Comment 9 by Michael Curran <mick@... on 2013-12-18 23:49
Changes:
|
Comment 10 by mdcurran on 2013-12-18 23:59 |
Comment 11 by Michael Curran <mick@... on 2013-12-19 07:32
|
Reported by kevinchao89 on 2013-10-30 19:30
There are many examples where asterisks can be used to mask information for security/privacy reasons or to provide meaningful content (as an alternative to other identifiers, e.g. numbers that may already exist). Unfortunately, with the default TTS setting of some, NVDA does not read the presence of asterisks. Instead, it's silent. asterisks are only read with most in NVDA, while in other desktop-based screen readers will read it at some.
Steps to Reproduce:
Expected: star or asterisk to be read at default punctuation level of some
Actual: asterisks are not read
Note1: asterisks are only read with punctuation level of most or higher, reviewing by characters, or spell-line.
Note2: Other desktop-based screen readers will read asterisks at default punctuation level of some.
P.S. An example where asterisks may be used instead of a numeric value (in use case #2) may be in the two notes I used above. For example, Note* and Note**, where there may be already note1 and note2 or a preference to use * instead of numeric values.
The text was updated successfully, but these errors were encountered: