- From: James Craig <jcraig@apple.com>
- Date: Mon, 02 Jun 2014 16:28:10 -0700
- To: Alexander Surkov <surkov.alexander@gmail.com>
- Cc: W3C WAI Protocols & Formats <public-pfwg@w3.org>
On Jun 2, 2014, at 2:05 PM, James Craig <jcraig@apple.com> wrote: > On Jun 2, 2014, at 1:36 PM, Alexander Surkov <surkov.alexander@gmail.com> wrote: > >> 1) A concern may be unrelated but aria-checked doesn't look clear [1], 'undefined' value is not defined or not linked, I see the undefined definition in the spec. http://rawgit.com/w3c/aria/master/spec/aria.html#aria-checked That said, I can see that it is confusing to list the implicit "undefined" value of a tristate control, when the tristate definition does not include "undefined." >> if it's supposed to define 'default value'/'missed value' then it's not in sync with implicit value for "checkbox" role [2] > > This may be an artifact b/c aria-checked used to be "allowed" on more roles. I think we've sufficiently cleaned up the taxonomy now so that aria-checked may be able to move back to the true/false/mixed datatype instead of true/false/mixed/undefined. It currently states that checked defaults to "undefined" on all roles except radio, checkbox, menuitemcheckbox, menuitemradio, etc. Previously it was allowed (but irrelevant) on option and maybe others. That may no longer be necessary. Bug 25951 - aria-checked lists tristate value but includes an implicit undefined value https://www.w3.org/Bugs/Public/show_bug.cgi?id=25951 Possible resolutions: 1. Remove the "undefined" definition from aria-checked. 2. Add undefined as a value on "tristate." Other suggestions? James
Received on Monday, 2 June 2014 23:28:43 UTC