I had a request to change the filtering of a certain column from "Starts With" to use a multi-select checkbox type filter to facilitate selecting 5-10 random items. Then of course some other users prefer the "Starts With" type of filtering. My solution is to have dual columns for that particular field, one with each filter type.
Since my grids save user preferences in local storage between sessions, the users can hide whichever column has the filtering they don't prefer and just use the other one. When they reload the page, their choice of column persists and their filtering is how they like it.
Darron
Hello Community
I'm currently facing an issue with utilizing PostgreSQL stored procedures and select queries in my reports when attempting to use dynamic parameterized input. Despite various attempts, I haven't been able to achieve the desired outcome.
Specifically, I am encountering challenges when trying to incorporate dynamic parameters into my stored procedures or select queries for report generation. The reports seem to be unable to properly handle dynamic input, and I'm struggling to identify the root cause of the problem.
If anyone has experience or insights into efficiently using dynamic parameterized input with PostgreSQL stored procedures or select queries for reports, I would greatly appreciate your guidance. Additionally, any examples or best practices related to this issue would be invaluable.
Thank you in advance for your time and assistance.
Focus order is inappropriate after Edit column settings popup is collapsed as focus moves from top of the page
observation:
When Edit column settings popup is collapsed, focus is expected to observed on the triggered respective ‘Edit column settings’ control and on next ‘Tab’ navigation, focus should move to the next control present after ‘Edit column settings’ control
1.Filter buttons present in the table are accessible through keyboard when we press ALT+down arrow but when we try to open filter, respective column header filter is not opening
2.Focus is not retaining back on the filter button after closing the Filter dialog using Esc key.
NVDA Screen reader is not announcing the sorting information for the table headers.
Observations
3. After invoking the table column headers, screen reader should announce the sorting ascending or descending information.
NVDA is identifying single table as two tables, while navigating using table shortcut key (T).
Observation:
1. Row data cells are not associated with the table column headers.
2.While navigating using table shortcut key ‘T’ in browse mode, NVDA is announcing as ‘clickable table with 1 rows and 15 columns row 1 column 1 Actions’, and using T key again, Screen reader announces ‘table clickable with 20 rows and 15 columns row 1 column 1 info button’.
3. Implementation of table is inappropriate where the tab focus is moving to all the controls in the table.
When using the kendo grid, it is considering the header as one table and data part as another table.
Hence need Resolution for considering the whole grid as one table
Kendo UI Grid Accessibility Issue
1.Kendo UI Grid is dividing Header and Content part into two different tables due to which when focus is on the data present in the table, screen readers are not linking them to the row/column headers.
2. While using tab key for navigating the Kendo grid,
2.1 focus is going again to the checkboxes after the last record in the kendo grid .
2.2 .when focus is on Column 10 , it is narrating the rest of the columns present in the Kendo grid. (Attached a pic for your reference)
Kendo Version: v2020.2.513