HMHemalatha Marikumar Syncfusion Team October 28, 2019 07:31 AM
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.
SMSaravanan Madheswaran Syncfusion Team October 29, 2019 08:15 AM
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.
HMHemalatha Marikumar Syncfusion Team October 30, 2019 08:48 AM
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.
HMHemalatha Marikumar Syncfusion Team November 6, 2019 08:37 AM
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.
LALavanya Anaimuthu Syncfusion Team January 15, 2020 11:38 PM
We are glad to announce that the reported issue has been fixed in our weekly Nuget 184.108.40.206 and it’s also available in our latest version v220.127.116.11.