- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Tue, 5 Feb 2013 09:13:40 +0800
- To: James Craig <jcraig@apple.com>
- Cc: wai-xtech@w3.org
Hi, James. It seems it's usual practice to ignore the attribute having empty or undefined value as it wasn't presented at all. Otherwise it looks good. Thank you. Alex. On Tue, Feb 5, 2013 at 5:17 AM, James Craig <jcraig@apple.com> wrote: > Would this edit resolve the confusion? > > From: > "if the attribute is not present, or its value is false then the default value of false applies." > > To: > "if the attribute is not present, then the value is inherited from the parent element." > > > On Feb 4, 2013, at 2:43 AM, Alexander Surkov <surkov.alexander@gmail.com> wrote: > >> Hi. The spec says >> (http://www.w3.org/WAI/PF/aria/states_and_properties#aria-invalid): >> >> "For future expansion, the aria-invalid attribute is an enumerated >> type. Any value not recognized in the list of allowed values MUST be >> treated by user agents as if the value true had been provided. If the >> attribute is not present, or its value is false, or its value is an >> empty string, the default value of false applies." >> >> In particular this means that >> >> <div aria-invalid="true"> >> <span>1st span</span> >> <span aria-invalid="false">2nd span</span> >> </div> >> >> Both "1st span" and "2nd span" text ranges should have "invalid:false" >> text attributes because "if the attribute is not present, or its value >> is false then the default value of false applies". It doesn't seem >> this behavior in the context of the "1st span" text range is evident >> and actually wanted. >> >> Thank you. >> Alex. >> >
Received on Tuesday, 5 February 2013 01:14:07 UTC