Medallia Digital Web 2.38 release notes

System requirements

Digital for Web requirements

  • Digital Command Center browsers: Latest two versions of Google Chrome, Apple Safari, Microsoft Edge, and Mozilla Firefox. Survey management is not supported in Internet Explorer.

Survey-taking requirements

  • Desktop browsers

    • Latest two versions of Google Chrome, Apple Safari, Microsoft Edge, and Mozilla Firefox.

    • Microsoft Windows 10 for Microsoft Internet Explorer 11: latest available consumer build.

    • Other browsers or older versions will likely work; however, Medallia not certify a full experience in browsers older than two years. Any issues will be handled on a best-effort basis.

  • Mobile browsers

    • Google Chrome: latest version

    • Android: latest version

    • Safari for iOS: latest version

  • Network connectivity requirements: Digital surveys require unobstructed network connectivity over an HTTPS connection. If your organization employs a content security policy or any other network filtering method, you may need to allow-list Medallia domains. For more information, refer to allow-list documentation or contact your Digital expert.
  • ADA / WCAG compliance: Digital Web is certified WCAG 2.0 Level AA. For the best survey experience, Medallia recommends the following screen reader and browser combinations:

    • Microsoft Windows: Mozilla Firefox + NVDA; Google Chrome + JAWS; and Internet Explorer 11 + Jaws

    • Apple MacOS: Safari + Voice Over

    • Android: Google Chrome + TapTalk

    • iOS: Safari + Voice Over

    • Safari MacOS users: To enable tabbing in Safari, it is required that the Press tab to highlight each item on a webpage box, located under Safari Preferences - Advanced, is selected.

Highlights

  • Digital now provides the capability to programmatically close the currently displayed survey. For more information, refer to the SDK documentation.

  • Contentsquare integration is now supported natively.

  • Survey infrastructure has been improved to better support the following accessibility use cases:

    • Automatic focus on the lightbox modal once it appears.

    • The lightbox modal will be the first focusable element in cases where the user is tabbing into the browsing window from a different section of the browser, such as the url area or from bookmarks.
      Note: This functionality is not supported by the Android screen reader.

  • It is possible to configure a spinner to be displayed before the survey until all custom CSS and fonts have been rendered. Contact your Medallia to enable this behavior.

  • Companies can now perform the following:

    • Block attempts to publish or save targeting options for forms that are not targeted by any rule.

    • Display a warning before saving any changes to targeting settings for unpublished forms that are not targeted by any rule.

  • The following areas of the Digital Command Center have been improved:

    • Forms view with Folders view enabled or List view

    • Form Localization modal for forms and app ratings

    • Custom parameters table

    • DHH Packages table

    • Icons optimization

    • Folder management

    • Top section dropdown menu

Resolved issues

  • An issue where importing a translation file switched the checkbox and radio button orientation from horizontal to vertical has been resolved. Customers who are currently experiencing this issue will need to change the orientation per their requirement and save the form again.

  • An issue that caused the survey options display order to not persist has been fixed.

  • On IE11, radio buttons are now highlighted on focus as expected.

  • An issue where the "Number of lines" in the "TextArea" component was not being respected in certain configurations has been resolved.

  • In some rare cases, the rating components label appeared to be broken. This issue has been fixed.

  • In cases when the user defines a question label that includes a custom parameter and the custom parameter does not exist or is empty, the default label will be displayed.
    Note: In cases where multiple custom parameters are defined, then it is required to have at least one custom parameter with a value for the label with the custom parameter to appear.