Web Interactive ease of use guidelines

1. Input control automatic focus and available keyboard switching input focus

Use JavaScript to implement automatic Spotlight (focus) to the first input control immediately after the page load completes. Use the TAB key (ie default implementation) or the direction key switch to focus on the next input control.

2. Can be submitted with enter (or ctrl+enter) key to ensure that the effect of clicking the Submit button is the same

Do not include JavaScript code such as onclick= "..." on the Submit button.

3. Mouse action prompts and responses

The user's mouse positioning operation, when moved to a responsive position, should be given visual or auditory cues.

4. Validate input data as early as possible at the client

The validation of the input data should be validated on the client using JavaScript. Validation work should be done as early as possible unless validation is done on the server side only.

5. Decide whether to use the intermediate transition page between the form page and the page after submission, depending on the application scenario

Depending on the scenario, decide whether to display the Receive form page (the form page and return the intermediate transition page between the pages), and how to display the Receive form page.

6. Prevent forms from being repeatedly submitted for processing

After clicking on the Submit button, do the gray processing to avoid the user submitting the same form repeatedly when the network response is slow. Use page expiration to prevent users from browsing back and repeating submitting forms.

7. Page link is the principle of opening a new window, using the original window or a pop-up window

In general, links on the home page can use the target= "_blank" property to open a new window, and links on other pages should use the original window or pop-up window. If the linked page content is not important relative to the original page, it is attached, and you can use the pop-up window.

8. Arrange as few options as possible and schedule as few steps as you can

Arrange as few Action menu options as possible according to the user's operating habits, while ensuring as few procedures as possible.

9. No loopholes in operation logic to ensure data is safe to operate

The logical relationship between multiple pages and multiple operations on the same page is designed to be safe and rigorous. Guarantees that no combinations of user actions are not allowed, or at least not because of improper actions by the user.