| 5 | | 1. Interaction — mouse and keyboard are two different input methods, and the fundamental interaction design paradigm of the combination of these modalities has at its foundation to have two different highlights to specify focus. Since mouse and keyboard act and move in different ways, we have the ability to target them independently. |
| 6 | | 2. Weight — mouse and keyboard are inherently different. The mouse pointer is often enough to signify where the user is and clicks. As a reference, many desktop UI guidelines don't even provide a hover in many instances, but they ALL provide keyboard navigation. Adding a styling to `hover` is in many instances an extra on top of not really requiring anything, while adding a styling on keyboard is a fundamental requirement, and it has to be evident because the user doesn't know where the focus is going to jump in the next tabulation. |
| 7 | | 3. Standard — the standard provides both independently for independent styling for the reasons above. |
| | 5 | 1. Interaction — '''mouse and keyboard are two separate input methods''', and the fundamental interaction design paradigm of the combination of these modalities has at its foundation to have two different highlights to specify focus. Since mouse and keyboard act and move in different ways, we have the ability to target them independently. |
| | 6 | 2. Weight — '''mouse and keyboard are inherently different in their behaviour''' too. The mouse pointer is often enough to signify where the user is and clicks. As a reference, many desktop UI guidelines don't even provide a hover in many instances, but they ALL provide keyboard navigation. Adding a styling to `hover` is in many instances an extra on top of not really requiring anything, while adding a styling on keyboard is a fundamental requirement, and it has to be evident because the user doesn't know where the focus is going to jump in the next tabulation. |
| | 7 | 3. Standard — the standard provides both for independent styling — for the reasons above. |