RE: Initial draft of aria-linktype (RESEND)

This is an interesting proposal. Wouldn't it be better just to define four roles in the ontology that inherit their properties from the link role? It seems you are introducing a secondary attribute that contains what is really role information. (It's an enumeration, unlike aria-roledescription). Thus role="detailslink|commentlink|..." would be the alternative.

Another opton would be to have a global ARIA mechanism for subcategorizing roles, but it isn't clear what the advantage would be if everyone has to implement it (one might as well just carry the information in more specific roles).

I suppose one could argue that the proposed property isn't characterizing the role of the link object but only its destination. One could call it aria-linkdest to make that point clearer. How one interacts with it and its effect are the same regardless of the type of destination, so there could be merit in that argument.


________________________________

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, 12 February 2016 21:22:37 UTC