- From: White, Jason J <jjwhite@ets.org>
- Date: Fri, 11 Sep 2015 15:43:57 +0000
- To: James Craig <jcraig@apple.com>
- CC: WAI Protocols & Formats <public-pfwg@w3.org>
> On Sep 11, 2015, at 03:58, James Craig <jcraig@apple.com> wrote: > > Please change it to recommend one or the other (either @aria-errormessage or live regions) but not both simultaneously. +1 The spec, as currently drafted, is going to confuse Web application authors very effectively, as they won’t know how to decide whether to use live regions or not in this case, or whether the user’s experience will differ depending on the choice that is made. My view is that error messages should always be announced and presented in braille as soon as aria-invalid becomes true, provided of course that aria-errormessage is specified on the element. I suppose someone could argue for finer control using a polite rather than an assertive region, but I can’t think of a persuasive use case for it. ________________________________ 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 Friday, 11 September 2015 15:44:27 UTC