- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 9 Mar 2017 18:44:40 +0000
- To: Rich Schwerdtfeger <richschwer@gmail.com>, Alexander Surkov <surkov.alexander@gmail.com>, Bogdan Brinza <bbrinza@microsoft.com>, Dominic Mazzoni <dmazzoni@google.com>
- CC: ARIA Working Group <public-aria@w3.org>
> -----Original Message----- > From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] > Sent: Thursday, March 9, 2017 8:20 AM > So, the ARIA 1.1 spec. no longer supports aria-expanded on the separator role. > Consequently, it is now an invalid property for that role. Should browsers > suppress the mapping if it is not the role or leave it up to accessibility test tools > to flag it or both? [Jason] I think what they do should be consistent with the kind of checking that is already performed on states and properties in deciding whether to forward them to the accessibility API. If they already check that a state/property is valid for the role of the element, then they can perform the test in this case as well. If not, then they should simply forward the result to the AT, and leave it to accessibility evaluation tools to discover the problem. So far as I can remember, we don't specify anywhere what checking user agents should perform. If that's the case, then I suppose it's implementation-defined, and authors shouldn't rely on any specific behavior if they decide to use ARIA attributes contrary to specification. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Thursday, 9 March 2017 18:45:15 UTC