Re: aria-current concerns from Apple


> On Sep 11, 2015, at 18:14, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> wrote:
>
> I'm not understanding how the ID ref is supposed to work for aria-current.
>
> The way it was proposed, aria-current would simply indicate that the element that it was applied to was current, such as the element that has focus.
>
> If aria-current is placed on some other container somewhere and points to another element using an ID ref, and the element that it is pointing to has focus, the AT won't be interfacing with the aria-current element and will never convey this to the user.
I don’t understand the last quoted sentence above.

The scenario is this: we have a container element with an aria-current attribute, the value of which is an idref that refers to one of the child elements of the container. When a different element becomes current, a script updates the idref accordingly.

I don’t understand why you seem to think the UA can’t expose this to the accessibility API as a property of the child element, i.e., as a property of the element to which the idref refers, rather than as a property of of the referring container element. So far as I am aware, this is perfectly possible and wouldn’t be hard to implement.


________________________________

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, 14 September 2015 13:35:31 UTC