Tomjones at 22:50, 12 October 2018

2018-10-12T22:50:39Z

New page

''<< Back to [[Baseline_Functional_Requirements_v1.0|Baseline Functional Requirements Index]]''

== USABLE-3. PLAIN LANGUAGE ==
Information presented to [[IDEF Glossary USERS|USERS]] in [[IDEF Glossary DIGITAL IDENTITY MANAGEMENT FUNCTIONS|digital identity management functions]] MUST be in plain language that is clear and easy for a general audience or the transaction's identified target audience to understand.

=== SUPPLEMENTAL GUIDANCE ===
Instructions for use of the system should be visible or easily retrievable whenever appropriate.

Help and documentation information should be easy to search, focused on the users' task, listing
concrete steps to be carried out, and be concise.

Platform conventions for words, actions, and situations are consistent across the platform.
Example: users should not have to wonder whether different words, situations, or actions mean the same thing across the platform.

The system should speak the users' language, following real-world conventions and making
information appear in a natural and logical order.
Example: Systems should use words or phrases and graphics or icons familiar to the user rather than system-oriented terms.
Example: although the phrase "privacy enhancing technology" is widely in use in industry, research suggests that "privacy protection" is more readily understood and used by real users.

Error messages should be expressed in plain language, without codes, clearly indicating the problem
and constructively suggesting a solution.

The user’s identity status on a system should be clear to the user.
Example: It should be clear to the
user whether their identity is anonymous, pseudonymous or verified.

Any change in identity status should be presented in clear language to the user.
Example: If a process requires a user to switch to a verified identity from a more anonymous state, the user should
be clearly prompted to change their identity status.

Descriptions of states of identity (verified, anonymous, pseudonymous) should be linked to clear,
easy to read, understandable and concise definitions.

If standard definitions are available, they should be used.

The design of the website should eliminate information that is irrelevant or rarely needed.

Layout and look/feel/branding, in addition to language, should also eliminate information that is
rarely needed.

=== REFERENCES ===
None.

=== APPLIES TO ACTIVITIES ===
[[IDEF Functional Model REGISTRATION|REGISTRATION]],
[[IDEF Functional Model CREDENTIALING|CREDENTIALING]],
[[IDEF Functional Model AUTHENTICATION|AUTHENTICATION]],
[[IDEF Functional Model AUTHORIZATION|AUTHORIZATION]],
[[IDEF Functional Model INTERMEDIATION|INTERMEDIATION]]

=== KEYWORDS ===
[[IDEF Keywords CHOICE|CHOICE]],
[[IDEF Keywords CLARITY|CLARITY]], [[IDEF Keywords LANGUAGE|LANGUAGE]], [[IDEF Keywords OPTIONS|OPTIONS]], [[IDEF Keywords USABILITY|USABILITY]]

----
----
Quick Links: [[SALS]] | [[Baseline Functional Requirements v1.0]] | [[Glossary]] |

----
----
[[Category:User Experience]]

Usable Req 3 - Revision history

Tomjones at 22:50, 12 October 2018