- From: Janina Sajka <janina@rednote.net>
- Date: Tue, 29 Mar 2016 13:17:46 -0400
- To: public-aria-admin@w3.org
I think this could also cover touch keyboards on mobile devices where the user relies on echo to know which char is to be selected for input. Clearly, there are situations with mobile (and anywhere, actually) when echo is perfectly OK. At other times it may be necessary to go find those headphones. We worked on this quite a bit with Chase Bank's talking ATMs while I was at AFB years ago. We determined echo could be acceptable even in public environs, leaving it to the user to judge whether anyone else was also close enough to hear what was echoed. I think the main concern is to avoid surprises from the technology, the case where echo shows on screen, but not via the AT. Janina Léonie Watson writes: > From: Matt King [mailto:a11ythinker@gmail.com] > Sent: 29 March 2016 16:42 > > > > “Instead, could we place a normative requirement on screen readers to do 2 things when a password field is encountered: > > 1. Automatically turn off key echo while focus is in the password field. > > 2. If key echo was on, echo exactly what is typed in the field instead.” > > > > This would solve the problem I think, and it seems that Joannie has already implemented something very like it in Orca. > > > > Léonie. > > > > -- > > @LeonieWatson tink.uk Carpe diem. > > > > > -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Email: janina@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
Received on Tuesday, 29 March 2016 17:19:38 UTC