Bug 51932 - [Xamarin-Profiler]:Accessibility:MAS36: Windows: Keyboard:Time span Scale is not accessible for the selected instruments.
Summary: [Xamarin-Profiler]:Accessibility:MAS36: Windows: Keyboard:Time span Scale is ...
Status: CLOSED FIXED
Alias: None
Product: Profiler
Classification: Xamarin
Component: Windows ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: 15.2
Assignee: Jose Miguel Torres
URL:
Depends on:
Blocks:
 
Reported: 2017-01-28 12:11 UTC by Dona Venkata Jaswanth Kumpatla
Modified: 2017-07-11 21:27 UTC (History)
7 users (show)

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


Attachments
Please find the attached screenshot (136.43 KB, application/x-zip-compressed)
2017-01-28 12:11 UTC, Dona Venkata Jaswanth Kumpatla
Details
Log (1.65 KB, application/x-zip-compressed)
2017-04-13 12:17 UTC, Swati Gangrade
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 Dona Venkata Jaswanth Kumpatla 2017-01-28 12:11:29 UTC
Created attachment 19614 [details]
Please find the attached 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 Profiler 1.0.4

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

Repro:
1.Launch Xamarin profiler through Visual Studio.
2.From "Choose an Instrument Template" window navigate to the "General" tab and select any instruments tab from the existing "Available Instruments”.
3.Navigate to "Xamarin Profiler" window and try to access time span scale in "Plot Chart" section.

Actual Result:
"Time span" scale is not accessible for the selected instrument.
Observation:
"Time span" scale gives the "Time and Value" information for the selected instrument, which is observed when user mouse hover on it.

Expected Result: 
"Time span" scale should be accessible for the selected instrument, where the user is missing the "Time and Value" information.

Suggested fix:
The Is Keyboard Focusable and Has Keyboard Focus must be "True".

User Impact:
Visually impaired users who are dependent on keyboard navigation find difficult when the UI elements are not accessible while navigating through the application.
Comment 1 xamarin-release-manager 2017-04-06 10:24:24 UTC
Fixed in version 1.5.99.35 (master)

Author: Jose Miguel Torres
Commit: 053203387da79b307cb5db54141eeedc8a6d12a4 (xamarin/profiler)
Comment 2 Swati Gangrade 2017-04-13 12:17:42 UTC
Created attachment 21502 [details]
Log

Bug is retested in the below build test environment:

• Microsoft Visual Studio Enterprise 2017 d15rel Version 15.1 (26403.0) d15rel d15rel
• Microsoft .NET Framework Version 4.6.01586
• Xamarin   4.5.0.339 (265d40a)
• Xamarin.Android SDK   7.3.0.5 (40f69c3)
• Xamarin.iOS and Xamarin.Mac SDK   10.10.0.4 (9245c1c)
• Xamarin Profiler Version 1.5.99.57

Actual result- It is working as mentioned in the expected result. Hence marking as verified 

Screen Cast Link-https://www.screencast.com/t/SmVHUEJkhhh
Comment 3 Adrian Murphy 2017-07-11 21:25:56 UTC
VF per Salieu Njie on 7/8/17. Updating BZ as their contractor did not have access permissions to change the bug state.