- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Wed, 19 Nov 2014 12:57:49 -0500
- To: Matthew King <mattking@us.ibm.com>, Joseph Scheuhammer <clown@alum.mit.edu>
- CC: public-pfwg@w3.org
Léonie, Matt, Thanks for your clarifications. > So, what is the best way to write the text so the undefine/false > equivalency is clear? For the "Values" table, how about: "false (default): The element is not current. true: The element is current." I'm following the style of the value tables for other boolean aria-* attributes. For example, see the table for aria-disabled (http://rawgit.com/w3c/aria/master/aria/aria.html#aria-disabled). Similarly, for the "Value" entry in the "Characteristics" table: "Value: true/false" Also, given that "conveyed by User Agents" has to do with the accessibility API, I suggest this re-wording: "If the aria-current attribute is false or undefined, User Agents SHOULD NOT expose the aria-current state of an element, and assistive technologies SHOULD NOT convey it." Hope that helps. -- ;;;;joseph. 'Array(16).join("wat" - 1) + " Batman!"' - G. Bernhardt -
Received on Wednesday, 19 November 2014 17:58:18 UTC