-
-
Notifications
You must be signed in to change notification settings - Fork 634
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
Always read superscripted and subscripted numbers. #6438
Comments
I think separating superscript/subscript from attributes makes sense. I'd be reluctant (at least at this stage) to introduce heuristics based on the presence of numbers or the like, as this doesn't account for some edge cases (e.g. x sub y) and it's hard to get right. It's worth noting, though, that you would hear "10 superscript 44 baseline". P3 because this would certainly improve some common use cases and it's not a difficult change. |
cc: @nvdaes |
Based on this comment in PR #10448 I suggest to extent this issue here to the most important font attributes. Here the list:
|
cc: @lukaszgo1 |
I think this issue has been resolved with PR #10919. Always reading super / sub script can now be configured independently of other format settings. |
I think this is not fixed, but this might be due to the rendering of the characters. If I write 1^3 NVDA still reads "1 3" instead of "1 superscript 3". |
Actually such numbers are usually read as for example 1 to the 3 instead of "1 superscript 3". |
@Adriani90 I think the
Indicating that it is already something that can be enabled, but only if you enable other format reporting that isn't desired. |
yes. For example, science fields use super/subscripts. For example, |
Given the initial description and the last comments, I'll close this issue as fixed by #10919. If you still need a finer control of reported attributes, please open a new issue or comment in existing ones. |
one thing that might be useful is to ignore the font attribute setting for numbers, (or create a new one for subscript/superscript) so that NVDA will read numbers like 10^44 as 10 superscript 44, rather than 1044. it's annoying to have to turn all font attributes on for a webpage, just so that I can hear 10 superscript 44.
This might require a redesign of the font settings of the document formatting dialog, maybe a configure font settings button in this dialog, so users can have more fine grained control over the font.
The text was updated successfully, but these errors were encountered: