Accessibility-insights-web: Screen Reader announces content page tab as "document unknown"

[Shobhit1]

Describe the bug

Content reader (NVDA) announces the new tab opened for content

To Reproduce
Steps to reproduce the behavior:

1. Open any assessment from Assessment option on AI4W browser extension
2. Open NVDA
3. tab through to the Guidance link and press Space
4. Check NVDA output

Expected behavior

NVDA reads document unknown before announcing the title of the content page.
It should just announce the title and not document unknown.

Screenshots

Extension (please complete the following information)

• OS: Windows 10
• Version: Insider
• Browser Version: Edge Insider Version 75.0.139.1 (Official build) dev (64-bit)
• Target Page: Doesn't matter

Are you willing to submit a PR?

Yes

[msft-github-bot]

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

[ferBonnin]

@iamrafan thoughts on this?

[msft-github-bot]

This issue has been marked as requiring additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, please update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

[iamrafan]

@ferBonnin NVDA is doing this because of the target="_blank" attribute on the hyperlink used to navigate to this page. Let me file it with NVDA team and find out their take on the issue

[iamrafan]

Filed https://github.com/nvaccess/nvda/issues/9533

[ferBonnin]

thanks @iamrafan!

[ferBonnin]

per reply on NVDA bug this seems like a weird edge condition. @Shobhit1 does this repros if you start NVDA before?

[msft-github-bot]

The team requires additional author feedback; please review their replies and update this issue accordingly. Thank you for contributing to Accessibility Insights!

[Shobhit1]

@ferBonnin For this I have NVDA running on my machine, before I clicked on any other link. I dont completely understand what "starting NVDA before" means. Sorry.

[ferBonnin]

@Shobhit1 repro steps indicate open Assessment and then launch NVDA, per the bug Guru opened nvaccess/nvda#9533 the workflow seems a bit odd.

[iamrafan]

@ferBonnin I don't think it has anything to do with when NVDA is started, I think it related to focus and how NVDA handles pages without a focusable component

[msft-github-bot]

This issue has been marked as requiring additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, please update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

[karanbirsingh]

@iamrafan @ferBonnin looks like there's a response on the bug Guru filed - we might want to reply

[DaveTryon]

After checking with Karan, the status of this should not have been changed on 9 October. Undoing those changes.

[ferBonnin]

@iamrafan friendly ping to take a look at the reply of the bug you filed, please

[iamrafan]

@Shobhit1 I do not see this issue anymore, can you please let me know if you are able to repro?

[Shobhit1]

Verified that the issue cannot be replicated anymore. Closing.