ACTION-10: Ask WCAG to clarify the 2.4.6 INTENT as follows: Note that this success criterion does not REQUIRE heading and labels—just that if they are provided, they be descriptive. Also if headings are provided they must be programmatically determinable per 1.3.1.
Ask WCAG to clarify the 2.4.6 INTENT as follows: Note that this success criterion does not REQUIRE heading and labels—just that if they are provided, they be descriptive. Also if headings are provided they must be programmatically determinable per 1.3.1.
- State:
- closed
- Person:
- Gregg Vanderheiden
- Due on:
- June 22, 2012
- Created on:
- June 15, 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
Correction to above note:
From the June 21st, 2012 WCAG WG meeting:
RESOLUTION: Add Note to 2.4.6 Understanding doc - "Note: This success criterion does not REQUIRE heading and labels, just that, if they are provided, they be descriptive. Also note that, if headings are provided, they must be programmatically determinable per 1.3.1."
Display change log.