Skip to Content
MOCAP Website UX Research Report - December 2025
DocsExecution GuidesInteraction Guides

Interaction Guides

Purpose

This section defines consistent interaction behaviors that apply across all pages and components. Interaction patterns establish predictable user experiences that reduce cognitive load and build trust.

Interaction patterns answer: How should the platform respond to user actions?

These patterns complement Component Specifications (Section 12) by defining behaviors that span multiple components and contexts.


Top 5 Expectations

CrazyEgg analysis identified 5 user expectations that must help shape the website architecture.

1. Data Must Be Manipulable

Users expect to sort, filter, search, and export product data. Static displays violate fundamental mental models formed by decades of spreadsheet use.

ExpectationImplementation
Sort columnsClick header to sort ascending/descending
Filter resultsAttributes filtering with instant updates
Search within resultsSearch bar scoped to current context
Export dataDownload filtered results as CSV/PDF

Research basis: “11-12% of all table interactions result in dead clicks” because current tables are static. Engineers and procurement specialists expect spreadsheet-like manipulation.

2. Actions Must Confirm

Every user action must receive immediate, visible feedback. Silent interfaces erode trust and stall conversion.

Action TypeRequired Feedback
Button clickVisual state change (pressed, loading)
Form submissionLoading state → Success/error message
Cart additionToast notification + cart badge update
Filter selectionResults count update + filter chip
NavigationPage transition or content update

Research basis: “Submit button clicked multiple times per user” because forms provide no loading or success state. “Add to Cart actions lack confirmation” across both MOCAP and Cleartec/Beckett sites.

3. Images Must Function

Product images are navigation and evaluation tools, not decoration. Non-interactive images generate rage clicks.

Image ContextRequired Functionality
Category tilesEntire tile clickable to category page
Product thumbnailsClick to view product detail
Gallery imagesZoom on click/hover
Variant imagesSwitch main image on click

Research basis: “61+ clicks on main image (mostly dead), 8 rage clicks” on RVC product page. “180 thumbnail clicks” on SBT page. Users treat images as interactive controls.

4. Complexity Must Be Guided

Users cannot infer technical parameters without help. Configurators need explicit guidance, tooltips, and examples.

Complexity LevelGuidance Pattern
Simple selectionClear labels, visual options
Technical parametersTooltips explaining each option
Multi-step configurationProgress indicator, step validation
Size/fit decisionsMeasurement guides, fit calculators

Research basis: Customer survey feedback about tube terminology confusion: “The nomenclature was all new to me.” Stakeholders requested “Measurement guides and tooltips” (8.0 MoSCoW score).

5. Friction Must Be Minimal

B2B users are task-focused and time-constrained. Every extra click, unclear state, or missing confirmation increases abandonment risk.

Friction SourceMitigation
Extra stepsCombine related actions, eliminate redundant pages
Unclear statesVisible feedback for all selections
Missing confirmationToast notifications, success messages
Forced registrationGuest checkout for first-time buyers
Repeated data entrySave preferences, remember selections

Research basis: Users follow task-focused model: “find product → select size → convert → leave.” 75-85% never reach supporting content placed below the fold.


Feedback Patterns

Immediate Feedback

All interactive elements must respond instantly to user input.

ElementHover StateActive StateCompletion State
ButtonBrightness changeDarker, slight scaleSuccess indicator
LinkUnderline or color changeColor shift-
CheckboxBorder highlightChecked animation-
ToggleBackground shiftPosition change-
Input fieldBorder highlightFocus ringValid/invalid indicator

Loading States

Any action taking longer than 100ms must show a loading indicator.

ContextLoading Pattern
Button clickSpinner replaces or appears beside label
Form submissionButton shows spinner, form disabled
Page navigationProgress bar or skeleton screen
Search querySkeleton results or loading indicator
Filter applicationResults area shows loading overlay
Image loadingSkeleton placeholder with correct aspect ratio

Loading state rules:

  • Never freeze the interface without an indication
  • Allow cancellation for long operations where possible
  • Show progress for operations with known duration
  • Maintain layout stability (no content shift after load)

