CKTIS / HTML
novalidate — skipping validation during form submission
The boolean `novalidate` attribute on a `form` skips built-in constraint validation during submission. It does not remove field constraints or disable explicit calls to validation methods.
Version: WHATWG HTML Living Standard; index snapshot date recorded separately
Syntax
<form novalidate>...</form>Place novalidate on a form element to skip automatic constraint validation during submission. For example, an empty field with required will then not block form submission.
This is a boolean attribute: its presence matters, not its value text. Valid forms are novalidate, novalidate="", and novalidate="novalidate". Writing novalidate="false" violates boolean-attribute syntax but still enables skipping validation. To restore automatic checking, remove the attribute or set the property form.noValidate = false.
Do not confuse it with formnovalidate: that attribute applies to a particular button or input submit button. In contrast, novalidate on the form applies to submission regardless of which button is used.
Field constraints remain active: checkValidity() still checks validity, and reportValidity() can display problems. Client-side validation does not replace server-side data validation.
In the example, the submit event handler stops actual submission with preventDefault(). Leaving the field empty and clicking Submit shows that the event occurred even though checkValidity() returns false.
Examples
<!doctype html>
<html lang="en">
<meta charset="utf-8">
<title>novalidate demo</title>
<form id="demo" novalidate>
<label>Name: <input name="name" required></label>
<button type="submit">Submit</button>
</form>
<pre id="result"></pre>
<script>
const form = document.getElementById('demo');
const result = document.getElementById('result');
form.addEventListener('submit', (event) => {
event.preventDefault();
result.textContent = `submit event: yes\ncheckValidity(): ${form.checkValidity()}`;
});
</script>
</html>Result
submit event: yes checkValidity(): false
The displayed code and declared result were verified in an isolated environment using the method recorded in the verification evidence for this exact version.