From: Léonie Watson [mailto:tink@tink.uk] Sent: Monday, April 25, 2016 3:32 PM That’s more or less what’s happening I think. The feature has been marked as at risk/under review in the spec, pending implementations and the Security IG review. It does raise a question about the ARIA exit criteria though. By the looks of things, the ARIA 1.0 exit criteria [1] only required interoperability at the accessibility API/browser level, not at the AT/screen reader level. I’ve been thinking about this issue and I agree that it needs careful attention. In this case, we make strong recommendations about correct implementation on the part of the AT, any departure from which should take into account the motivating security considerations that underlie the statements in the specification. I think the exit criteria need to be carefully considered (here and in certain other instances of new features introduced into ARIA 1.1). ________________________________ 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 Monday, 25 April 2016 21:27:01 UTC