Re: 7 Day Call for Consensus March 17, 2016 ARIA Working Group Resolutions

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]
> 
> 
>> 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.
> 
> ________________________________