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
Word Page numbering style "- 1 -" reads "dash" for page 2 onwards #6004
Comments
It appears that NVDA is not moving through other headers at all with this page numbering style in effect. I tried adding additional pages to a document but not much luck. |
It does move between pages for me, although without it reading the page To test, you can insert a page number elsewhere although you can't do it 22 Point Web: http://www.22point.com.au Check out our first app, RapiTap! - Tap targets fast & avoid decoys: On 28 May 2016 at 00:31, PratikP1 notifications@github.com wrote:
|
This is definitely a bug in MS Word in the way that it allows moving by word and characters. Sometimes it skips over part of the field as we collect text. If this is specific to page fields I can probably work around this with out too much fuss. However, it would be nice to get an idea if there are other fields that are also broken. E.g. date/time fields seem to work fine. |
Using Word 2013. |
This change allows the page number part of a header to be read out when moving by line. We are still unable to move through this field by character.
This change allows the page number part of a header to be read out when moving by line. We are still unable to move through this field by character.
When using Microsoft Word, page-number fields in headers can now be read. (#6004)
In Word 2016 at least, from a blank document, press control+enter to add a second page. Then add page numbers (alt+n, n, u then any style - top of page, plain text 1 is fine). Press the applications key and choose "format page numbers", press down arrow to change number format to - 1 -, - 2 -, - 3 - and press enter to accept.
Page 1's number reads as "- 1 -" but page 2 onwards only read as "dash".
The text was updated successfully, but these errors were encountered: