Why you should not use the "send" button
When you see the submit button, what comes to mind? Obviously, when you click a button, information will be sent to the system for processing. The “send” button describes the actions of the system well, but does not describe the actions of users at all.
When users fill out a form, they are involved in the task. The action button should confirm this task so that users know exactly what will happen when they click. A button that describes the task informs users that the form is focused on a specific goal. The more understandable your form, the more likely it is to fill it.
A form button that says “send” gives users the impression that the form is not focused on specific tasks. It also gives the impression that your site is not user-friendly, because you speak a technical language that many are not familiar with. If the user has such an impression when filling out the form, then be prepared for the fact that some will not fill it.
Your button should accurately describe what the user is trying to do when performing the task. For example, if it is registered on the site, a button with the caption “Create account” will inform the user that when you click on the button, an account will be created. Understandable and connected with the task. If the button were called “send,” then users would most likely have a question about what would happen when they click this button. This creates a certain level of uncertainty among users, which can easily be avoided by simply using a button that describes the result of a user task.
')
Although the problem with the “send” buttons is not so acute, but they all exist today on forms. The good thing is to fix them simply. It does not require more than just renaming a button to reflect specific actions. This may not seem like such a big difference at first glance, but when you notice that the number of users who fill out the form increases, you will understand that clear and task-oriented buttons work best.
When users fill out a form, they are involved in the task. The action button should confirm this task so that users know exactly what will happen when they click. A button that describes the task informs users that the form is focused on a specific goal. The more understandable your form, the more likely it is to fill it.
A form button that says “send” gives users the impression that the form is not focused on specific tasks. It also gives the impression that your site is not user-friendly, because you speak a technical language that many are not familiar with. If the user has such an impression when filling out the form, then be prepared for the fact that some will not fill it.
Your button should accurately describe what the user is trying to do when performing the task. For example, if it is registered on the site, a button with the caption “Create account” will inform the user that when you click on the button, an account will be created. Understandable and connected with the task. If the button were called “send,” then users would most likely have a question about what would happen when they click this button. This creates a certain level of uncertainty among users, which can easily be avoided by simply using a button that describes the result of a user task.
')
Although the problem with the “send” buttons is not so acute, but they all exist today on forms. The good thing is to fix them simply. It does not require more than just renaming a button to reflect specific actions. This may not seem like such a big difference at first glance, but when you notice that the number of users who fill out the form increases, you will understand that clear and task-oriented buttons work best.
Source: https://habr.com/ru/post/111583/
All Articles