Guidelines for buttons (Windows Store apps)
Follow these guidelines for adding a button to your Windows Store app.
A button lets the user initiate an immediate action, such as submitting a form.
Don't use a button when the action is to navigate to another page; use a link instead.
Exception: For wizard navigation, use buttons labeled "Back" and "Next". For other types of backwards navigation or navigation to an upper level, use a button with the
Send a user input to a server or perform an action, such as saving form data and going to the next app page.
Clear a form or page of user input.
Create a customized command or action.
|Do||Use a concise, specific, self-explanatory text that clearly describes the action that the button performs.|
|Use text or images to make it clear what happens when button and submit are tapped or clicked.|
|When using AJAX to submit a form, use submit and override the form submit function so users can commit by pressing the enter key regardless of where the focus is in the form.|
|Don't||Don't change button text unless for localization.|
|Don't swap the default submit, reset, and button styles.|
|Don't put too much content inside a button. Although it can contain almost any other HTML element, such as tables and check boxes, too much content will confuse users. Make the content concise and easy to understand (nothing more than a picture and some text).|
- Guidelines for buttons
- Guidelines for radio buttons
- Guidelines for the select control
- Guidelines for toggle switches
- Guidelines for checkboxes