Bug 51913 - [Xamarin-Profiler]: Accessibility: MAS40B: Windows: Inspect: The name-property text is incomprehensible for for the table content under call tree's inspector view
Summary: [Xamarin-Profiler]: Accessibility: MAS40B: Windows: Inspect: The name-propert...
Status: CLOSED FIXED
Alias: None
Product: Profiler
Classification: Xamarin
Component: Windows ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: 15.3
Assignee: Jose Miguel Torres
URL:
Depends on:
Blocks:
 
Reported: 2017-01-28 10:28 UTC by Ramya Sri Narasinga
Modified: 2017-07-07 07:01 UTC (History)
6 users (show)

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


Attachments
13.Incomprehensible text for call tree's inspector view (189.22 KB, image/png)
2017-01-28 10:28 UTC, Ramya Sri Narasinga
Details
name-property text _after fix (149.25 KB, image/png)
2017-07-07 07:01 UTC, Ramya Sri Narasinga
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 FIXED

Description Ramya Sri Narasinga 2017-01-28 10:28:50 UTC
Created attachment 19595 [details]
13.Incomprehensible text for call tree's inspector view

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 Profiler 1.0.4 

Pre-Requisites: 
1. Install Microsoft Visual Studio 2017 (Enable .Net, Android Emulators, Mobile Development Features).
2. Launch Microsoft Visual Studio 2017 and Log in with valid VS details.
3. Map Xamarin Account to Visual Studio (Tools -> Xamarin Account -> provide Valid Credentials).
4. Create New project (Template C# -> Cross Platform -> Xamarin template).
5. Select Debug Mode -> ARM -> Select App Name.Droid -> Select Android Emulator.
6. Build the application (Application Should Build Successfully).

Repro Steps: 
"1. Run Pre-requisite
2. Navigate to Top status bar of ""Visual Studio 2017 RC"" >Analyze> Xamarin Profiler> , then Press ENTER to launch Xamarin Profiler.
 (Xamarine Profiler is launched.)
""General"" tab button-> All Instruments-> ""Allocations"" of Instrument list-> ""Call tree"" tab of ""Instrument Detail Area"" -> Inspector View pane-> Info tab-> table contents of allocations per thread-> Threadpool worker, 
"


Actual result:
"The name property for these table contents(ie Threadpool worker,..) is as below: 
""XamarinProfiler.Instruments.ThreadsListItem""
Narrator: The narrator announces as below: 
""XamarinProfiler.Instruments.ThreadsListItem""
"


Expected result:
"The name property for these table contents(ie Threadpool worker,..) should be as below: 
""Threadpool worker""
Narrator: The narrator should announce as ""Threadpool worker, row 1 of 7"""


User impact: 
These incomprehensible text are very confusing for the screen reader user, who completely rely on screen reader.
Comment 1 xamarin-release-manager 2017-05-12 14:06:58 UTC
Fixed in version 1.5.99.141 (master)

Author: Jose Miguel Torres
Commit: 6a4cd5ac188293b77b57659566090ca71967d1e0 (xamarin/profiler)
Comment 2 Ramya Sri Narasinga 2017-07-07 07:01:37 UTC
Created attachment 23370 [details]
name-property text _after fix

Verified the issue in version 1.5.5.8
Issue got fixed. Hence closing bug.