- From: Jonathan Avila <jon.avila@levelaccess.com>
- Date: Fri, 16 Aug 2019 01:03:48 +0000
- To: Maximiliano Sorribas <max.sorribas@area7g.com>
- CC: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <BN6PR03MB31394A5A4390E94D459A7653F1AF0@BN6PR03MB3139.namprd03.prod.outlook.com>
Hi, while the mechanism sounds like it will meet the requirements I’m not sure users will know all of this. Perhaps updating the accessible description on the unmask button to say something like “activating will focus and unmask the SSN field”. When the unmasked field is focus the accessible description could say “remains unmasked until another field is focus”. We want to be careful not to add too much verbosity but we want to help the user know that focus will move and that when they move focus away from the unmasked field it will become masked. For example, we don’t want to violate 3.2.2 On Input – so we want to advise the user. We also want to use device independent language since this could be used on mobile. Jonathan Jonathan Avila, CPWA Chief Accessibility Officer Level Access jon.avila@levelaccess.com 703.637.8957 office Visit us online: Website<http://www.levelaccess.com/> | Twitter<https://twitter.com/LevelAccessA11y> | Facebook<https://www.facebook.com/LevelAccessA11y/> | LinkedIn<https://www.linkedin.com/company/level-access> | Blog<http://www.levelaccess.com/blog/> [The State of Digital Accessibility 2019 report is here! Download the report today to read the findings. Level Access]<https://levelaccess.com/state-of-digital-accessibility-2019> The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited. From: Maximiliano Sorribas <max.sorribas@area7g.com> Sent: Wednesday, August 14, 2019 7:02 AM To: Jonathan Avila <jon.avila@levelaccess.com> Cc: w3c-wai-ig@w3.org Subject: Re: Question about ADA Integration input fields with PII data CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Jonathan, At this moment I'm working on this mechanism: The user uses the key "Tab" to go to the masked field, so he listens ''this is a masked field", then he's going to listen the asterisks. Next, the user presses the "Tab" and move to the eye Icon (button) and he listens "Unmask field", then the user press "enter" to unmask and the focus auto-change to the field unmasked. Then the user is going to listen the unmasked information. When the user press "Tab" again the form focus to the next field and the unmasked field is masked again on blur event. That's my idea to integrate ada with PII masked data to secure the information and the user control to mask or unmask information. It's ok? What do you think about this mechanism? Maybe add some message at reading for example on the eye button "Unmask field xxxxx" and then when the auto-focus moves to the field the user listens the information directly or is better something like "Unmasked information of field zzzzz" before listening the information unmasked or do you think that the user maybe understand with the first message only. Thanks! -- Maximiliano J. Sorribas <http://www.area7g.com/> El mar., 13 ago. 2019 a las 9:19, Jonathan Avila (<jon.avila@levelaccess.com<mailto:jon.avila@levelaccess.com>>) escribió: If the field was only unmasked when another field was focused, I think it would be an issue for some screen reader user to access the unmasked contents. Jonathan Sent from my iPhone On Aug 13, 2019, at 2:14 AM, Maximiliano Sorribas <max.sorribas@area7g.com<mailto:max.sorribas@area7g.com>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, I have a question about ADA integration: If I have a PII masked field in a web form is a required or not use a button as an eye Icon to reveal and hide the information? Right now on our site, we use the event on focus to reveal and the on blur to hide the information of the field with masking using asterisks. Please somebody can clarify this. I don't find documentation about this case. Here is an example: <Screenshot_2019-08-06 Citi Wealth Builder - Goals(1).png> Thanks. Regards! Maximiliano Sorribas
Attachments
- image/jpeg attachment: image002.jpg
Received on Friday, 16 August 2019 01:04:15 UTC