- From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
- Date: Mon, 15 Dec 2014 11:06:11 -0500
- To: "'Rigo Wenning'" <rigo@w3.org>, <public-privacy@w3.org>
- Cc: "'David Singer'" <singer@apple.com>, "'Nicholas Doty'" <npdoty@w3.org>, "'Joseph Lorenzo Hall'" <joe@cdt.org>, <chaals@yandex-team.ru>, "'Richard Schwerdtfeger'" <schwer@us.ibm.com>, "Janina Sajka" <janina@rednote.net>, "jcraig@apple com" <jcraig@apple.com>
Relative to IndieUI and accessibility preferences and settings, (unless something has changed that I am unaware of) the plan is to provide that level of user control, via user prompts with specific information about exposure. I am unsure about Access Key support in the current drafts. * katie * Katie Haritos-Shea Senior Accessibility SME (WCAG/Section 508/ADA/AODA) Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile | Office: 703-371-5545 -----Original Message----- From: Rigo Wenning [mailto:rigo@w3.org] Sent: Monday, December 15, 2014 10:41 AM To: public-privacy@w3.org Cc: David Singer; Nicholas Doty; Joseph Lorenzo Hall; chaals@yandex-team.ru Subject: Re: does accessKeyLabel expose user data? On Wednesday 10 December 2014 14:00:20 David Singer wrote: > Yes. At the recent workshop, we asked whether giving the user > “control” over their privacy necessarily means giving the user more > “controls”, especially when the consequences of the choices are not > obvious. But it would be already beneficial to give the user controls where the consequences *are* obvious. The current tendency in UX is to not expose much anymore. -- Rigo Wenning (@rigow) - W3C Legal counsel
Received on Monday, 15 December 2014 16:06:41 UTC