Need More Info
Last Updated: 20 May 2026 14:19 by ADMIN
Test Environment:
OS: Windows 11 Version 25H2 (OS Build 26200.8390)
Browsers: Edge (Version 148.0.3967.70), Chrome (Version 148.0.7778.168)
Screen Reader: NVDA (2026.1), JAWS (2026.2603.86), Narrator

User Impact:
Screen reader users are getting impacted because the focus moves in an unexpected order after activating the combo box. This makes it hard to understand where they are on the screen and can cause confusion while navigating.

Pre-Requisites:
  1. Connect to 'MSFT AzVPN-Manual' VPN.
  2. Turn on Screen Readers:
    NVDA: Ctrl + Alt + N
    JAWS: Ctrl + Alt + J
    Narrator: Ctrl + win + Enter 
  3. Verbosity:
    NVDA: Default
    JAWS: Beginner, Highest
    Narrator: Default

Repro Steps:
  1. Open the URL: https://agoradev-ppe.azurewebsites.net/home?dashboard-id=RnRToolsHomePage in edge/chrome browser in windows.
  2. Agora Home page will open.
  3. Press tab key to navigate to the 'Save As' control and activate it.
  4. 'Save As' dialog will open.
  5. Press tab key to reach to the 'Save to workspace' combo box and activate it using enter key.
  6. Verify whether screen reader focus order is incorrect after activating the 'Workspace to be Saved As in' combo box or not.

Actual Result:
After activating the “Workspace to be Saved As in” combo box, keyboard focus moves to the search edit field, while the screen reader focus shifts to the /user control, causing a mismatch in focus.

Refer Attachment:
  1. Screen Reader focus order is incorrect after activating the 'Save to workspace' combo box in windows.png
  2. Screen Reader focus order is incorrect after activating the 'Save to workspace' combo box in windows.mp4

Expected Result:
After activating the combo box, both keyboard focus and screen reader focus should remain in sync and move to the search edit field in a proper sequence.
Need More Info
Last Updated: 20 May 2026 14:18 by ADMIN
Test Environment:
OS: Windows 11 Version 25H2 (OS Build 26200.8039)
Browser: Edge (Version 146.0.3856.84), Chrome (Version 146.0.7680.165)
Screen Reader: NVDA (2025.3.3), JAWS (2026.2603.86), Narrator

User Impact:
Screen reader users are getting impacted as they are unable to hear the names of the colors available in the Font Color dropdown, making it difficult for them to select the desired color independently.

Pre-Requisites:
  1. Connect to 'MSFT AzVPN-Manual' VPN.
  2. Turn on Screen Readers:
    NVDA: Ctrl + Alt + N
    JAWS: Ctrl + Alt + J
    Narrator: Ctrl + win + Enter 
  3. Verbosity:
    NVDA: Default
    JAWS: Beginner, Highest
    Narrator: Default

Repro Steps:
  1. Open the URL: https://agoradev-ppe.azurewebsites.net/home?dashboard-id=RnRToolsHomePage in edge/chrome browser in windows.
  2. Agora Home page will open.
  3. Press tab key to navigate to the 'Add a widget' control and activate it.
  4. Press tab key to navigate to the 'Table' control and activate it.
  5. 'Create Table' dialog will open.
  6. Press tab key to reach to the 'Font' dropdown control and activate it using enter key.
  7. Font color options will appear.
  8. Verify whether screen reader announces the name for the colors Present in Font dropdown control in windows or not.

Actual Result:
Screen reader does not announce the name for the colors Present in Font dropdown control in windows.
Screen Reader announces as '#ffffff row 1 column 1'

Refer Attachment:
  1. Screen reader does not announce the name for the colors Present in Font dropdown control in windows.png
  2. Screen reader does not announce the name for the colors Present in Font dropdown control in windows.mp4

Expected Result:
Screen reader should announce the name for the colors Present in Font dropdown control in windows.
Screen Reader announces as '#ffffff row 1 column 1 White'
Need More Info
Last Updated: 21 Nov 2025 13:08 by ADMIN
Created by: Andrei
Comments: 10
Category: KendoReact
Type: Bug Report
0
We use "@progress/kendo-react-treelist": "^5.10.1" in our project. Trees are usually placed in flexible containers, and users can reduce their size to 0. At this point, we get an error when calling the tableRowsVirtualization function. I have attached a screenshot at the moment of debugging. You can see that the values of items[0] and lastItem are undefined when the container size approaches 0. I didn't prepare an example to reproduce the error, because I think it's pretty clear that an error occurs here. So the questions are: if this is a bug, is it fixed in the new versions of the package? If there is a possible error on our part or it has not been fixed in the new versions, then what should we do to solve the problem? Thanks
Need More Info
Last Updated: 30 Oct 2025 10:43 by ADMIN
Title, requests formed by the component are sent out with empty payload.