UI for ASP.NET AJAX
The Telerik UI for ASP.NET AJAX PDFViewer control enables the end-users to review PDF files directly in the browser without the need to download it first. The RadPDFViewer control is a server-side Web Forms wrapper over the PDFViewer for Kendo UI for jQuery widget. With responsive rendering the PDF Viewer will provide print and download functionality, built-in accessible and localized toolbar, and various configuration settings.
The RadPDFViewer component provides responsive and adaptive rendering capabilities out of the box. This means that the control is equally suitable and operational on both the desktop and mobile browsers. With responsive rendering the PDF Viewer will provide print and save functionality, built-in accessible and localized toolbar, and various configuration settings.
The PDFViewer has an inbuild Toolbar to compliment the control by conveniently exposing the variety of features. With a single line of code, you get all the UI expected from a standard PDF viewing application, including page navigation, zoom and page control, open/download/print buttons. When updating from version to version, you'll automatically get UI for all the new commands we expose. Here is the full list of toolbar options:
The inbuild Virtualization in the PDF Viewer allows large files to be you to upload and render to enable previewing and navigating within them. This is also covered by the smooth scrolling offered by this feature.
The available 21 beautiful skins should be a perfect match for the design of your apps. If you need to customize them, this should be an easy task since they are based on HTML5 and CSS3 only.
A critical requirement for software accessibility is keyboard support as a complete alternative to pointing devices (mouse, etc.). Keyboard support is comprised of command key, focus key, and keyboard navigation. The PDFViewer seamlessly switches between mouse and keyboard navigation.
Our goal is to have all of our components be WCAG compliant. The Telerik UI for ASP.NET AJAX PDFViewer component satisfies the requirements of Section 508 and WCAG 2.1 for software accessibility.
To get more familiar with accessibility and its importance, check out our whitepaper focused on the topic to learn how accessibility affects your applications.