- From: John Foliot <john.foliot@deque.com>
- Date: Tue, 29 Mar 2016 12:13:09 -0700
- To: Rich Schwerdtfeger <richschwer@gmail.com>
- Cc: "White, Jason J" <jjwhite@ets.org>, janina@rednote.net, "public-aria-admin@w3.org" <public-aria-admin@w3.org>
- Message-ID: <CAKdCpxwU_z=f9c4nKrWvJSb0cnc6eosLOTNq9U1D-9MS0de-Bg@mail.gmail.com>
I would argue that when it comes to security and privacy, that SHOULD is not enough: it needs to be a MUST (at least from my vantage point). That said, if we can get a commitment from the SR vendors, then it might be enough of a solution. JF On Mar 29, 2016 3:06 PM, "Rich Schwerdtfeger" <richschwer@gmail.com> wrote: > Having built screen readers myself there are things that the screen reader > could do to compare the text being echoed to the text in the input field. > If it were a password field and the text was not obscured then a screen > reader should let the user know they have a problem. It is very easy to > read the input field text and compare the results against what is being > typed. > > We have not done this before but this is a good place where we could put a > screen reader SHOULD … > > Rich > > Rich Schwerdtfeger > > > > > On Mar 29, 2016, at 12:56 PM, White, Jason J <jjwhite@ets.org> wrote: > > > > -----Original Message----- > From: Janina Sajka [mailto:janina@rednote.net <janina@rednote.net>] > > > > I think the main concern is to avoid surprises from the technology, the > case where echo shows on screen, but not via the AT. > > > I agree. I think echo should generally be suppressed by screen readers in > this case, but the characters spoken as one navigates on a touch screen > around a virtual keyboard aren't echo in my view. > > I think the spec should provide advice to implementors on these points, > but I'm not sure whether it should be normative. Security considerations > are of course important. > > > ________________________________ > > 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 Tuesday, 29 March 2016 19:13:38 UTC