Skip to content
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

Narrator Scan mode gets stuck at the end of WPF FlowDocument content #3175

Closed
guybark opened this issue Jun 24, 2020 · 3 comments
Closed

Narrator Scan mode gets stuck at the end of WPF FlowDocument content #3175

guybark opened this issue Jun 24, 2020 · 3 comments
Assignees
Labels
accessibility mas An issue which is a MAS (Microsoft Accessibility Standards) certification requirement Accessibility An issue related to accessibility enhancements or blockers.
Milestone

Comments

@guybark
Copy link

guybark commented Jun 24, 2020

This bug has been logged in response to a bug being logged against a Microsoft app, relating to Narrator's navigation behavior at the app. I've not verified myself that the issue repros with .NET Core.

  1. Build a new WPF app with .NET Framework 4.8.
  2. Add the following XAML:
Hello. 3. Point Narrator to the running app UI, (I'm on Windows 1909). 4. Move through the app UI in Narrator's Scan mode.

Expected result: Narrator moves through all the UI in the app.

Actual result: Narrator won't move beyond the last of the content in the FlowDocument.

Note: Narrator may jump out of Scan mode when encountering the FlowDocument. If this happens for you when repro'ing the issue, explicitly re-enter Scan mode and try to move forward out of the FlowDocument.

Note: Replacing the use of the RichTextBox hosting the FlowDocument with a FlowDocumentReader didn't seem to avoid the issue. In fact, when a FlowDocumentReader is used, the app's UIA representation includes two document elements, which seems unexpected.

I've been told that when Narrator attempts navigate forward by Paragraph in RichTextBlock in this specific scenario, the same paragraph will be returned over and over again. The API in question is ITextRangeProvider::Move with TextUnit_Paragraph.

The following image shows that the UIA hierarchy of the app seems reasonable.

FlowDocument

@fabiant3 fabiant3 added the Bug Product bug (most likely) label Jun 29, 2020
@fabiant3
Copy link
Member

@guybark - can you update the post with the XAML? //Add the following XAML:

@fabiant3 fabiant3 added this to the Future milestone Jun 29, 2020
@guybark
Copy link
Author

guybark commented Jul 19, 2020

@fabiant3, add the following XAML in a UWP XAML app newly created in VS...

<Grid Margin="20"> <Grid.RowDefinitions> <RowDefinition Height="Auto" /> <RowDefinition Height="*" /> <RowDefinition Height="Auto" /> <RowDefinition Height="Auto" /> </Grid.RowDefinitions> <Button Grid.Row="0" Content="Before" /> <RichTextBox Grid.Row="1" AutomationProperties.Name="Details"> <FlowDocument> <Paragraph> Hello. </Paragraph> </FlowDocument> </RichTextBox> <TextBlock Grid.Row="2" Text="This is static, not-focusable text." /> <Button Grid.Row="3" Content="After" /> </Grid>

@merriemcgaw merriemcgaw added Accessibility An issue related to accessibility enhancements or blockers. accessibility mas An issue which is a MAS (Microsoft Accessibility Standards) certification requirement labels Oct 13, 2021
@anjali-wpf anjali-wpf self-assigned this Nov 1, 2021
@anjali-wpf
Copy link
Contributor

@guybark This issue is not reproducible. I tested your code, it is working fine. It is not getting stuck at the end of WPF flow document. Please find attached video.

Media1.mp4

@anjali-wpf anjali-wpf removed the Bug Product bug (most likely) label Dec 12, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accessibility mas An issue which is a MAS (Microsoft Accessibility Standards) certification requirement Accessibility An issue related to accessibility enhancements or blockers.
Projects
None yet
Development

No branches or pull requests

4 participants