- From: Paul Adam <paul.adam@deque.com>
- Date: Thu, 19 Nov 2015 11:25:05 -0600
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Cc: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
Received on Thursday, 19 November 2015 17:25:37 UTC
1.3.1 <http://www.w3.org/TR/2008/REC-WCAG20-20081211/#content-structure-separation-programmatic> Info and Relationships: Information, structure <http://www.w3.org/TR/2015/NOTE-UNDERSTANDING-WCAG20-20150226/content-structure-separation-programmatic.html#structuredef>, and relationships <http://www.w3.org/TR/2015/NOTE-UNDERSTANDING-WCAG20-20150226/content-structure-separation-programmatic.html#relationshipsdef> conveyed through presentation <http://www.w3.org/TR/2015/NOTE-UNDERSTANDING-WCAG20-20150226/content-structure-separation-programmatic.html#presentationdef> can be programmatically determined <http://www.w3.org/TR/2015/NOTE-UNDERSTANDING-WCAG20-20150226/content-structure-separation-programmatic.html#programmaticallydetermineddef> or are available in text. (Level A) Is there a definition in WCAG for the term "or are available in text.” So a title attribute can create not just an accessible name 4.1.2 but also a relationship connection 1.3.1? I could see the argument for aria-labelledby as that’s an association but aria-label or title are not connecting anything programmatically to the input. Paul J. Adam Accessibility Evangelist www.deque.com
Received on Thursday, 19 November 2015 17:25:37 UTC