RE: technique to include security

I agree and interestingly Jakob Nielsen has just come out with some new guidance about those three lines that we now see as menu items for responsively designed sites – this is also linked to memory load for making objects actions and options visible in this case the fact that you lose the main menu system and are presented with what he calls a ‘hamburger menu’. http://tinyurl.com/nreydpa


Best wishes
E.A.

Mrs E.A. Draffan
WAIS, ECS , University of Southampton
Mobile +44 (0)7976 289103
http://access.ecs.soton.ac.uk<http://access.ecs.soton.ac.uk/>
UK AAATE rep http://www.aaate.net/

http://www.emptech.info<http://www.emptech.info/>

From: Steve Lee [mailto:steve@opendirective.com]
Sent: 18 August 2015 12:04
To: John Rochford
Cc: public-cognitive-a11y-tf; lisa. seeman
Subject: RE: technique to include security


That's very good

Steve Lee
Sent from my mobile device Please excuse typing errors
On 18 Aug 2015 11:58, "Rochford, John" <john.rochford@umassmed.edu<mailto:john.rochford@umassmed.edu>> wrote:
Hi Lisa,

My second impression about this approach is that it could be combined with recommendations for what developers *should* do.

Example:
“Minimize the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.”

Reference: Neilson 10 Principles at http://www.expressiveproductdesign.com/nielsens-10-usability-heuristics-user-interface-design/ , provided by Steve Lee to our list serve on 8/14.

John

John Rochford<http://profiles.umassmed.edu/profiles/display/132901>
UMass Medical School/E.K. Shriver Center
Director, INDEX Program
Instructor, Family Medicine & Community Health
www.DisabilityInfo.org<http://www.DisabilityInfo.org>
Twitter: @ClearHelper<https://twitter.com/clearhelper>
 <http://www.facebook.com/pages/New-England-INDEXShriver-CenterUMass-Medical-School/227064920160>

From: Rochford, John
Sent: Tuesday, August 18, 2015 6:48 AM
To: 'lisa.seeman' <lisa.seeman@zoho.com>; public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Subject: RE: technique to include security

Hi Lisa,

My first impression about this approach is that it does not provide developers any recommendations about what they *should* do, which is the optimal approach.

John

John Rochford
UMass Medical School/E.K. Shriver Center
Director, INDEX Program
Instructor, Family Medicine & Community Health
www.DisabilityInfo.org
Twitter: @ClearHelper



From: lisa.seeman [mailto:lisa.seeman@zoho.com]
Sent: Tuesday, August 18, 2015 6:02 AM
To: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Subject: technique to include security

Hi
I was thinking of the following technique as a way to include security and other considerations



"Do not require cognitive abilities when it is  avoidable"


In security this may include:
Requiring that the user has a good working memory or short term memory required to copy a code
Requiring that the user can remember complex passwords
Requiring that the user can remeber spelling of terms used in security questions such as how to spell a strange pets name
Requiring that the user can remember visual patterns

Having tokans, signing in via email account or face book, or biometrics are all alternatives to the above


In voice  systems this may include,

  *   Requiring the user to understand categories,
  *   Requiring the user to remember numbers
  *   can all be used as a barrier to getting human help
is is aviodable by having 0 as a reserved digit to access a human

In the Web of things this may include:

  1.  remembering what symbols mean
  2.  remembering sequences to run certain tasks
This is aviodable by having simple text with symbols and
clear discovrability of how o complete each task
and recovrability from errors



All the best

Lisa Seeman

Athena ICT Accessibility Projects
LinkedIn, Twitter