This document:Public document·View comments·Disposition of Comments·
Nearby:Accessibility Guidelines Working Group Other specs in this tool Accessibility Guidelines Working Group's Issue tracker
Quick access to LC-2651 LC-2652 LC-2653 LC-2654 LC-2655 LC-2656 LC-2657 LC-2658 LC-2659 LC-2660 LC-2661 LC-2662 LC-2663 LC-2664 LC-2665 LC-2666 LC-2667 LC-2668 LC-2669 LC-2670 LC-2671 LC-2672 LC-2673 LC-2674 LC-2675 LC-2676 LC-2677 LC-2678 LC-2679 LC-2680 LC-2681 LC-2682 LC-2686 LC-2687 LC-2688 LC-2689 LC-2690 LC-2691 LC-2692 LC-2693 LC-2694 LC-2695 LC-2698 LC-2700 LC-2701 LC-2702 LC-2817 LC-2818
Previous: LC-2676 Next: LC-2677
Keyboard should not be required for all scenarios. Alternate approach should be considered. WCAG 2.0 success criteria 2.1.1 is no longer an appropriate requirement for software. Keyboard was the input method of choice for visually impaired and users without fine motor control. But keyboard is no long the only viable option for input and navigation in such scenarios. It would be important to recognize that there are alternatives to keyboard input such as allowing multiple user selectable input options that use different bodily functions (speech recognition, gesture, touch, etc.) Keyboard should no longer be considered a required input method when other viable options are available. In fact, we believe our recommendation is more accessible to more people, with and without disabilities. We recommend to replace WCAG 2.0 2.1.1 with a more flexible success criteria to allow accessible ICT innovation. "Where the platform supports keyboard navigational and manipulation interfaces, all functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. Where the platform does not support keyboard navigational and manipulation interfaces, all functionality of the content is operable through at least two user selectable input and feedback modalities, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints."