- From: White, Jason J <jjwhite@ets.org>
- Date: Tue, 29 Mar 2016 15:31:54 +0000
- To: Joanmarie Diggs <jdiggs@igalia.com>, "tink@tink.uk" <tink@tink.uk>
- CC: 'Rich Schwerdtfeger' <richschwer@gmail.com>, 'John Foliot' <john.foliot@deque.com>, 'ARIA Working Group' <public-aria-admin@w3.org>
>-----Original Message----- >From: Joanmarie Diggs [mailto:jdiggs@igalia.com] >For what it's worth, what Orca now does (semi-recent change) if something >has ATSPI_ROLE_PASSWORD and key echo is also enabled is twofold: > >1. Do not echo keypresses >2. Do echo inserted characters Item 2 also implies that the braille display, if present, would show the inserted characters. > >I realize that "no one uses Linux." <grins> However, if the screen readers of >the major platforms were to adopt such an approach, would it not address the >concerns Léonie raises? I do use Linux a lot, which is perhaps why I didn't recognize a problem here. I think the above measures would place a screen reader user in an equal position to users of the visual interface, who have to start entering text into a password field to find out whether or not it is hidden (as it normally should be). Also, not all password fields hide the text that is entered; one interface that I used recently had a "show password" check box next to the password entry field. ________________________________ 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 15:32:25 UTC