The page should allow you to use the menu, forms and buttons without mouse. It is worth taking this method of handling into the project and then check the full tasks of the user.
Design the road between elements
Keyboard support helps people who cannot or do not want to use the mouse. W3C indicates the need for this function to be accessible by this path and the logical order of transition between elements. Explains this WAI material on keyboard compatibility.
It is therefore worth taking into account not only the condition after the cursor has invaded, but also the visible selection of the active element. The user must know where it is located.
Check the most important path
Go from menu to selected service, open the form, complete the data and correct the error. Note whether the order is understood and whether you need to pass multiple times through unnecessary items.
Do not test only the first button. The problem may not be revealed until you have opened the drop-down menu, selected the filter or a message appears.
Predict opening and closing of layers
- After opening the window, the user should understand how to use it.
- The method of closure must be attainable without the mouse.
- After closing, it is worth keeping a logical return to the earlier place.
- Automatic change of content should not take control of the task.
This behavior should be determined with the person implementing the interaction. The button color model itself does not describe the entire process.
Maintain a common style
The visible selection may match the company identification. It does not need to be removed to make the interface look aesthetic. It is important that it remains recognizable on different backgrounds and when the text is enlarged.
We write about consistent elements of the service in library guide for componentsChecking the keyboard is an important part of the reception, although in itself it does not constitute a full audit of the availability of the entire page.
