ACTION-15: Ask WCAG to add to 1.3.3 INTENT: WCAG was designed to apply only to controls that were displayed on screen. The intent was to prevent references to visual or auditory cues. When applying this to instructions for operating physical hardware controls (e.g. a web kiosk with dedicated content), tactile cues on the hardware might be described (e.g. the arrow shaped key, the round key on the right side). This success criterion is not intended to prevent the use of tactile cues in instructions.
Ask WCAG to add to 1.3.3 INTENT: WCAG was designed to apply only to controls that were displayed on screen. The intent was to prevent references to visual or auditory cues. When applying this to instructions for operating physical hardware controls (e.g. a web kiosk with dedicated content), tactile cues on the hardware might be described (e.g. the arrow shaped key, the round key on the right side). This success criterion is not intended to prevent the use of tactile cues in instructions.
- State:
- closed
- Person:
- Gregg Vanderheiden
- Due on:
- June 26, 2012
- Created on:
- June 19, 2012
- Related emails:
- No related emails
Related notes:
From the June 21st, 2012, WCAG WG meeting:
Add the following to the intent of SC 1.3.3 in Understanding WCAG: WCAG was designed to apply only to controls that were displayed on a web page. The intent was to avoid describing controls solely via references to visual or auditory cues. When applying this to instructions for operating physical hardware controls (e.g. a web kiosk with dedicated content), tactile cues on the hardware might be described (e.g. the arrow shaped key, the round key on the right side). This success criterion is not intended to prevent the use of tactile cues in instructions.
RESOLUTION: Add the text above to SC1.3.3 in Understanding WCAG2
Display change log.