Re: aria-current concerns from Apple

Uhm, I think you replied to the wrong thread, or at the very least used aria-errormessage instead of aria-current ;)

Although one could apply the ID to the currently active item in the list, that doesn’t seem preferable as it doesn’t match the intentions of ID’s. Also, what if an element already had an ID besides the one designated to be used for the current element?

—Michiel

> On 11 Sep 2015, at 17:58, White, Jason J <jjwhite@ets.org> wrote:
> 
> 
>> On Sep 11, 2015, at 11:51, Michiel Bijl <michiel@agosto.nl> wrote:
>> 
>> A downside to this implementation is that you need to have ID’s on everything. This is not a practice most developers use.
>> 
> You only need an ID on the element that provides the error message. If that’s a serious problem (and it shouldn’t be), then I suppose one could define aria-errormessage=“text of error message” and aria-errormessageref=idref.
> 
>> Any thoughts on that?
> It isn’t hard to satisfy the requirement to put an id on the element with the error message.
> 
> 
> ________________________________
> 
> 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.
> 
> ________________________________
>