Bug 51885 - [Xamarin-Profiler]: Usability: OSX: VoiceOver: VoiceOver is not announcing the name of any of the quick access Toolbar buttons.
Summary: [Xamarin-Profiler]: Usability: OSX: VoiceOver: VoiceOver is not announcing th...
Status: CLOSED FIXED
Alias: None
Product: Profiler
Classification: Xamarin
Component: Mac ()
Version: 1.0.x
Hardware: PC Mac OS
: --- normal
Target Milestone: 15.4
Assignee: Jose Medrano
URL:
Depends on:
Blocks:
 
Reported: 2017-01-28 07:21 UTC by Ramya Sri Narasinga
Modified: 2017-08-01 09:22 UTC (History)
6 users (show)

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


Attachments
3. Quick Access ToolBar Button do not have name (269.05 KB, image/png)
2017-01-28 07:21 UTC, Ramya Sri Narasinga
Details
Issue fixed (1.25 MB, image/png)
2017-08-01 09:21 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 07:21:21 UTC
Created attachment 19572 [details]
3. Quick Access ToolBar Button do not have name

Testing Environment:
OS: OSX (Version: 10.11.6)
Xamarin-Profiler: 1.0.4 

Pre-Requisite: 
1. Install Xamarin Studio.
2. Launch Xamarin Studio.
3. Navigate to top menu bar of the Xamarin studio> File> New Solution> Press ENTER
("Choose a template for your new project" wizard is opened)
4.  Navigate to App under Multiplatform> Forms app under Xamarin.Forms
5. Navigate to Next button> Press ENTER
('Configure your Form app' wizard is opened.)
6. Fill the App name, check all the target platform-check box, select use portable class library radio button, use XAML for user interface files.
7. Navigate to Next button> Press ENTER
(Configure your new project" wizard is opened)
8. Navigate to Create> Press ENTER.
(New project is created)
9. Turn VoiceOver ON using Commond + F5.

Repro Steps:
"1. Run Pre-requisite
2. Navigate to Top menu bar of ""Xamarin Studio"" > Run> Start Profiling, then Press ENTER to launch Xamarin Profiler.
 (Xamarine Profiler is launched.)
3. ""General"" Button (LHS)-> All instruments-> Press Enter.  (Profiling started)
4. Using CAPS+RIGHT ARROW, navigate to Toolbar(ie at the top of the profiler window)
5. Press CONTROL+OPTION+SHIFT+DOWN ARROW  keys to interact with these tools(ie Start/stop button, pause, take a snapshot button, choose data button, reading data button).
6. Press CAPS+DOWN ARROW to navigate these buttons
"

Actual result:
"The VoiceOver is not announcing the corresponding name of the buttons, its only announcing as ""button""
For example: For the start/stop button , VoiceOver is announcing as ""Button"" without any name."


Expected result:
The VoiceOver should announce the corresponding name of the buttons of Toolbar


User impact:
The Screen Reader user won't able to perform the proper action(like stop/start etc.) until the name of the button has not been announced.
Comment 1 xamarin-release-manager 2017-07-18 09:34:07 UTC
Fixed in version 1.5.7.42 (master)

Author: Jose Medrano
Commit: dbeab42b5dad701e2f03ed2e9873266eb5484799 (xamarin/profiler)
Comment 3 Ramya Sri Narasinga 2017-08-01 09:21:44 UTC
Created attachment 23932 [details]
Issue fixed

Verified issue on 1.5.6-27 version, issue got fixed. Hence closing this bug.

Thank you.