You may have seen a short HTML attribute change how a field, image, or link behaves. This guide is about Spellcheck Values and Browser Defaults. The spellcheck attribute tells the browser whether it should offer spelling feedback while someone edits text.
The useful question is not simply “Which value should I memorize?” It is “What should people be able to do on this page?” First decide the goal, then choose an HTML value that matches it.
How the values work
| Value | Meaning |
|---|---|
true | Ask the browser to check spelling where supported. |
false | Ask the browser not to check spelling. |
attribute omitted | The browser uses inherited or default behavior; results depend on the control and browser. |
A practical example
<label for="story">Your story</label>
<textarea id="story" name="story" spellcheck="true" rows="4">
I wrote a short storry.
</textarea>
<label for="product-code">Product code</label>
<input id="product-code" name="product-code" spellcheck="false">Understanding the code
Start by finding the attribute in the example. The HTML element tells the browser what kind of thing it is displaying; the attribute supplies an extra instruction or hint about that particular element. If you remove the attribute, the element usually still exists, but one part of its behavior may change.
Spellchecking does not validate whether a value makes sense. It can also be unreliable for names, code, multilingual text, and browser or operating-system settings.
If a file path or form action appears in the code, it is an example project path. Create the matching file or server endpoint before expecting the complete behavior to work. This distinction is important: HTML describes the page, but it does not automatically build a server or create missing resources.
When to use it
Use spellcheck only where its documented behavior helps someone complete a task. Ask whether the choice improves clarity, keyboard access, performance, or correct data collection. If an extra attribute has no clear purpose, leaving it out may be safer than relying on a poorly understood hint.
Try it yourself
Type a deliberate spelling mistake in the textarea, then try spellcheck="false" and compare.
Save the code in a local HTML file, open it in a current browser, and inspect the relevant control or request. When the feature depends on a server, use a small local development server rather than guessing from the source alone.
Common Beginner Mistakes
- Treating a red underline as a form validation error.
- Assuming every browser provides identical controls or follows a hint in exactly the same way.
- Copying a demonstration without providing the files or server behavior it expects.
Key Takeaways
- This is a writing aid, not a security or data-validation feature.
- Choose the value based on what the visitor needs to do, not only on how the source looks.
- Test the result in the browser, including keyboard access and submitted values where relevant.