Hello,
We are currently developing an application based on Kendo React components.
We are wondering if the React-Gantt chart has the functionality to edit the data by drag-n-drop the same way it possible with JQuery-Gantt (see attachment).
Thanks in advance for your help.
Kind regards,
Sergei
MaterialUI exposes a `ListBoxComponent` prop on their dropdown components (https://material-ui.com/api/autocomplete/) it would be nice to have that exposed on the kendo multiselect as well.
Use cases include:
- simplifying styling
- Custom scroll bars for the dropdown
- Open the https://answers.microsoft.com/en-us/msoffice/ using valid credentials.
- open any related article.
- Navigate to 'Reply' button and invoke it.
- Navigate to 'ordered list' button and invoke it.
- Navigate to the edit region and type some ordered list items.
- Now, Navigate to the ordered list items and listen to Narrator announcement.
Actual Result:
On navigating to ordered list items with arrow keys, Narrator is only announcing first letters of the text and while navigating with 'caps-arrow' keys, Narrator is only announcing position details of the list items.
Note: this issue is not observed with nvda
Nvda version: 2020.2
Expected
On navigating to ordered list items with 'arrow keys' or using 'caps-arrow' keys, Narrator should announce the whole text of the list item including position details.
User Impact
Knowing how many items are in a list is extremely useful to assistive technology users as they can know if they should attempt to skip the list, navigate to the end, help them recall placement of certain items, or orient themselves within the list.
Click icon to close as well as open
Hi,
I'm trying to validate the file names that are being
uploaded using Kendo react Upload component. But the validation message I
set is not displaying next to the file just the way the following
messages are displayed.
File type not allowed.
Invalid file(s). Please check file upload requirements.
File size too large.
File size too small.
For reproducing the steps here is the code pen. If you try to upload any file which contains 2019 should show the validation error message.
https://stackblitz.com/edit/react-3x6dal-p7uycz?file=app/main.js
Could you please consider this request as a new feature?
- open the https://answers.microsoft.com/en-us/msoffice/ using valid credentials.
- Select 'reply' button.
- Navigate to 'Insert image' button and invoke it.
- Now Run the fast pass using Accessibility Insights for web and observe the failure 'label'.
Actual results:
Aria label attribute is not defined for button in 'Insert image' dialogue.
Narrator is announcing as 'No file chosen, choose file, button'.
Expected results:
Aria label attribute should be defined for button in 'Insert image' dialogue.
User Impact:
Adding effective form labels is absolutely necessary to make forms accessible. The purpose of form elements such as a checkboxes, radio buttons, input fields, etc. is often clear for sighted users, even if the form element is not programmatically labeled. This isn't usually the case for screen reader users. Adding a label to all form elements eliminates ambiguity and contributes to a more accessible product.
- open the given URL using valid credentials.
- Navigate to 'Reply' button and invoke it.
- Navigate to 'Insert image' button and invoke it.
- Now Run the fast pass using Accessibility Insights for web and observe the failure 'Nested- interactive'.
Actual results:
Expected results:
Interactive control elements have focusable descendants.
User Impact:
When interactive elements have an incorrect name and role, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content. Knowing the role for a control helps users know what will happen when that object has focus and is selected, as well as what keyboard shortcuts to use when interacting with the control.
We have two issues with grid with virtual scroll.
Both are registered on github.
First one is really blocking us: https://github.com/telerik/kendo-react/issues/1010
Second one we found on Safari, it's also very critical for our customers: https://github.com/telerik/kendo-react/issues/1013
Version: 4.7.0. Please note that version specified in Additional information does not make sense as we use Kendo React not Kendo UI.
Can you help us somehow?
Hi Team,
I'm facing below issue when manually enter the value in the datepicker.
Control : DatePicker
<DatePicker defaultValue={value} format="dd/MM/yyyy" />
Step 1: Manually I'm trying to enter the data as 01/01/2021 and clicked outside the datepicker control ( now the focus is out of the datepicker ).
Step 2: Now try to change the date (day) by entering "2". (Our Expectation is system should display the date as 02/01/2021 instead it is appending the date and displaying as 12/01/2021)
Every time system is expecting the user to clear the existing value and then enter the new value.
Can you take this as feature request. Value should not get append to existing value. It should overwrite.
Reference Ticket URL : https://www.telerik.com/forums/datepicker-when-user-enter-the-date-manually-the-value-getting-appended-with-the-previous-value
If this is taken as feature request when will it get delivered.
The ListView component has an item prop that allows you to specify the render component. That component receives ListViewItemProps. The ListViewItemProps type is not exported and cannot be properly imported elsewhere.
Looking for callback for what item was dragged or resized.
coz we have as well Charts(HighCharts) inside not automatically resizing and we need to determine what item was resized to be able to trigger charts inside to redraw.
https://github.com/telerik/kendo-react/issues/865
This could be done as a demo, that showcases how this functionality can be added and extended for more elements.
- open the given URL using valid credentials.
- Navigate to 'Reply' button and invoke it.
- Navigate to 'table' button and invoke it.
- Now, try to navigate to table cells to select the size of the table and observe
Actual Result:
After invoking 'table' button, user is unable to select the size of the table i.e, Keyboard focus is not going to 'Insert row and column cell components.
Tab index property is not defined.
Expected
Control(s) must be accessible to keyboards and other assistive technology. Common causes of this problem include a) the element does not have a proper role assigned, b) the element needs tab-index="0" attribute to be focusable, or c) the component is not registering keypresses.
User should be able to navigate to insert row and column cell components to select the size of the table.
User Impact
When interactive components are not accessible, assistive technology users are blocked, which leads to everything from inaccessible content, features, and functionality, up to entire applications or sites.
- open the given URL using valid credentials.
- Navigate to 'Reply' button and invoke it.
- Navigate to 'insert image' button and invoke it.
- Now, try to upload the image and observe
Actual Result:
User is unable to navigate to 'upload' button in 'insert image' dialogue. On invoking 'insert image' dialogue focus is navigating in the background and after navigating whole page then focus is going to the 'insert image' dialogue. Now, when user try to upload the image, focus is going out of the dialogue (going to the top of the page).
Expected Result:
When focus order does not follow the visible reading order, the experience can create a different interaction pattern, and/or unintended content relationships for assistive technology users. On rare occasions, there is a logical reason the focus order is different from the reading order, but the meaning of the content and interactions must remain the same.
- open the given URL using valid credentials.
- Navigate to 'Reply' button and invoke it.
- Navigate to 'color group' and invoke it.
- Now, Navigate to the colors in color group and listen to Narrator announcement.
Actual Result:
On navigating to colors, Narrator is staying mute and not announcing anything.
Expected
On navigating to colors, Narrator should announce the name of the color.
When interactive elements have an incorrect name, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content.
- open the given URL using valid credentials.
- Select 'reply' button.
- Now Run the fast pass using Accessibility Insights for web and observe the failure aria required children.
Actual results:
Elements with Aria role is not containing child role with in them.
Expected results:
Elements with Aria role should contain child role with in them.
User Impact:
For each role, WAI-ARIA explicitly defines which child and parent roles are allowable and/or required. ARIA roles missing required child roles will not be able to perform the accessibility functions intended by the developer.
Actual results:
aria-label is not defined for ‘Reply editor’ when the keyboard focus is on 'Reply’ edit box narrator is announcing as “Editing End of line”.
Expected
All components need an accessible name, ideally using semantic elements and attributes. In rare cases, aria-label or aria-labelled by may be needed to alter the name. Learn more by reading about the accessible name property.
User Impact
When interactive elements have an incorrect name, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content.
Hi Team,
we are looking same property in Kendo Tree View React Version.
https://docs.telerik.com/kendo-ui/api/javascript/ui/treeview/configuration/dataspritecssclassfield
could you pls check the feasibility and add the same?
Actual Result:
While navigating in table, Narrator is not announcing as 'enter table' and it is also not announcing rows and column information. while navigating in table, With arrow keys or table navigation keys or tab key, Narrator is announcing as 'end of line/blank'.
With caps-arrow keys, Narrator is giving row and column information.
Expected
While navigating in table, Narrator should announce as enter table and it should also give row and column information. And while navigating with arrow keys or table navigation keys or tab key, Narrator should not announce as 'end of line/blank' instead it should give row or column information