Gravity Forms 3.0: International phone formats and accessibility by default

We’re excited to announce the release of Gravity Forms 3.0!

3.0 brings international phone formats to the Phone field, giving your users a smoother experience when entering phone numbers no matter where they’re based. Accessible settings are on from day one, so you can build inclusive forms right out of the box. We’ve also added full Block API v3 support and a number of developer improvements to make building on Gravity Forms faster and easier.

A big thank you to everyone who tested the beta and release candidate and shared feedback. Your input helped us polish this release, and we’re delighted to now make it available to everyone.

Watch the video and read on to find out what’s new in Gravity Forms 3.0, and how to update today…

International phone formats: Build better forms for a global audience

The Phone field now offers full support for international phone formats, helping you create better experiences for users around the world.

You can set a default country for the field, allow users to select their country by name or country code, and rely on built-in validation to ensure the number is accurate and correctly formatted for the country in question.

The international format has also been built with accessibility in mind:

• Visible sub-labels: The country selector and phone input now display clear sub-labels, so users know exactly what each part of the field is for. You can customize these in the form editor under the field’s General Settings.
• Semantic structure: The field uses a fieldset wrapper with a legend for the label, providing better structure for screen readers and other assistive technologies.
• Accessible country search: When users search for a country in the dropdown, a live region announces the number of results found, helping screen reader users move through the list efficiently.

If you’re collecting inquiries from across the globe, the new Phone field gives your users a smoother, more intuitive experience, and helps you capture accurate numbers, wherever they’re based.

For more information on international phone formats, check out the documentation.

Accessibility by default: Inclusive forms, right out of the box

Building WCAG 2.1 AA-compliant forms just got easier!

With Gravity Forms 3.0, accessible settings are now enabled by default for every new form you create, no extra configuration required. This reduces manual setup and helps you avoid inadvertent mistakes when working towards WCAG 2.1 AA standards.

The datepicker has had an upgrade, too. The Date field now uses the WhatSock library in place of jQuery UI, delivering fully accessible date selection, with improved keyboard navigation and screen reader support, and no jQuery dependency.

Form submit buttons also now use semantic <button> elements instead of <input> elements, creating more consistent, accessible button markup across your forms and giving you greater styling flexibility.

And to make consistent layouts easier, the Checkbox, Radio, and Multiple Choice fields now share a single Choice Alignment setting. Display choices vertically, horizontally, or in columns, all controlled from the same place across every choice-based field.

For more information on accessibility and WCAG improvements, check out the documentation.

Block API v3: A smoother block editor experience

Gravity Forms 3.0 adds full support for the WordPress Block API v3, allowing blocks to be registered using block.json version 3.

The result is better compatibility with current themes and tools, and a smoother experience embedding and styling your forms inside the block editor.

Developer features: Easier to build on than ever

As well as the features above, 3.0 includes a number of improvements aimed at developers, helping to make Gravity Forms easier to build on.

• Modern input masking: The jQuery-dependent jquery.maskedinput.js library has been replaced with imaskjs, a vanilla JavaScript solution that loads asynchronously and improves the accessibility of input masks.
• Updated JavaScript libraries: The libraries powering formatted inputs and character counts have been updated for a more modern experience.

New filters and hooks

3.0 also introduces several new filters and hooks for greater customization and control over form behavior:

• The gform-phone-countries filter lets you customize the list of countries displayed in the international phone field.
• The gform_state_pre_encode action hook allows you to add values to the form state before it is encoded.
• The gform_text_counter_template filter allows developers to modify the text counter template string (replacing gform_counter_script, which is no longer supported).
• The gform-form_editor-initialized event is triggered after the form editor has been initialized, allowing developers to perform actions once the editor is ready.
• The gform-datepicker-pre_init filter can be used to modify the options used to initialize a field’s datepicker before it is rendered (replacing gform_datepicker_options_pre_init, which is no longer supported).

Check out our documentation for more information on the key features of Gravity Forms 3.0.

Update to Gravity Forms 3.0

Gravity Forms 3.0 is available now to all customers with an active license, and is being released through a staggered rollout to help ensure a smooth update experience for all customers. During the rollout period, the update will gradually become available to licensed sites through your WordPress dashboard.

It’s important to note that the Gravity Forms plugin does not auto-update for major releases. Once the update becomes available, simply navigate to the Plugins page within your WordPress Admin, scroll down to Gravity Forms and select Update Now.

You can also download the latest version from within your Gravity Forms Account.

New to Gravity Forms? Head over to our pricing page to get started, or test drive Gravity Forms with our free demo to see it in action.

Note: Caching and script optimization plugins or services can sometimes affect form functionality after an update. We recommend clearing your website, CDN, and browser caches once Gravity Forms 3.0 has been installed.

If you have any questions about Gravity Forms 3.0 or the staggered release process, our Support team is happy to help.

Gravity Forms 3.0 changelog

