4.9.3
Core Forms 4.9.3 fixes wrapper-class data loss and redundant ARIA requirements, and improves the Support Request template with preconfigured email actions.
Improved
- The Support Request template now includes an optional Site URL, category, priority, subject, and a six-row issue description, with an admin notification and submitter auto-responder configured using the site’s email address.
- Applying a template inside the visual builder now saves its action and message presets through both Save fields and Save Form.
Fixed
- Classes and supported attributes on individual p/div/span field wrappers survive Code/Visual conversions without turning the wrapper into a container or hiding its input. Wrapper attributes remain separate from input attributes.
- Recover the specific saved wrapper/container name collision produced by 4.9.2 when the original input is still present in the schema.
- Native required fields no longer trigger a missing aria-required warning. Frontend enhancement, accessibility autofix, templates, and the legacy field generator no longer add redundant aria-required attributes alongside required.
- Cached accessibility reports discard the retired warning while retaining other findings. Native required validation and explicitly authored ARIA remain intact.