- From: Léonie Watson <LWatson@PacielloGroup.com>
- Date: Wed, 19 Nov 2014 16:45:54 -0000
- To: "'Joseph Scheuhammer'" <clown@alum.mit.edu>, "'Matthew King'" <mattking@us.ibm.com>, <public-pfwg@w3.org>
Joseph Scheuhammer wrote: "I lean towards: if aria-current is undefined, that means the element is not current, i.e. "undefined" == "false". I can't think of a use case where it is desirable to restrict certain elements as being not current AND unable to ever become current. Maybe someone can outline such a use case; if so, then "undefined" can be defined as "not current and can't ever be current"." The intention is that false and undefined are equivalent, yes. "I'm not sure what "conveyed by User Agents" means here. It could be interpreted as, "User Agents SHOULD NOT expose values of 'false' or 'undefined' via the accessibility API". Is that correct? If so, that does make values of "false" and "undefined" equivalent, at least with respect to accessibility APIs. Could you clarify?" Yes, that's it. Unless aria-current="true" nothing needs/should be exposed by the browser. Léonie. -- Senior Accessibility Engineer, TPG @LeonieWatson @PacielloGroup
Received on Wednesday, 19 November 2014 16:46:14 UTC