Bug 51823 - [Xamarin-Inspector]:Accessibility: MAS40B:Windows: Inspect: Name property is empty for the REPL window
Summary: [Xamarin-Inspector]:Accessibility: MAS40B:Windows: Inspect: Name property is ...
Status: CLOSED UPSTREAM
Alias: None
Product: Workbooks & Inspector
Classification: Xamarin
Component: Accessibility ()
Version: master
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bojan Rajkovic [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2017-01-27 11:22 UTC by Naveen Katakam
Modified: 2018-05-14 06:59 UTC (History)
2 users (show)

Tags: accessibility, wipro, xamarin-inspector, a11ymas, mas40b
Is this bug a regression?: ---
Last known good build:


Attachments
Inspect Screenshot (267.84 KB, image/png)
2017-01-27 11:22 UTC, Naveen Katakam
Details
Name property is not descriptive (263.72 KB, image/png)
2017-09-15 10:16 UTC, Ramya Sri Narasinga
Details
Inspect screenshot (88.82 KB, image/png)
2017-09-18 15:52 UTC, Bojan Rajkovic [MSFT]
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
CLOSED UPSTREAM

Description Naveen Katakam 2017-01-27 11:22:54 UTC
Created attachment 19515 [details]
Inspect Screenshot

Testing Environment:
  OS: 
      •	Windows 10.
      •	Version 1067.
      •	Build 14393.607.
  Visual Studio and Xamarin:
      •	VS 2017 RC Enterprise.
      •	Xamarin For VS 4.3.0.550.
      •	Xamarin Inspector 1.0

Pre -Requisites: Build and Deploy Xamarin Application into Android Emulator

Repro:
  
  1. Launch Xamarin App.
  2. Select the "REPL" button from the bottom left corner of the app window.
  3. Select the whole pane 
  4. Observe the Name property in Inspect

Actual:
  
  The Name property is empty for the REPL pane of the app
  Narrator Behavior: Pane

Expected: 

  The Name property should be specific.
  Eg: REPL app window

User Impact:

Visually impaired users will not get to know the purpose of the REPL app window as the screen reader will not announce anything when the user arrives at the control. Providing the name property enables the compatibility with the Screen Reader, which may be used by people with disabilities.
Comment 2 Bojan Rajkovic [MSFT] 2017-05-30 15:26:43 UTC
This is fixed in the upcoming 1.3 release.
Comment 3 Ramya Sri Narasinga 2017-09-15 10:16:59 UTC
Created attachment 24763 [details]
Name property is not descriptive
Comment 4 Ramya Sri Narasinga 2017-09-15 10:17:30 UTC
Needs to be reactivated
Comment 5 Bojan Rajkovic [MSFT] 2017-09-15 13:53:34 UTC
I’m not sure we *can* set the Name property of that—it is created by the Internet Explorer control, which we have no power over. Reopening anyway, I can have a second look.
Comment 6 Bojan Rajkovic [MSFT] 2017-09-18 15:52:12 UTC
Created attachment 24800 [details]
Inspect screenshot

I did more research on this this morning, and this is *not* something we can fix.

If you look at the screenshot, this is how Internet Explorer presents itself to UI automation--the URL pane is the parent of the actual document. The `<title>` tag of the document is set as the name of its pane, but its parent is always a pane with the URL set as the name.

I will add a <title> to our HTML so that it is a little more descriptive, but otherwise, this is an "upstream" issue.
Comment 7 Ramya Sri Narasinga 2018-05-14 06:59:24 UTC
As per Ryan's comments closing this bug and filed a new bug(Bug 17503975) to track this issue.