Success States

All completed actions must confirm success visibly.

ActionSuccess PatternDuration
Add to CartToast: “Added to cart” + View Cart link4 seconds
Form submissionInline success message or redirectPersistent until dismissed
Save actionBrief checkmark animation2 seconds
Filter appliedFilter chip appears, count updatesInstant
Selection madeVisual selection indicatorPersistent

Success message content:

  • Confirm what happened: “T-250 added to cart”
  • Provide next action: “View Cart” or “Continue Shopping”
  • Include an undo option where appropriate

Error States

Errors must be clear, specific, and actionable.

Error TypeDisplay PatternContent
Field validationRed border + inline message below fieldWhat’s wrong + how to fix
Form submissionError summary at top + field highlightsList all issues
System errorModal or inline messageWhat happened + what to do
Network errorToast notificationRetry option
Not foundDedicated page or inline messageSuggestions + alternatives

Error message principles:

  • Explain what went wrong in plain language
  • Avoid technical jargon or error codes shown to users
  • Provide specific guidance to resolve
  • Never blame the user (“Invalid input” → “Please enter a valid email address”)

Progressive Disclosure

Users engage intensely with above-the-fold content but abandon before reaching supporting content. Average scroll depth is 35-45% across all page types.

Content Placement Hierarchy

PriorityContent TypePlacement
CriticalProduct selection, configuration, primary CTAAbove the fold
ImportantKey specifications, stock status, pricingWithin first scroll
SupportingRelated products, guides, cross-sellsOn-demand (expandable)
ReferenceTechnical specs, certifications, policiesTabs, modals, or links

On-Demand Patterns

PatternUse CaseTrigger
Expandable rowAdditional product details in tableClick row or expand icon
TooltipBrief explanation of term or fieldHover (desktop) / Tap (mobile)
ModalDetailed content without page navigationClick “Learn more” or icon
AccordionMultiple content sections, one visible at a timeClick header to expand
Tab panelRelated content categoriesClick tab
DrawerFilters, navigation, secondary contentClick button to slide in

Point-of-Need Information

Critical information must appear where users need it, not in separate sections.

InformationPlacement
Measurement helpIcon beside dimension fields → opens guide
Material guidanceLink in material dropdown → opens comparison
Fit explanationTooltip on size chart headers
Temperature ratingsBadge on high-temp products
Stock statusInline with product row, near Add to Cart
Shipping estimateVisible before checkout commitment

Research basis: “Specs in table: Use tooltips, expandable rows, or modal dialogs” instead of placing below fold where “only 18% reach informational text.”


Breadcrumbs provide orientation and enable navigation up the hierarchy.

RuleImplementation
Always visiblePresent on all pages except homepage
Complete pathShow full hierarchy from homepage
Current pageLast item not linked, visually distinct
Clickable ancestorsAll parent levels are links
TruncationMiddle items truncate on mobile if needed

Example: Home > Products > Caps > Tapered Caps > T-250

Back Navigation

Browser back button must work predictably.

ScenarioExpected Behavior
Filter appliedBack removes filter, stays on page
Modal openedBack closes modal
Tab changedBack returns to previous tab
Page navigationBack returns to previous page
Form submittedBack may show confirmation, not resubmit

Implementation: Use browser history API to manage state changes. URL should reflect filterable/linkable state.

Persistent Elements

Some elements must remain accessible regardless of scroll position.

ElementBehavior
Primary navigationSticky header (desktop), hamburger (mobile)
SearchAlways accessible from header
CartBadge visible, clickable from header
ContactFloating button on mobile, header on desktop
Back to topAppears after scrolling below fold

Form Patterns

Field Interaction

EventResponse
FocusVisible focus ring, label remains visible
InputReal-time character count if limited
BlurValidation runs, error shows if invalid
ValidGreen checkmark (optional), error clears
InvalidRed border, error message below field

Form Layout

PrincipleImplementation
Single columnAll fields stack vertically on mobile
Logical groupingRelated fields grouped with headers
Required indicatorsAsterisk or “Required” label
Optional indicators”(Optional)” suffix where needed
Field orderMost important/common first

