Released: May 27, 2025

Updates in v2.1.0

Features

• Form Library Accessibility Now Reaches 100%:
  • SurveyJS Form Library is 100% accessible when using the Contrast theme.
• Populate Existing PDF Forms with Survey Responses:
  • PDF forms often include interactive fields that allow users to fill out the form within their PDF viewer and then save, share, or print it. Starting with v2.1.0, SurveyJS introduces a plugin that enables you to link survey fields to editable fields within a PDF form. Users can enter data through a dynamic SurveyJS interface, and their responses will automatically populate the corresponding fields in the PDF document.
• Survey element titles no longer use HTML heading tags:
  • In previous versions, titles for questions, panels, pages, and the survey itself were rendered using HTML heading tags (<h1>-<h6>). This helped search engines to understand the hierarchy of the survey content. However, it also introduced accessibility issues when heading levels were skipped - for example, <h1> followed directly by <h3> - which violates HTML standards.
  • To prevent accessibility violations and ensure consistent HTML semantics across all environments, survey element titles are now rendered using <div> elements by default.
  • If you want to revert to heading tags or use other HTML elements for titles, configure the titleTags property in global survey settings.

Fixes

• [Safari on iOS] Input Mask: It was impossible to enter certain dates when the mask pattern is yyyy-mm-dd.
• Localization: Incorrect locale code was used for the Ukrainian language.
• [Mobile] Composite Question: Matrices were rendered incorrectly.
• Composite Question: The "Other" value is empty for a Checkboxes question if the storeOthersAsComment property is enabled by default.
• [Survey Creator]: A matrix column remains required after unselecting the Required checkbox if the isRequired property's default value is overridden for the Question class.
• setValueExpression wasn't triggered for the Matrices and Dynamic Panels that weren't rendered yet.
• Switching to the next page in code works incorrectly in question-per-page mode if a time limit is set.