Understanding 1.4.13 Show Hide techniques and failures for 1.4.13 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.13 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. SCR39: Making content on focus or hover hoverable, dismissible, and persistent ARIA: Using role="tooltip" (Potential future technique) CSS: Using hover and focus pseudo classes (Potential future technique) Failures for Success Criterion 1.4.13 F95: Failure of Success Criterion 1.4.13 due to content shown on hover not being hoverable Failure to make content dismissable without moving pointer hover or keyboard focus (Potential future technique) Failure to meet by content on hover or focus not remaining visible until dismissed or invalid (Potential future technique) Back to top Principle 2 – Operable User interface components and navigation must be operable. Guideline 2.1 – Keyboard Accessible Make all functionality available from a keyboard. 2.1.1 Keyboard Level A 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.