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 announces section breaks as page breaks #5946

Closed
Qchristensen opened this Issue May 13, 2016 · 3 comments

Comments

Projects
None yet
5 participants
@Qchristensen

Qchristensen commented May 13, 2016

When you insert a section break (new page), NVDA identifies it as simply a "page break". When you insert a section break (continuous), no identification is given by NVDA. Column breaks are also not identified.

With formatting symbols displayed, column, page and section breaks are all displayed as a dotted line (different types of dots between the three types) across the page with the type of break in (what appears visually as) text identifying "Page break (continuous)", "Column break" etc.

@derekriemer

This comment has been minimized.

Show comment
Hide comment
@derekriemer

derekriemer May 13, 2016

Collaborator

I think a similar issue can be seen with column breaks, and using the
arrow keys, no method is given to move to the next column. I might e
wrong, I only saw this once on a test.

On 5/13/2016 5:04 AM, Quentin Christensen wrote:

When you insert a section break (new page), NVDA identifies it as
simply a "page break". When you insert a section break (continuous),
no identification is given by NVDA. Column breaks are also not identified.

With formatting symbols displayed, column, page and section breaks are
all displayed as a dotted line (different types of dots between the
three types) across the page with the type of break in (what appears
visually as) text identifying "Page break (continuous)", "Column
break" etc.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#5946


Derek Riemer
  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio http://derekriemer.com
Awesome little hand built weather app!
http://django.derekriemer.com/weather/

email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu
Phone: (303) 906-2194

Collaborator

derekriemer commented May 13, 2016

I think a similar issue can be seen with column breaks, and using the
arrow keys, no method is given to move to the next column. I might e
wrong, I only saw this once on a test.

On 5/13/2016 5:04 AM, Quentin Christensen wrote:

When you insert a section break (new page), NVDA identifies it as
simply a "page break". When you insert a section break (continuous),
no identification is given by NVDA. Column breaks are also not identified.

With formatting symbols displayed, column, page and section breaks are
all displayed as a dotted line (different types of dots between the
three types) across the page with the type of break in (what appears
visually as) text identifying "Page break (continuous)", "Column
break" etc.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#5946


Derek Riemer
  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio http://derekriemer.com
Awesome little hand built weather app!
http://django.derekriemer.com/weather/

email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu
Phone: (303) 906-2194

@Qchristensen

This comment has been minimized.

Show comment
Hide comment
@Qchristensen

Qchristensen May 13, 2016

You're right, there are other issues with columns which I've been pondering as well. I just mentioned the issue with column breaks as I wasn't sure if this specific aspect was related to the section break identification.

Qchristensen commented May 13, 2016

You're right, there are other issues with columns which I've been pondering as well. I just mentioned the issue with column breaks as I wasn't sure if this specific aspect was related to the section break identification.

@michaelDCurran

This comment has been minimized.

Show comment
Hide comment
@michaelDCurran

michaelDCurran May 24, 2016

Contributor

Microsoft Word exposes all breaks as page break characters (0x12)
However We could announce section changes like we do for page changes. I.e. when arrowing anywhere if the section changes we could say "section x" before the text, where x is the new section number. We can get this with selection.sections(1).index

Contributor

michaelDCurran commented May 24, 2016

Microsoft Word exposes all breaks as page break characters (0x12)
However We could announce section changes like we do for page changes. I.e. when arrowing anywhere if the section changes we could say "section x" before the text, where x is the new section number. We can get this with selection.sections(1).index

@nvaccessAuto nvaccessAuto added the p2 label Jul 5, 2016

@feerrenrut feerrenrut self-assigned this Oct 18, 2016

feerrenrut added a commit that referenced this issue Oct 24, 2016

Report section numbers in MS word.
Fixes #5946. When reading through a document, report when the section
number changes. This is tied to the report page number setting
(available in document formatting settings dialog)

feerrenrut added a commit that referenced this issue Dec 8, 2016

incubates #6498
Issue #5946
Merge branch 'i5946-reportSectionNumber' into next

@nvaccessAuto nvaccessAuto added this to the 2017.1 milestone Dec 29, 2016

feerrenrut added a commit that referenced this issue Dec 29, 2016

Update changes file for PR #6498
- In Microsoft Word the type of section break, and the section number can now be reported. This is enabled with the "report page numbers" option in the document formatting dialog. (Issue #5946)
- In Microsoft Word the text columns can now be reported. This is enabled with the "report page numbers" option in the document formatting dialog. (Issue #5946)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment