> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/flows/showing-input-error.md).

# Showing input error 🚨

Users mistype all the time - whether it's a finger slipping or rushing through letters, errors happen. So for an everyday occurrence, solving an error should be obvious and seamless.

* [ ] Keep the input in default state

  The text field should be checked for errors only after the information has been entered.
* [ ] Allow user to enter information

  Let the user type without interruptions and submit the information aka don't assess as changes are made.
* [ ] Signal error after loss of focus

  After the input has lost focus (user has clicked another element), the field should be assessed. Looks like we have an error here!

  In this case, explain why the error happened, and what is required to resolve it. For accessibility, combine the text with a visual icon that indicates an error was found.
* [ ] Return to default state upon reattempt

  Once the user focuses on the field again, the error message should disappear. If there is an error again, the process will simply repeat until they are able to continue.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/flows/showing-input-error.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.