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

Re: what do screen readers do with "the padlock"?

From: Joshue O Connor <joshue.oconnor@ncbi.ie>
Date: Wed, 31 Oct 2007 22:17:52 +0000
Message-ID: <4728FF10.6090206@ncbi.ie>
To: Alfred.S.Gilman@IEEE.org
Cc: 'WAI Interest Group list' <w3c-wai-ig@w3.org>

Al Gilman wrote:
> Do some screen readers or self-voicing browsers inform the user of
> this security status distinction?  Do they generally?  How?

JAWS in IE will generally output 'secure connection' when it comes
across the https:// protocol.

This area is very interesting. For example is security binary? Is
something either completely secure or completely insecure? Are there
grey areas where the connection may be partially secured and good enough
to use but not *completely* secure and so on?

To me it makes more sense for a user agent to be able to inform the user
to what degree a connection is secure. The user agent could detect the
encryption algorithm/key and inform the user if it is a high bit rate
(128 +) or of a lower variety. Colour coding can be used to visually
show the user however how is this information given to a screen reader user?

I suppose I am saying that in time IMO there will be a need for
informing the user about the *degree* of security and this must be
accessible to users of assistive technology.

BTW Security is an illusion anyway IMO.

Josh


********************************************************************

NOTICE: The information contained in this email and any attachments 
is confidential and may be privileged.  If you are not the intended 
recipient you should not use, disclose, distribute or copy any of 
the content of it or of any attachment; you are requested to notify 
the sender immediately of your receipt of the email and then to 
delete it and any attachments from your system.

NCBI endeavours to ensure that emails and any attachments generated 
by its staff are free from viruses or other contaminants.  However, 
it cannot accept any responsibility for any such which are 
transmitted.  We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email 
and any attachments are those of the author and do not necessarily 
represent the views of NCBI


********************************************************************
Received on Wednesday, 31 October 2007 22:18:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:27 GMT