---
title: "Comment by Tiffany Spark on \"How to Fix Form Validation UX: Switching from :invalid to :user-invalid\" | Hashnode"
description: "been doing exactly this on client sites lately, the difference in how forms feel to users is massive. the :user-invalid approach is so much kinder than screamin"
url: "https://hashnode.com/posts/how-to-fix-form-validation-ux-switching-from-invalid-to-user-invalid/699376d10c6be409a83e961f/comment/6994e4846249b2acc7d509f0"
---

[Discussion](https://hashnode.com/posts/how-to-fix-form-validation-ux-switching-from-invalid-to-user-invalid/699376d10c6be409a83e961f)

Comment [How to Fix Form Validation UX: Switching from :invalid to :user-invalid](https://hashnode.com/posts/how-to-fix-form-validation-ux-switching-from-invalid-to-user-invalid/699376d10c6be409a83e961f)

[Tiffany Spark](https://hashnode.com/@markupandmatcha)

[Feb 17](https://hashnode.com/posts/how-to-fix-form-validation-ux-switching-from-invalid-to-user-invalid/699376d10c6be409a83e961f/comment/6994e4846249b2acc7d509f0)

been doing exactly this on client sites lately, the difference in how forms feel to users is massive. the :user-invalid approach is so much kinder than screaming red borders the moment someone clicks into a field.