SC Shortname: Familiar Design (Minimum)

SC Text

Familiar design (Minimum): Help, navigation to help and search forms are easily identifiable and available to the user in one or more of the following ways:

• Platform specific: A platform specific user interface design.
• Adaptive interface: An adaptive user interface design that can be personalized.
• User interface from a prior version: A user interface design that was used successfully by users in a prior version of the application.

Exception: The style is an essential part of the main function of the site, such as for a game.

Suggestion for Priority Level:

A

Related Glossary additions or changes

Help: a mechanism provided to give a user access to help content, a support page or a support function

What Principle and Guideline the SC falls within.

Principle 3, Guideline 3.2: Predictable

Description and Benefits

Many people cannot easily learn new design metaphors or remember things which they have learned for example, people with Mild Cognitive Impairment (MCI) or dementia. Without these skills it can be much harder or impossible to:

• Locate desired items to interact with and
• Know what the interaction may do.

However at a minimum level (Conformance level A) as many users as possible should be able to reach help and a search mechanism.

Using a familiar design, terms and symbols is key to being able to use the Web for people who cannot remember new symbols for example, people with memory related impairments like dementia. Therefore, this success criteria addresses the user need for things to be familiar including:

• Location of elements
• Symbols

When an author is creating a platform specific UI, the look and feel of these features should appear and operate in a manner which is consistent with the platform or be capable of being personalized. The only exception would be a design that has been proven through user testing to be intuitive and easy to use even though it departs from that of the platform.

COGA is also working on standardizing the relevant semantics and personalization settings to support alternative implementations.

 

See User research

Gap analysis

• User needs Table:6, 7,8 and 9
• Background research document
• Semantics for adaptive interfaces

Related Resources

Resources are for information purposes only, no endorsement implied.

• iOS Human Interface Guidelines
• Xcode - Interface Builder
• Android User Interface Guidelines
• Microsoft Windows - UX Checklist
• Nielsen Norman Group - The Need for Web Design Standards
• Background research document - 3.7.6.1 Consistency

Testability

Test procedure

Identify any help, navigation to help and search forms . Where item 1, 2 or 3 can be applied, confirm that either item 1, 2 or 3 below is true for each help and search element:

1. The icons and navigation conform to a standard identified in a WCAG technique or in the UI standard of the native platform

2. Semantics are used to enable personalization

3. A roll back option to the previous interface that has been in use by the user is available (in this case the roll back must be to a user interface that has been previously widely used)

Techniques

The more predictable your content is the easier it is to know how to use it.

• Using standard Web layout design, so it is easy to find the help and search. In 2015 for English sites this includes:
  • The location of the search box is in the top right hand corner
  • A question mark as the graphical symbol for help, etc
  • Using COGA semantics such that search and help components and icons are programmatic determinable and that their positions can be standardized via personalization

  Following the standard user interface guidelines for a specific platform. See also:

  • iOS UI Bars
  • iOS UI Views
  • iOS UI Controls

  Follow the standard user interface guidelines for a specific platform.

working groups notes (optional)