The design follows branding or style guides that dictate the use of logos, color, and typography.
The design follows a cohesive set of human interface guidelines or design patterns.
Naming conventions are consistent across pages and widgets.
Layouts and page elements have a cohesive look and feel.
Similar interactions and design patterns behave consistently.
The design meets minimum font size legibility guidelines.
The design meets guidelines for minimum contrast between foreground, text and background.
Visual information is 'double-coded' for accessibility by users with color blindness or other visual impairments.
The design meets guidelines for minimum target size for mouse and touch targets.
The design meets W3C's Web Content Accessibility Guidelines (WCAG) for users of screen readers.
The design meets minimum font size legibility guidelines.
Undo functions prevent major data loss and unintended consequences.
Error messages include instructions for recovery.
Version control, history or archiving functions are built into data intensive or collaborative workflows.
The system mitigates impact of catastrophic errors, crashes, and network outages.
Lists of critical choices (menu options, navigation categories) are visible in a single view, or limited to <10 items.
The system 'does the math' for the user.
Microcopy and microinteractions provide ongoing feedback to the user.
Long strings of text or numbers (security codes, phone numbers) are visually chunked or masked.
Security systems reduce need for spontaneous recall by utilizing password best practices, 2-step-authentication, or single sign-on.
Navigation hierarchy is no more than 3 or 4 levels deep.
Layouts are responsive, or optimized for the screen size of target devices.
Navigation breadcrumbs, progress trackers, and keyboard shortcuts improve findability.
Autocomplete, auto-detect and other accelerators improve task speed.
Auto-save and/or cookies maintain session state and prevent accidental data loss.
Branded vocabulary, internal language, and marketing jargon is used sparingly, and absent from navigation, menus, and buttons.
Technical or system jargon is absent from error messages and other microcopy.
Acronyms include access to definitions, and appear in narrative content only.
Technical, legal, and other potentially difficult-to-understand content is written in plain language.
Content readability level is appropriate for the target audience(s).