W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2006

Re: Public vs. Private information

From: vivienne trulock <vivienne@ilikecake.net>
Date: Mon, 20 Nov 2006 22:33:29 +0000
Message-ID: <db4fe6a00611201433x233699c7n1e98598e3dd66f0b@mail.gmail.com>
To: "John Foliot" <foliot@wats.ca>
Cc: gawds_discuss@yahoogroups.com, w3c-wai-ig@w3.org

Hi John

What about using a style and a title attribute to give both visual and
semantic markup
<td class="private" title="private">cell content</td>

V

On 20/11/06, John Foliot <foliot@wats.ca> wrote:
>
> Polling for some ideas / opinions.
>
> The scenario:
> Database search returns back a large chunk of data about a person - some of
> this data is public, but other bits are "private", and requires
> authentication (logged in) for it to be exposed.  The issue however is that
> the query subject (person) gets to decide what is public and what is
> private, so the field returns are variable; for example I can choose to list
> my cellular number as public or private, but the choice is up to me.  I may
> choose public but my associate may choose private.
>
> The problem:
> The issue is how to denote what is public and what is private to
> authenticated users (who are seeing both), given that for many (most) of the
> individual field returns it can be either.
>
> The on-screen return must match results each time (order), so dynamically
> grouping the public stuff and the private stuff unfortunately won't work.
>
> In the paper prototypes, the designer is displaying the public content in a
> bold font and the private content in regular font (<strong>Public
> Data</strong>), along with text that explains:
> "Information in bold is in this person's public profile.  All other
> information is available to you as an authenticated user." (I wish I could
> show you, but the examples are behind the wall)
>
> Needless to say I am uncomfortable about this, as it is relying on a mostly
> visual display to convey supplemental information.  However I am drawing a
> blank on ways of achieving the requirement that also meet accessibility
> guidelines, short of adding a "private" icon with appropriate alt text at
> the end of each private result.  This could conceivably produce a page with
> 12 - 20 "private icons", an issue in it's own right.
>
> If anyone has dealt with a similar scenario, I would be curious how you
> resolved the issue (a link would be awesome!), however even if you have
> never dealt with this, if you have an idea or opinion I'm open to both.
>
> Thanks in advance.
>
> JF
> ---
> John Foliot
> Academic Technology Specialist
> Stanford Online Accessibility Program
> http://soap.stanford.edu
> Stanford University
> 560 Escondido Mall
> Meyer Library 181
> Stanford, CA 94305-3093
>
>
>
>


-- 
http://www.ilikecake.net
+353 1 658 4081

The information in this email (including attachments) is intended
solely for the named addressee(s) and may contain confidential and/or
privileged material. If you have received this in error please notify
the sender and delete the material from your computer. Any
retransmission of the contents of this mail is forbidden without the
written consent of the sender. ilikecake limited does not accept
liability for any loss or damage which may result from this email or
any attachment, or for errors or omissions arising after it was sent.
Received on Monday, 20 November 2006 22:33:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:31 UTC