OS: Windows 11 Version 25H2 (OS Build 26200.8039)
Pre-Requisites:
- Connect to 'MSFT AzVPN-Manual' VPN.
- Turn on Screen Readers:
NVDA: Ctrl + Alt + N
JAWS: Ctrl + Alt + J
Narrator: Ctrl + win + Enter - Verbosity:
NVDA: Default
JAWS: Beginner, Highest
Narrator: Default
- Open the URL: https://agoradev-ppe.azurewebsites.net/home?dashboard-id=RnRToolsHomePage in edge/chrome browser in windows.
- Agora Home page will open.
- Press tab key to navigate to the 'Add a widget' control and activate it.
- Press tab key to navigate to the 'Table' control and activate it.
- 'Create Table' dialog will open.
- Press tab key to reach to the 'Font' dropdown control and activate it using enter key.
- Font color options will appear.
- Verify whether screen reader announces the name for the colors Present in Font dropdown control in windows or not.
Screen reader does not announce the name for the colors Present in Font dropdown control in windows.
- Screen reader does not announce the name for the colors Present in Font dropdown control in windows.png
- Screen reader does not announce the name for the colors Present in Font dropdown control in windows.mp4
Overview:
The KendoReact PDF Viewer renders every page of a document up front. For large PDFs this causes long initial load times and high memory use.
Expose load-on-demand / virtualized page rendering in the React component, matching the existing Kendo UI for Angular PDF Viewer which has:
- loadOnDemand - render pages as the user scrolls
- loadOnDemandPageSize - pages fetched/rendered per batch
Reference: https://www.telerik.com/kendo-angular-ui/components/pdfviewer/load-on-demand
This is a framework-parity gap. The same underlying rendering engine already supports on-demand loading in Angular (and virtualization has been requested for Blazor: httpzor/1594054-pdf-viewer-virtualization). React usershitting large documents currently have no first-party option and must swap to a third-party viewer.
Environment: @progress/kendo-react-pdf-viewer 10.2.0, React 19, Next.js 15.