Form Submission

StageUser Experience
Before submitValidate all fields, disable submit if invalid
Submit clickedButton shows loading state
ProcessingForm fields disabled, loading visible
SuccessSuccess message, redirect or next action
ErrorError summary, scroll to first error, focus field

Inline Editing

For account and cart contexts, enable editing without page navigation.

ContextPattern
Cart quantityIncrement/decrement buttons or editable field
Shipping addressEdit button → inline form → Save/Cancel
Payment methodEdit button → inline form → Save/Cancel
Profile fieldsEdit button → field becomes editable → Save

Research basis: Debbie Gerlach: “Even though it looks like you can edit it, it won’t let you. You must back out of the cart and then add or change.” Inline editing prevents this friction.


Selection Patterns

Single Selection

For choosing one option from a set.

PatternUse CaseBehavior
Radio buttons2-5 visible optionsOne selected at a time
Dropdown6+ options or limited spaceOpens list, one selection
Segmented control2-4 options, prominent choiceToggle between options
Card selectionVisual options with detailsClick selects, shows active state

Multiple Selection

For choosing multiple options.

PatternUse CaseBehavior
CheckboxesOptions listIndependent toggles
Chip/tag selectionCompact multi-selectClick to add/remove
Multi-select dropdownMany options, space limitedCheckboxes in dropdown
Transfer listLarge sets, need organizationAdd/remove between lists

Product Variant Selection

Special patterns for product configuration.

Variant TypePattern
ColorVisual swatches with border on selection
SizeButtons or dropdown with size labels
MaterialDropdown with material name + key property
QuantityInput field with increment/decrement buttons

Selection feedback:

  • Selected option visually distinct (background, border, checkmark)
  • Price updates if variant affects pricing
  • Stock status updates if variant affects availability
  • Image updates if variant affects appearance

Cart Patterns

Add to Cart

StepUser Experience
Click Add to CartButton shows loading briefly
Item addedToast notification with product name
Cart updatesCart icon badge increments
Continue shoppingStay on page, toast has “View Cart” link

Mini Cart

Accessible from the header without navigating to the cart page.

ElementContent
TriggerCart icon click or hover
DisplayDropdown or slide-in panel
ContentItem list (thumbnail, name, qty, price), subtotal
ActionsView Cart, Checkout
LimitShow first 3-5 items + “and X more”

Cart Page

SectionContent
Item listProduct details, quantity editor, remove button
SummarySubtotal, estimated tax, estimated shipping, total
ActionsContinue Shopping, Proceed to Checkout
Cross-sells”Frequently bought together” or “You may also need”

Quantity Updates

InputBehavior
Increment (+)Increase by 1, check max
Decrement (−)Decrease by 1, minimum 1
Direct inputAccept valid integers, validate on blur
RemoveConfirm if qty > 1, immediate if qty = 1

Package quantity alignment: If products have minimum order quantities or packaging units, show helper text and auto-adjust to valid quantities.


Checkout Patterns

Checkout Flow

Step-based checkout with clear progress indication.

StepContentValidation
1. ContactEmail, phone (for order updates)Email format, required fields
2. ShippingAddress, method, carrier optionsAddress validation, method selection
3. PaymentPayment method, billing addressCard validation, terms acceptance
4. ReviewOrder summary, final confirmationAll previous steps complete

Progress Indicator

StateVisual Treatment
Completed stepCheckmark, muted or green
Current stepHighlighted, numbered
Future stepMuted, numbered
ClickableCompleted steps clickable to return

Guest vs. Account Checkout

User TypeExperience
GuestFull checkout flow, account creation offered at end
Logged inPre-filled contact and shipping, saved payment options
New accountCreate account during checkout or after

Research basis: Competitive analysis: “Open checkout (Caplugs, Fastenal, Rose): Guest allowed = 20-35% higher first-time conversion.”

Order Confirmation

ElementContent
Success message”Thank you for your order”
Order numberProminently displayed
Order summaryItems, quantities, prices
Shipping infoAddress, method, estimated delivery
Next steps”You’ll receive an email confirmation”
ActionsPrint, Track Order, Continue Shopping

