Description
WCAG Level
Level A
Priority
High
Pages/screens/components affected
Description
Good design means supporting different modes of interaction, because there are many reasons why someone might use a keyboard instead of a mouse, and if keyboard interaction is not fully supported the website is effectively unusable.
While the vaadin-context-menu itself is keyboard-accessible, the documentation pages for it currently only have examples that require a user to right-click / long-touch static text sections.
User impact
Someone with mobility problems will often use a keyboard instead of a mouse to navigate a web page. A screen reader user will also tend to use a keyboard if they cannot see the screen to use the mouse. Therefore if the website does not properly support keyboard interaction a large number of people are effectively prevented from using it.
In this case, sighted keyboard users will not be able to trigger any context menu example in the documentation site.
Required solution
Make sure that all interactive controls can be used with a keyboard.
In this case, make sure that examples include an actual keyboard-focusable element that has a context menu associated with it. We would recommend further including an explanation/instruction that reminds keyboard users that once the element has focus, they can trigger the context menu using Shift+F10 (or the dedicated context menu key on their keyboard) on Windows. Note that on MacOS, there does not currently seem to be a dedicated key or key combination to trigger the context menu using the keyboard (though users can set up custom key mappings that send the equivalent of a mouse's right-click).
This solution must be applied to all instances of the issue identified within the test sample, then applied to all other instances of the same issue identified throughout the rest of the components, their variants, and the documentation website.
Definition of done
Complete all of these tasks before closing this issue or indicating it is ready for retest:
- All issues identified within the test sample have been resolved.
- The rest of the components, their variants, and the documentation website have been tested for the same issue.
- All issues identified throughout the rest of the components/website have been resolved or filed as new issues.
Related standards
More information
Test data
Test date: March 2021
Website: vaadin.com/components, vaadin.com/docs-beta