• Added security enhancements.
• Added a new international variant of the Phone Field.
• Added multiple accessibility improvements to the dashboard.
• Added imaskjs to replace the old jQuery based input mask library for US phone fields and text fields with input mask.
• Added improvements to the honeypot feature.
• Added new gform_text_counter_template filter so that the text counter format can be customized.
• Added several merge tag modifiers for the repeater field: :count to get the number of repeats; :text to get the value without HTML markup; :field_ids= to get only the values of the specified field IDs (separate multiple IDs with a |); and :value to get only the value with no label or HTML markup.
• Added textareaHeight setting to the Paragraph Field and usage notice to all Field Size settings.
• Added total field validation for existing fields.
• Added the gform_state_pre_encode hook, so that add-ons can add additional non-field values to the state before it is encoded.
• Added the gform_enable_repeater_field_button filter to allow enabling the beta Repeater field.
• Added additional logging details to the processing of gf-download links.
• Updated many default form and field settings to be accessible by default on new forms.
• Updated drop-zones in the form editor to indicate when a field cannot be dropped in a specific location.
• Updated form buttons to use elements instead of elements for better accessibility and styling flexibility. It is no longer necessary to use the gform_submit_button filter to change the submit input into a button, and use of that filter might cause unexpected issues.
• Updated form theme/frontend based scripts to load on block editor pages.
• Updated the layout editor so that it doesn’t use jQuery UI libraries.
• Updated Save and Continue to use GFFormDisplay::validate_field() with a $context of send-link-submit to validate the send link email field, so the gform_email_field_rejectable_values and gform_field_validation filters are triggered.
• Updated state validation to support additional field types, including fields added by add-ons that extend the GF_Field class.
• Updated the appearance of the Repeater field in the form editor, the frontend, Entry Details page, and in the {all_fields} merge tag output.
• Updated the Dashboard Widget setting to be off by default.
• Updated the datepicker field to use a new datepicker library that is fully accessible and does not rely on jQuery.
• Updated the form submission spinner to display inside the submit button instead of next to it.
• Updated the Gravity Forms block to use the Block API version 3.
• Updated the settings for the Radio, Checkbox, and Multiple Choice fields so that they all have the same settings for displaying vertically, horizontally, and in columns.
• Updated the accessibility settings for the Submit and Page Navigation buttons when the button type is set to Image.
• Updated the location and naming of the Choice Layout settings for the Radio, Checkbox, and Multiple Choice fields.
• Updated the accepted files filter for the Import Forms upload input to .json files.
• Updated the name of the “Field Size” setting to “Field Height” for the Paragraph, Post Body, Post Excerpt, and Post Custom Field fields.
• Updated the browser log so that it doesn’t contain the characters -->, which can trigger WAF rules and cause form submissions to be rejected.
• Updated the validation used by the Submission Speed Check.
• Fixed several bugs with the beta Repeater field.
• Fixed a JavaScript error that occurs when editing a page with an embedded form that includes a multi-file upload field.
• Fixed an issue where empty required fields can be submitted if the value is sanitized.
• Fixed an issue where some fields are displayed incorrectly on block editor pages.
• Fixed an issue with the consent field description spacing in the Orbital Theme.
• Fixed an issue with the consent field for the field required indicator and description spacing and placement in the Gravity Forms 2.5 Theme.
• Fixed an issue with the required field indicator placement and spacing in the Orbital Theme.
• Fixed an issue with the notifications list and edit pages where you can’t see that a notification is assigned to an event that is missing.
• Fixed deprecation notices on MySQL 8.0 caused by the use of the deprecated SQL_CALC_FOUND_ROWS modifier.
• Fixed an issue where false is output in the gf_global.number_formats variable instead of the selected format when the number field visibility is set to administrative and dynamic population is enabled. Developers: use $field->set_context_property( 'adminonly_hidden', true ) instead of $field->inputType = 'adminonly_hidden'.
• Fixed a fatal error when the $text value passed to GFCommon::replace_variables() is not a string.
• Fixed an issue that causes the Submit button to lose its appearance settings when it is set to display inline and another field is added to the end of the form.
• Fixed an issue that can cause PHP warnings with PHP 8.1+ when a color selected in the Form block settings is a CSS variable defined in theme.json.
• Fixed an issue where the reCAPTCHA v2 Invisible field label is displayed, or space is reserved for it, when no label is provided.
• Fixed an issue where multiple forms with an inline submit button embedded on the same page output a duplicate element ID for the submit button container.
• Fixed an issue where the user selection dropdown doesn’t display all users.
• Fixed an issue where an administrative List field with dynamic population enabled causes a fatal error when the form is submitted or the entry is viewed.
• Fixed an issue where the dropdown caret on the Settings page overlaps the text in RTL languages instead of appearing on the leading (left) side.
• Fixed an issue where the Personal Data page doesn’t display a Gravity Forms alert when the form doesn’t contain an Email field.
• Removed the gform_ajax_spinner_url and gform_spinner_url filters. You can use CSS to replace the default spinner.
• Removed the gform_always_show_spinner filter. You can use CSS to hide the spinner.
• Removed the form button section from the form settings page.
• Removed the gform_price_change JQuery event.
• Removed the Preview toggle in the block editor.
• Removed “display grid” and “show structure” from the form preview
• Removed reCAPTCHA from the Global Settings page when no site key or secret key is configured.
• API: Added get_value_save_input() to replace the deprecated functions get_value_save_entry() and GFFormsModel::prepare_value().
• API: Added a conditional_descriptions property to the setting field class that can be used to conditionally display descriptions based on the field’s value.

Newsletter

If you want to keep up-to-date with what’s happening on the blog sign up for the Gravity Forms newsletter!

"*" indicates required fields

Facebook

This field is for validation purposes and should be left unchanged.

Email*

Enter Email Confirm Email

Privacy*

I agree with the storage and handling of my data by this website. – Privacy Policy *

CAPTCHA