- From: Léonie Watson <tink@tink.uk>
- Date: Sat, 2 Apr 2016 12:37:44 +0100
- To: "'Rich Schwerdtfeger'" <richschwer@gmail.com>, "'Chaals McCathie Nevile'" <chaals@yandex-team.ru>
- Cc: "'James Teh'" <jamie@nvaccess.org>, "'John Foliot'" <john.foliot@deque.com>, "'Joseph Scheuhammer'" <clown@alum.mit.edu>, "'Cynthia Shelly'" <cyns@microsoft.com>, "'Matt King'" <a11ythinker@gmail.com>, "'ARIA Working Group'" <public-aria-admin@w3.org>, "'David Bolter'" <dbolter@mozilla.com>, "'Dominic Mazzoni'" <dmazzoni@google.com>, "'James Craig'" <jcraig@apple.com>
> From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] > Sent: 02 April 2016 12:22 > > No. We spoke to Microsoft browser people. They did not believe we made > the problem worse. We also heard from Wendy Seltzer, who agreed that the proposed role definition represented a risk because of the possible discrepancy between the visual and aural representations. > > Our solution thus far actually narrows it for screen reader users. > No, I'm sorry, it doesn't. It changes the security risk, it doesn't narrow it down. If anything the uncertainty factor makes it a much more serious problem. The updated role definition is a step in the right direction, but Jamie Teh raises some valid points. We need to hear from other SR vendors including Apple, Dolphin and GWMicro/AISquared, and it would be helpful if we could point to wherever Freedom Scientific and others have expressed their commitment to implementing the role as described. > I asked Cynthia to reach out to Microsoft as I felt their browser team would > be more experienced in dealing with browser security issues than an interest > group. That said, who do you recommend I ask in the security ig? Are they > active? Wendy offered a review by WebAppsSec. Perhaps we could take her up on that offer? Léonie. -- @LeonieWatson tink.uk Carpe diem.
Received on Saturday, 2 April 2016 11:39:11 UTC