Approved
Last Updated: 11 Nov 2019 13:58 by ADMIN
Created by: Anna
Comments: 1
Category: Notification
Type: Bug Report
0

I'm testing https://demos.telerik.com/kendo-ui/notification/index with the NVDA screen reader.

1. Notifications are not announced by the screen reader, violating success Criterion 4.1.3.

2. Notifications are not accessible by keyboard.

3. The "close" button is not semantically a button.

4. The "close" button is not focusable by keyboard.

5. Auto-hiding notifications violate the 2.2 guideline (enough time). I can give my user an option to see notifications for a longer time, say 100 seconds instead of 10, but unable to close them by keyboard, they can end up with an overflow of messages.

6. The color contrasts are insufficient (4.26 for the red ones, only 2.73 for the green ones).

Notifications are listed on https://docs.telerik.com/kendo-ui/accessibility/section-508-wcag as AA-level compliant, and while I understand they're one of the hardest component to make accessible due to their asynchronous nature, the current implementation is closer to a bad practices example than a correct solution.

Pending Review
Last Updated: 11 Oct 2019 14:20 by ADMIN
Created by: Anna
Comments: 1
Category: Notification
Type: Bug Report
0

Reproduction

Run dojo at https://dojo.telerik.com/@GaloisGirl/UtuZIyOd

Current behavior

All three notifications are removed after one second

Expected behavior

The blue notification should be removed after 2 seconds, the orange one after 1 second, the red one never.

Analysis

The bug only occurs with the appendTo option.

In the showStatic method, we clearly see all displayed notifications are iterated over and being attached the _hideStatic method. In my example:

  1. the blue notification is shown and scheduled to be hidden after 2s
  2. the red notification is shown, none is scheduler do be hidden, because autoHideAfter is 0
  3. the orange notification is shown, and the blue one, the red one, and the orange one are scheduled to be hidden after 1s.

The 2018.1.117 code does not feature this loop and the bug is not present.