CARMEL UX Guidelines & Criteria
Each guideline has been operationalized to include 5 key criteria for a multi-faceted evaluation.
-
Consistency
- Style guides
The design follows branding or style guides that dictate the use of logos, color, and typography. - Design systems
The design follows a cohesive set of human interface guidelines or design patterns. - Naming conventions
Naming conventions are consistent across pages and UI elements. - Look & feel
Layouts and page elements have a cohesive look and feel. - Interactions
Similar interactions (e.g. transitions, widget states) behave consistently.
- Style guides
-
Accessibility
- Font size
The design meets minimum font size legibility guidelines. - Contrast
The design meets guidelines for minimum contrast between text and background. - Double coding
Visual information is ‘double-coded’ for accessibility by users with color blindness or other visual impairments. - Target size
The design meets guidelines for minimum target size for mouse and touch targets. - Screen Readers
The design meets W3C’s Web Content Accessibility Guidelines (WCAG) for users of screen readers.
- Font size
-
Recovery
- Confirmation dialogs
Destructive or high-impact actions require confirmation. - Undo functions
Undo functions prevent major data loss and unintended consequences. - Error messages
Error messages include instructions for recovery. - Version control
Version control, history or archive functions are built into data intensive or collaborative workflows. - System recovery
The system mitigates impact of catastrophic errors, crashes, and network outages.
- Confirmation dialogs
-
Memory
- Limited choices
Lists of critical choices (menu options, navigation categories) are visible in a single view, or limited to <10 items. - Automatic calculations
The system ‘does the math’ for the user. - Feedback
Microcopy and microinteractions provide ongoing feedback to the user. - Chunking and masking
Long strings of text or numbers (security codes, phone numbers) are visually chunked or masked. - Security practices
Security systems reduce need for spontaneous recall by utilizing password best practices, 2-step-authentication, or single sign-on.
- Limited choices
-
Efficiency
- Shallow navigation
Navigation hierarchy is no more than 3 or 4 levels deep. - Responsive layouts
Layouts are responsive, or optimized for the screen size of target devices. - Navigation shortcuts
Navigation breadcrumbs, progress trackers, and keyboard shortcuts improve findability. - Accelerators
Autocomplete, auto-detect and other accelerators improve task speed. - Autosave
Auto-save and/or cookies maintain session state and prevent accidental data loss.
- Shallow navigation
-
Language
- Internal language
Branded vocabulary, internal language, and marketing jargon is used sparingly, and absent from navigation, menus, and buttons. - Technical jargon
Technical or system jargon is absent from error messages and other microcopy. - Acronyms
Acronyms include access to definitions, and appear in narrative content only. - Plain language
Technical, legal, and other potentially difficult-to-understand content is written in plain language. - Readability level
Content readability level is appropriate for the target audience(s).
- Internal language
CARMEL UX Design Guidelines by Eva Kaniasty is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License.
Based on a work at https://www.nngroup.com/articles/ten-usability-heuristics/.