v11.6.0
In this release, we’ve extended editing and layout controls for DOCX Editor and Spreadsheet Editor, both add-ons to the Web SDK, bringing more sophisticated formatting, styling, and cell-level control into a single, browser-based experience. It’s a step forward in keeping users focused and productive within your application.
Our modular UI now meets WCAG 2.2 AA standards across WebViewer, DOCX Editor, and Spreadsheet Editor. This ensures your applications are accessible to users with motor or visual impairments, without requiring additional development effort.
The Spreadsheet Editor interface uses an Excel-like layout users are used to seeing so it’s intuitive and easy to use. Building on our View Mode launch, Spreadsheet Editor now has edit mode functionality users can use for:
Spreadsheet Editor is available as an add-on to the Web SDK.
Editing capabilities in Spreadsheet Editor reduce reliance on third-party systems, multiple vendors, and file downloads for everyday spreadsheet tasks without compromising control, compliance, or security. Teams can format and calculate spreadsheet data directly all with a similar look and feel to how they manipulate PDFs and DOCX files.
See the following new documentation for developing these features:
DOCX Editor now has a new layout tab users can use for:
Now, you can make more complex documents that jump from one section to the next with different layouts. DOCX Editor preserves text flow and section logic to ensure documents remain true to their original form, no matter how complex the layout.
DOCX Editor is available as an add-on to the Web SDK.
The benefits of margin and column editing include:
DOCX Editor eliminates dependency on using other apps and file downloads without compromising security, control, or compliance. Companies can format and write directly within the same interface they’re already using for PDF files.
Our modular UI now meets WCAG 2.2 AA standards across WebViewer PDF Editor, DOCX Editor, and Spreadsheet Editor which ensures your applications are accessible to those with motor impairments, visual limitations, or cognitive disabilities without requiring additional development effort.
Here’s everything you get for a consistent, accessible UI with default behavior that enables developers to embed accessible in-browser document experiences without needing to build a custom solution from scratch:
Accessibility Category | Apryse Product Feature |
---|---|
Visual Accessibility | High Contrast Ratios: Text and UI meet or exceed 4.5:2 contrast ratios. Screen Reader Compatibility: NVDA, VoiceOver, and JAWS supported with ARIA labels and semantic structure. |
Motor Accessibility | Full Keyboard Navigation: From UI interactions to page navigation, every action is accessible via keyboard, with logical tab order and visible focus indicators. ARIA Role Support: Interactive UI elements are semantically correct or mapped to appropriate ARIA roles for better operability. |
Cognitive Accessibility | Predictable Layouts and Actions: Toolbar and menu structures remain consistent across sessions. Focus Management: Modals, menus, and form inputs automatically redirect focus, which helps users stay oriented. |
Developer Assistive Tools | Modular UI Framework: Allows teams to customize UI while retaining accessibility. |
On June 28, 2025, The European Accessibility Act made effective the requirement that digital products and services comply with WCAG 2.1 AA standards for certain industries. Our accessibility update exceeds the WCAG 2.1 AA baseline.
We recommend that customers review their usage of our Web SDK solutions to ensure that their own applications remain compliant. Product and accessibility teams should test against the updated criteria and are encouraged to contact us with any questions or concerns.
See our latest Changelog for more WebViewer release information, including bug fixes.
Did you find this helpful?
Trial setup questions?
Ask experts on DiscordNeed other help?
Contact SupportPricing or product questions?
Contact Sales