Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

Accessible Authentication discussion

John Rochford edited this page Dec 20, 2017 · 6 revisions

see current wording: https://www.w3.org/WAI/GL/wiki/2.2.7_Revision# (Correction from John Rochford: Previous address is for Interruptions. Most-recent commentary on Authentication is https://www.w3.org/WAI/GL/wiki/Comment_Summary_2-2-6 .)

or re-authentication

re-authentication processes do not rely upon the user's ability to do any of the following:

memorize information; or perform calculations, such as including correctly identifying and entering numbers and letters from a character string; or reliably produce gestures; or recognize characters presented on screen, and then enter them into an input field; or speak; or transcribe information. Exceptions:

Re-authentication process only relies on basic personal identification information to which the user has easy access, such as name, address, email address and national identification number. This is not achievable due to governing statutory requirements.

comments - we lost the "speech" criteria, but at this point I do not remember why. I do not think speach signatures are included in 1.1.1 or captions etc as it is not a percivability issue.

Re-authentication (AC)

Re-authentication processes do not rely upon the user to do any of the following:

  • memorize information;
  • perform calculations;
  • reliably produce gestures;
  • transcribe information.

Exceptions:

  • Re-authentication process can rely on the user or user-agent entering personal identification information, such as name, username, password, address, email address, or national identification number, if the web content does not block automatic entry.

  • There are governing statutory requirements that require the use of memorisation, calculations, gestures, or transcription.