- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 18 Feb 2016 18:19:36 +0000
- To: Richard Schwerdtfeger <richschwer@gmail.com>, Joanmarie Diggs <jdiggs@igalia.com>
- CC: ARIA Working Group <public-aria@w3.org>
>-----Original Message----- >From: Richard Schwerdtfeger [mailto:richschwer@gmail.com] > >I am not quite following the correlation to roledescription. I think it is more >akin to subrole on some operating system platforms and that the reason for >having them is that regardless of the subrole both the user and assistive >technology need to know that it is still a link and work with the content as if it >was a form of link. I agree that there isn't a relationship with aria-roledescription. I think it's better to conceive this property as characterizing the destination of the link rather than as creating a subrole for the element on which the attribute is used. If we think of it as a kind of subrole then there's a stronger case for simply defining a new role for each link type. The counter-argument is that we should provide backward compatibility to ARIA 1.0 UAs that don't support the new roles, but by that logic we would be unable to add new roles anywhere in the ontology - and I don't support the backward-compatibility argument, for this reason. ________________________________ 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 Thursday, 18 February 2016 18:20:09 UTC