Client-Side Custom Field Validation Fails in Universal Login Signup Form Overview
Last Updated:
Overview
This article explains why client-side validation for custom fields may not function as expected in the Universal Login signup form.
Applies To
- Universal Login
- Signup
- Custom Fields
- Validation
Cause
The Universal Login signup form includes the 'novalidate' attribute. This attribute intentionally disables the default HTML5 browser validation to allow for a custom, Web Content Accessibility Guidelines (WCAG) compliant, client-side validation system.
Solution
The use of the 'novalidate' attribute is intentional on Auth0's part and part of a User Interface (UI) update to comply with Web Content Accessibility Guidelines (WCAG).
This change was implemented in early September 2025.
Any issues arising from this behavior are likely due to custom scripts relying on outdated Document Object Model (DOM) structures from the legacy UI.