Search Patterns

Search Interaction Flow

StageBehavior
Focus on searchInput expands (desktop), keyboard appears (mobile)
Typing (3+ chars)Autocomplete suggestions appear after 150ms
Select suggestionNavigate directly to suggested item/page
Submit searchNavigate to results page
No resultsSuggestions, browse links, contact option

Autocomplete Behavior

InputResponse
Exact SKU matchTop suggestion with “View Product” action
Partial SKUList of matching part numbers
Category termCategory suggestion with product count
Application termApplication page suggestion
No matches”No suggestions” + submit to search anyway

Search Results Interaction

ActionResponse
Click productNavigate to product detail page
Add to Cart (if shown)Add with default options, toast confirmation
Apply filterResults update, filter chip appears
Sort changeResults reorder, URL updates
Load moreAdditional results append, button updates

Mobile-Specific Patterns

Touch Targets

ElementMinimum Size
Buttons44×44px
Links in text44px touch area (padding if needed)
List items48px height minimum
Close buttons44×44px
Form fields44px height minimum

Mobile Navigation

PatternUsage
Hamburger menuPrimary navigation access
Bottom navigationKey actions (Home, Search, Cart, Account)
DrawerFilters, secondary navigation
Back buttonReturn to previous screen

Mobile Forms

AdaptationImplementation
Input typesUse appropriate keyboard (email, number, tel)
LabelsAlways visible above the field (not placeholder only)
LayoutSingle column, full-width fields
SubmitLarge button, bottom of form

Mobile Tables

AdaptationImplementation
Row to cardEach row becomes a stacked card
Priority columnsMost important data visible, rest expandable
Horizontal scrollAlternative for data-dense tables
SortingDropdown selector instead of header clicks

Research basis: “Mobile: Each row becomes a stacked card” from Caplugs benchmark. Only 3 of 14 competitors have usable mobile tables.


Error Prevention Patterns

Validation Timing

Validation TypeTiming
Format validationOn blur or after brief pause in typing
Required fieldsOn blur and on submit attempt
Cross-field validationOn submit
Server validationAfter form submission

Disabled States

Use disabled states to prevent invalid actions.

ScenarioDisabled Element
No size selectedAdd to Cart button
Required field emptySubmit button (with visual indication)
Out of stockAdd to Cart button (with “Out of Stock” label)
Invalid quantityCheckout button

Confirmation Dialogs

Require confirmation for destructive or significant actions.

ActionConfirmation
Remove item from cart”Remove [Product]?” Yes/No
Cancel order”Are you sure? This cannot be undone.”
Delete saved address”Delete this address?” Yes/No
Clear all filtersNo confirmation (easily reversible)

Undo Capability

Where possible, allow undo instead of confirmation.

ActionUndo Pattern
Remove from cartToast with “Undo” button (5 seconds)
Apply all filters”Clear All” button
Form changes”Discard Changes” option

Accessibility Patterns

Keyboard Navigation

KeyAction
TabMove to next focusable element
Shift+TabMove to previous focusable element
EnterActivate button/link
SpaceToggle checkbox, activate button
Arrow keysNavigate within components (tabs, menus)
EscapeClose modal, dropdown, popover

Focus Management

ScenarioFocus Behavior
Modal opensFocus moves to modal, trapped within
Modal closesFocus returns to trigger element
Dropdown opensFocus on first option
Error occursFocus on first error field
Page loadsFocus on main content or skip link target

Summary: Pattern Priority

Based on research severity and frequency:

PriorityPattern CategoryResearch Driver
CriticalFeedback (loading, success, error)Universal feedback gap, rage clicks
CriticalForm validation and submissionMultiple clicks, form confusion
CriticalAdd to Cart flowNo confirmation, trust erosion
HighProgressive disclosure75-85% don’t scroll to content
HighSearch interaction73% priority, broken current search
HighMobile adaptation20% of traffic, 3/14 competitors usable
MediumCheckout flowAddress editing friction
MediumError preventionDestructive actions, invalid states