Possible draft of 3.2.7

This is a rough first draft of an alternative for Success Criterion 3.2.7 

Please anyone send me comments on how to improve this — or problems I missed.

Thanks

Gregg



Success Criterion 3.2.7 Controls Visible as Controls (Level AA): When user interface components are invisible or not visually indicated as controls until hover or focus, provide a visible indicator that the components are available and are controls, except when:

·       The same functionality is available through a component on the same page, or on a different step in a multi-step process, without requiring pointer hover or keyboard focus to make it visible as a control;

·       The component provides keyboard-only functionality;

·       A mechanism is available to make the components persistently visible as a control;

·       A mechanism makes controls visible as controls whenever a pointer is moved within or over the page, page is clicked anywhere, or keyboard is used – and stays visible for at least 3 seconds after movement or keyboard operation stops

·       Hiding the visibility of the control as a control is essential to the purpose of the page. 



Examples of problems that fail

·      Controls are hidden unless the person points directly to the control

·      Page where links are not visible until the person tabs to them

 

Examples that pass

·      Movie where all controls are hidden but show up as soon as mouse is moved, person touches the screen anywhere, or the keyboard is used.

·      Page where links are hidden but show up as soon as mouse or keyboard are used within or over the page.



 



Gregg

———————————
Gregg Vanderheiden
gregg@vanderheiden.us