- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Fri, 1 Apr 2016 16:36:03 -0400
- To: Rich Schwerdtfeger <richschwer@gmail.com>, John Foliot <john.foliot@deque.com>
- Cc: Cynthia Shelly <cyns@microsoft.com>, Matt King <a11ythinker@gmail.com>, Léonie Watson <tink@tink.uk>, ARIA Working Group <public-aria-admin@w3.org>, David Bolter <dbolter@mozilla.com>, Dominic Mazzoni <dmazzoni@google.com>, Chaals from Yandex <chaals@yandex-team.ru>, James Craig <jcraig@apple.com>, jamie@nvaccess.org
On 2016-04-01 3:11 PM, Rich Schwerdtfeger wrote:
> The problem needs to be addressed at the AT. If the AT speaks the
> actual rendered characters vs. either the echo’d text or the star star
> star issue then the user will immediately know whether the author has
> NOT obscured the te
This is stated in latest proposed text:
"Presenting the rendered characters ensures that all users receive the
same information, including notification when the value is being entered
into an unobscured password field."[1]
The reason is because the user agent exposes the rendered text in the
accessibility tree. That is, if the text is rendered on the screen as a
string of asterisks, then the text that appears in the accessibility API
is a string of asterisks. If the text is rendered as plain text, then
the accessibility API text is the same plain text.
There is an implied user agent MUST here: User agents MUST expose the
rendered text through the accessibility API.
Secondly, a nit: "unobscured" is not a word. I suggest "plain text" or
"clear text" instead.
[1] https://rawgit.com/w3c/aria/password-role/aria/aria.html#password
last sentence of third paragraph.
--
;;;;joseph.
'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
- C. Carter -
Received on Friday, 1 April 2016 20:36:41 UTC