We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on: June 24, 2019).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

sfbutton is not accessibility on android

Thread ID:

Created:

Updated:

Platform:

Replies:

148601 Oct 27,2019 07:30 AM UTC Jan 16,2020 04:38 AM UTC Xamarin.Forms 5
loading
Tags: SfButton
Amer Almadany
Asked On October 27, 2019 07:30 AM UTC

sfButton
on IOS work good but on Android not working 
these problem on your simple on google play and github

and of course I use that property 

AutomationProperties.IsInAccessibleTree="True" 
AutomationId="mytext"
AutomationProperties.HelpText="mytextxxx"

these 
video for explain problem 
https://drive.google.com/file/d/14mLedfLWOhauSg4LVx_yXNTecWTWlvxK/view

Hemalatha Marikumar [Syncfusion]
Replied On October 28, 2019 12:31 PM UTC

Hi Amer, 
 
Greetings from Syncfusion. 
 
Currently we are validating the reported issue at our end and will update the complete details on October 29,2019. 
 
We appreciate your patience until then. 
 
Regards, 
Hemalatha M. 


Saravanan Madheswaran [Syncfusion]
Replied On October 29, 2019 01:15 PM UTC

Hi Amer, 
 
We can able to reproduce the reported issue while using content inside the SfButton. We will validate and update you the more details by tomorrow 30th October 2019.  
 
Regards, 
Saravanan.  
 


Hemalatha Marikumar [Syncfusion]
Replied On October 30, 2019 01:48 PM UTC

Hi Amer, 
  
We can able to reproduce the issue and we confirmed “Accessibility does not work with the Content property of SfButton” as an issue. The fix will be available in our upcoming volume 3 SP1 release, it scheduled to be rolled out in first week of November.  We appreciate your patience until then. 
  
If you have any more specification/precise replication procedure or a scenario to be tested, you can add it as a comment in the portal link above. 
  
 
Regards, 
Hemalatha M. 


Hemalatha Marikumar [Syncfusion]
Replied On November 6, 2019 01:37 PM UTC

Hi Amer, 
 
Sorry for the inconvenience. 
 
Due to some technical hurdle, we were unable to move this fix into our Volume 3 SP1 release. Now the issues are resolved and will move this fix into our upcoming weekly nuget release which is expected to be rolled out on November 12,2019. 
 
Please let us know if you need a patch before the mentioned timeline. 
 
Regards, 
Hemalatha M. 


Lavanya Anaimuthu [Syncfusion]
Replied On January 16, 2020 04:38 AM UTC

Hi Amer, 
 
We are glad to announce that the reported issue has been fixed in our weekly Nuget 17.3.0.30 and it’s also available in our latest version v17.4.0.43.  
 
  
Please check the issue with latest version and let us know if you have any other concern. 
 
Thanks, 
Lavanya A. 


CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

This page will automatically be redirected to the sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

Live Chat Icon For mobile
Live Chat Icon