Completed
Last Updated: 21 Jun 2018 14:41 by ADMIN
ADMIN
Georgi
Created on: 29 Sep 2015 10:39
Category: Menu
Type: Bug Report
2
Menu: Using RadMenu Automation peer leads to Jaws reading only the first letter of GridView cell
Available in LIB version 2017.3.1113, it will be also available in the R1 2018 Release.
6 comments
ADMIN
Kalin
Posted on: 21 Jun 2018 14:41
Hi Ab,

We already started working on corresponding item: https://feedback.telerik.com/Project/143/Feedback/Details/248741-datetimepicker-watermarkcontent-and-selectedvalue-are-not-read-with-jaws-screen

With the latest SP (R2 2018 SP) we've introduce some improvements in the automation of the DateTimePicker - can you please give it a try and share your thoughs for the improved behavior in the item as a comment.

Regards,
Kalin
AB
Posted on: 07 May 2018 20:23
Hello,

I am using datepicker with JAWS.  Here are the issue I ran into:
1. JAWS reads out watermark 3 times
2. JAWS reads out date and time where there is only date populate and dateformat is set for shortdate.  For example, date is "04/12/2018".  JAWS reads "04/12/2018 00:00:00"
3. Once the date is populated and date field got focus, it will read out date and time at least 2 times.

I work on project that required it to compliance with government section 508. This issue will not allow me to use Telerik's datepicker.  Please fix this.

ADMIN
Kalin
Posted on: 06 Mar 2018 14:15
Hi Leo,

The fix is live with the versions after R1 2018. Hope everything works as expected on your side.

Regards,
Kalin
Telerik 
Leo
Posted on: 20 Apr 2017 17:41
Given that this bug was reported more than a year and a half ago, when do you plan on addressing it?
ADMIN
Dilyan Traykov
Posted on: 13 Apr 2017 13:16
I'm afraid we cannot commit to a certain time-frame for this fix as we're currently working on a number of features and bugfixes. You can, however, subscribe to the feedback item in order to get notified once the development team starts working on it.
Leo
Posted on: 12 Apr 2017 18:10
This really, really needs to be fixed.  Why?  The workaround provided (override RadContextMenu and return NULL in the OnCreateAutomationPeer call) prevents screen readers from knowing anything about the context menu.  The user doesn't know that a context menu has been launched - because the menu's automation peer is null.

Can you provide a timeframe for the fix?