chevron-left

Kaniasty's

Kaniasty's

CARMEL Guidelines

1. Consistency
1. Consistency
1. Consistency
1.1. Consistency>Style guides
1.1. Consistency>Style guides
1.1. Consistency>Style guides

The design follows branding or style guides that dictate the use of logos, color, and typography.

The design follows branding or style guides that dictate the use of logos, color, and typography.

The design follows branding or style guides that dictate the use of logos, color, and typography.

1.2. Consistency>Design patterns
1.2. Consistency>Design patterns
1.2. Consistency>Design patterns

The design follows a cohesive set of human interface guidelines or design patterns.

The design follows a cohesive set of human interface guidelines or design patterns.

The design follows a cohesive set of human interface guidelines or design patterns.

1.3. Consistency>Naming conventions
1.3. Consistency>Naming conventions
1.3. Consistency>Naming conventions

Naming conventions are consistent across pages and widgets.

Naming conventions are consistent across pages and widgets.

Naming conventions are consistent across pages and widgets.

1.4. Consistency>Look & feel
1.4. Consistency>Look & feel
1.4. Consistency>Look & feel

Layouts and page elements have a cohesive look and feel.

Layouts and page elements have a cohesive look and feel.

Layouts and page elements have a cohesive look and feel.

1.5. Consistency>Interactions
1.5. Consistency>Interactions
1.5. Consistency>Interactions

Similar interactions and design patterns behave consistently.

Similar interactions and design patterns behave consistently.

Similar interactions and design patterns behave consistently.

2. Accessibility
1. Visibility of system status
2.1. Accessibility>Font size

The design meets minimum font size legibility guidelines.

2.2 Accessibility>Contrast

The design meets guidelines for minimum contrast between foreground, text and background.

2.3. Accessibility>Double coding

Visual information is 'double-coded' for accessibility by users with color blindness or other visual impairments.

2.4. Accessibility>Target size

The design meets guidelines for minimum target size for mouse and touch targets.

2.5. Accessibility>Screen Readers

The design meets W3C's Web Content Accessibility Guidelines (WCAG) for users of screen readers.

3. Recovery
1. Visibility of system status
3.1. Recovery>Confirmation dialogs

Destructive or high-impact actions require confirmation.

3.2. Recovery>Undo functions

Undo functions prevent major data loss and unintended consequences.

3.3. Recovery>Error messages

Error messages include instructions for recovery.

3.4. Recovery>Version control

Version control, history or archiving functions are built into data intensive or collaborative workflows.

3.5. Recovery>System recovery

The system mitigates impact of catastrophic errors, crashes, and network outages.

4. Memory
1. Visibility of system status
4.1. Memory>Limited choices

Lists of critical choices (menu options, navigation categories) are visible in a single view, or limited to <10 items.

4.2. Memory>Automatic calculations

The system 'does the math' for the user.

4.3. Memory>Feedback

Microcopy and microinteractions provide ongoing feedback to the user.

4.4. Memory>Chunking and masking

Long strings of text or numbers (security codes, phone numbers) are visually chunked or masked.

4.5. Memory>Security practices

Security systems reduce need for spontaneous recall by utilizing password best practices, 2-step-authentication, or single sign-on.

5. Efficiency
1. Visibility of system status
5.1. Efficiency>Shallow navigation

Navigation hierarchy is no more than 3 or 4 levels deep.

5.2. Efficiency>Responsive layouts

Layouts are responsive, or optimized for the screen size of target devices.

5.3. Efficiency>Navigation shortcuts

Navigation breadcrumbs, progress trackers, and keyboard shortcuts improve findability.

5.4. Efficiency>Accelerators

Autocomplete, auto-detect and other accelerators improve task speed.

5.5. Efficiency>Autosave

Auto-save and/or cookies maintain session state and prevent accidental data loss.

6. Language
1. Visibility of system status
6.1. Language>Internal language

Branded vocabulary, internal language, and marketing jargon is used sparingly, and absent from navigation, menus, and buttons.

6.2. Language>Technical jargon

Technical or system jargon is absent from error messages and other microcopy.

6.3. Language>Acronyms

Acronyms include access to definitions, and appear in narrative content only.

6.4. Language>Plain language

Technical, legal, and other potentially difficult-to-understand content is written in plain language.

6.5. Language>Readability level

Content readability level is appropriate for the target audience(s).