W3C home > Mailing lists > Public > public-aria@w3.org > January 2016

RE: [UPDATED][REVIEW REQUESTED] Re: aria-ACTION-2004: Create proposal for password role

From: John Foliot <john.foliot@deque.com>
Date: Thu, 14 Jan 2016 15:21:48 -0600
To: "'Joanmarie Diggs'" <jdiggs@igalia.com>, <public-aria@w3.org>
Message-ID: <006101d14f11$946c7830$bd456890$@deque.com>
Hi Joanie,

Thanks for this. As a "wordsmithing" exercise, might I suggest the following minor change:

s/Authors must set the password element's text to the characters being displayed so that assistive technologies can present what is visible on screen. Authors must update the element's text each time a character is inserted or deleted by the user so that assistive technologies can confirm input according to the user's preferences.

/Authors must set the password element's text to the characters being displayed (according to the user's preferences - obfuscated or 'in-the-clear'), so that assistive technologies can present the equivalent to what is visible on screen. Authors must update the element's text each time a character is inserted or deleted by the user so that assistive technologies can confirm input (again, according to the user's preferences).

Wordier, yes, but clearer as well.

Thoughts?

JF

> -----Original Message-----
> From: Joanmarie Diggs [mailto:jdiggs@igalia.com]
> Sent: Thursday, January 14, 2016 2:16 PM
> To: public-aria@w3.org
> Subject: [UPDATED][REVIEW REQUESTED] Re: aria-ACTION-2004: Create
> proposal for password role
> 
> Hi all.
> 
> At today's concall I received feedback on my draft. Thanks!! I hopefully
> addressed all the concerns:
> 
> 1. Don't mention the possibility that a screen reader might be silent
>    during input in a password field. Fixed by replacing that example
>    with the example of emitting a sound.
> 2. Alluded to the fact that the screen reader behavior in password
>    fields is user configurable.
> 3. Replaced the not-meant-to-be-normative "may" with "might".
> 4. Replaced the author "SHOULD" with "MUST" (of which there are now two) 5.
> Stated that the text needs to contain the characters being displayed
>    (so bullets are spoken as bullets, but if the "show password text"
>    option is checked, ATs can present the actual text)
> 
> As I indicated in the meeting, the "A type of" language is used throughout our
> spec. I'm happy to take that out for all the roles where it is present -- but as
> another, separate action. In order to be consistent with the current spec
> language, I left the phrase in for password.
> 
> Thanks again for all the feedback! Please review the new version, which is in the
> same place (https://rawgit.com/w3c/aria/password-
> role/aria/aria.html#password).
> 
> --joanie
> 
> On 01/14/2016 12:01 PM, Joanmarie Diggs wrote:
> > Cynthia made a good case for the creation of a new password role, and
> > I agree with the need even though we're trying to feature freeze ARIA 1.1.
> > I also think this will be a quick review <fingers crossed>, so I have
> > a draft for your consideration:
> > https://rawgit.com/w3c/aria/password-role/aria/aria.html#password
> >
> > Thanks in advance!
> > --joanie
> >
> >
> 
Received on Thursday, 14 January 2016 21:22:23 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:18 UTC