Please note the product releases for the environments are scheduled as follows:
U.S. = 7 October, Monday Evening | Canadian = 7 October, Evening
| Australia = 8 October, Tuesday Morning
Enhancements
Credit Card Recovery
You can now enable credit card recovery for standard and membership forms. With this feature, donors can opt to add the credit card processing fees to their donation amount.
Enable credit card recovery
- From a standard or membership form, open Content Properties.
- Select Enable for Optional Fee Recovery.
- To include the credit card recovery option as the last step prior to the billing page of the form, select the option. Otherwise, the recovery option appears at the bottom of the first page, allowing for a shorter and simpler donation form.
- In the Fee Percentage and Fee Amount fields, enter the percentage or flat fee to use for fee calculations. Most institutions enter the transaction fees set by the contract with their gateway.
After the donor enters their donation amount on the form, the calculated fee recovery amount appears on the form.
Accessibility Improvements for Form Controls
Form controls are elements on a form users use to enter information or make selections. Some common examples are buttons, checkboxes, and text fields. To meet WCAG accessibility standards, we made improvements to form controls.
Invalid entry indicator
When a user enters an invalid value in a form control, they receive a visual indicator that they need to fix their entry. Invalid form controls must be communicated programmatically to alert assistive technology users when they enter an invalid value, To address this:
- Aria-Invalid is set to "true" on form fields that contain invalid data. This ensures the control is exposed to assistive technologies as an invalid field. Screen readers will announce this, for example, by announcing "invalid entry" as part of the field description. Once the field is valid, the Aria-Invalid attribute is set to “false.”
Instructions
When instructions for a form control are only provided as text, screen reader users may have difficulty decerning which form control the instructions apply to. Instructions must be programmatically associated with the control. To address this:
- Instructions are now included as part of the <legend>.
Close button
The Close button looked and behaved as a button, but was missing the semantics and behavior for assistive technology to signal to the user they can interact with the control. To address this:
- The control is now set to role="button" on the containing <div> or <span> element.
Resolutions
Functional Area |
Reference |
Description |
Foundations | 2322784 |
Previously, the digital membership card form for lifetime members showed an invalid expiration date. The default value is now “N/A” because lifetime memberships never expire. |
Foundations | 2401716 |
We fixed an issue preventing Optimized Event Reports from downloading.
|
Email marketing | 2422270 |
Reports for email marketing campaigns were excluding clicks for custom URLS with tokens. These are now included as expected. |
Email marketing | 2301190 |
Users can now deactivate sender identities that are no longer tied to any active or pending emails. |
Email marketing | 2445044 |
When creating a commerce form and with the CC Fee Recovery option turned on, some users received an error. This issue is fixed and you can save the form. |
Email marketing | 1779900 |
When an email merge list is selected for an email audience, segments and other email lists can’t be added. Previously, the system would seemingly allow you to add a segment or email list even though the additions wouldn’t apply. This issue is fixed and you can’t make additions to the audience. |