- From: White, Jason J <jjwhite@ets.org>
- Date: Fri, 17 Jun 2016 19:52:56 +0000
- To: John Foliot <john.foliot@deque.com>, Joanmarie Diggs <jdiggs@igalia.com>
- CC: James Craig <jcraig@apple.com>, ARIA Working Group <public-aria@w3.org>, Michiel Bijl <michiel@agosto.nl>
- Message-ID: <BY2PR0701MB19909D74DF1B78F4D017C702AB570@BY2PR0701MB1990.namprd07.prod.outlook.>
From: John Foliot [mailto:john.foliot@deque.com] No worries, we now have James here who *is* an Apple person. I know that Apple traditionally does not state if or when they plan on doing anything specific, although James your continued input into this discussion is I think valuable. It is apparent that for this to "work" as scoped we will need the screen reader vendors onboard, and lack of 'support' in Voiceover would be a significant issue going forward. We currently have indication that ORCA (via Joanie) will support this, and it has been stated that Freedom Scientific are working on supporting this in JAWs, however there are significantly more screen readers in the marketplace then there are browsers, and so that is yet another troubling scenario - without widespread support this will not even address the problem it alledges to be addressing. If a screen reader doesn’t support the password role, then it seems to me that the outcome can’t be worse than a situation in which the author chooses to implement a custom password widget and there is no password role with which to make it accessible using ARIA. That is, defining the role improves the status quo for users of screen readers which support it, without making the situation worse for others. We already have a CFC on this which passed and I would rather avoid yet another lengthy controversy on the subject. ________________________________ 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, 17 June 2016 19:53:26 UTC