E-Commerce

Chapter 5
User Experience, Accessibility and Conversion Design

Bachelors Program in IT
E-Commerce   •   Bachelor

User Experience, Accessibility and Conversion Design

Introduction

In e-commerce, a customer does not experience a store as a collection of isolated web pages. The customer experiences a journey: discovering a product, understanding its value, assessing risk, adding it to a cart, completing payment, and receiving confirmation. User experience (UX) design coordinates this journey so that it is useful, understandable, efficient, trustworthy, and inclusive.

Conversion design applies UX principles to commercially meaningful actions, such as product views, registrations, purchases, subscriptions, and enquiries. It does not mean manipulating users into buying. Effective conversion design reduces unnecessary effort, clarifies choices, communicates value honestly, and removes barriers that prevent customers from completing an intended task.

Accessibility is an essential part of this work. An inaccessible store excludes users, increases legal and reputational risk, and often creates poor experiences for everyone. Responsive design, clear navigation, effective search, usable product pages, reliable checkout, personalization, prototyping, and evidence-based optimization must therefore be treated as one integrated discipline.

Learning Objectives

By the end of this chapter, students should be able to:

  1. Explain the relationship between UX, usability, accessibility, and conversion.
  2. Design product discovery, navigation, search, product pages, carts, and checkout flows.
  3. Apply responsive and mobile-first design principles.
  4. Identify accessibility requirements and evaluate interfaces using recognized principles.
  5. Use personas, journey maps, wireframes, prototypes, and usability tests.
  6. Calculate and interpret basic conversion metrics.
  7. Evaluate personalization, experimentation, AI assistance, and ethical risks.
  8. Recommend improvements for an e-commerce interface using evidence.

1. Foundations of E-Commerce UX

1.1 UX, usability, and conversion

UX is the total set of perceptions and responses that result from a person’s use or anticipated use of a product, service, or system. It includes functionality, emotional response, trust, speed, accessibility, content quality, and service recovery.

Usability is narrower. It concerns whether specified users can achieve specified goals effectively, efficiently, and satisfactorily in a particular context. A usable checkout allows a customer to enter information, correct errors, understand costs, and complete payment without unnecessary difficulty.

Conversion is the completion of a defined business or user goal. For an online retailer, the primary conversion may be a purchase, but useful secondary conversions include product comparison, account creation, email subscription, or store-location lookup.

A basic conversion rate is:

Conversion rate = (Number of conversions ÷ Number of eligible visits) × 100%

The denominator must be defined carefully. If it is sessions, the result is a session conversion rate; if it is unique users, it is a user conversion rate. These measures should not be mixed. Conversion rate alone does not prove that a design caused improvement because traffic source, price, seasonality, inventory, and promotions may also change.

1.2 Mental models and cognitive effort

Users approach an interface with mental models formed by previous experiences. They expect a logo to lead to the home page, a magnifying-glass icon to represent search, a cart icon to show selected items, and a prominent button to perform the primary action. Designs that violate familiar conventions increase cognitive effort.

Cognitive load is commonly discussed as:

  • Intrinsic load: difficulty inherent in the task, such as comparing technical specifications.
  • Extraneous load: difficulty created by poor presentation, confusing labels, or unnecessary steps.
  • Germane effort: mental effort used to understand and complete the task.

Good e-commerce design reduces extraneous load without hiding important information. Progressive disclosure can present essential information first while allowing users to inspect details when needed.

1.3 Trust as a design property

Customers must often provide money, identity information, and an address to an unfamiliar organization. Trust is supported by transparent pricing, recognizable payment methods, accurate stock information, clear returns policies, contact details, reviews with context, secure technical infrastructure, and consistent visual and verbal communication. Trust marks alone are weak if the surrounding experience appears deceptive or incomplete.

2. Product Discovery and Information Architecture

Product discovery includes all ways users find merchandise: menus, category pages, search, recommendations, filters, editorial content, advertising, and links from campaigns. Information architecture organizes products and content so users can understand where they are and what choices are available.

2.1 Navigation design

A navigation system should answer three questions quickly:

  1. Where am I?
  2. What can I find here?
  3. What should I do next?

Common structures include global navigation, local category navigation, breadcrumbs, filters, sorting controls, and footer navigation. Category labels should reflect customers’ language rather than internal departmental terminology. For example, “Running shoes” may be more understandable than “Athletic footwear—lower extremity.”

Navigation should communicate current location through headings, selected states, breadcrumbs, or visual emphasis. However, selected states must not rely on color alone. A text label, icon, border, or programmatic state should also identify the current category.

2.2 Category pages

A category page should support scanning and comparison. Important elements include:

  • a descriptive page title;
  • a brief explanation where the category is unfamiliar;
  • product count or result status;
  • filters and sorting controls;
  • consistent product cards;
  • price, availability, key attributes, and ratings where relevant;
  • pagination or an accessible alternative such as “load more”;
  • controls for list or grid presentation where useful.

Product cards should not hide essential information behind hover effects, especially on touch devices. If quick actions are provided, their labels must identify the product affected.

2.3 Search and filtering

Search is especially important when the catalog is large or users know what they want. A robust search system should tolerate spelling errors, synonyms, alternate product names, singular and plural forms, and common abbreviations. Search results should explain what was searched and provide useful recovery options when no results are found.

Filters should be based on meaningful attributes. A filter for “size” should expose available sizes rather than all possible sizes if unavailable options cannot produce results. Multi-select filters are useful when users may accept several values; single-select controls are suitable when only one value makes sense.

Sorting and filtering are different. Filtering removes products that do not meet criteria. Sorting changes order, such as by relevance, price, rating, or newest arrival. “Best” or “recommended” sorting should be explained sufficiently to avoid misleading users.

3. Product Pages and Decision Support

The product page is where discovery becomes evaluation. It should answer the customer’s practical questions before the customer commits effort or money.

3.1 Essential product information

A well-designed product page commonly includes:

  • product name and concise value proposition;
  • high-quality images, with zoom and alternative text;
  • price, discounts, and currency;
  • availability and expected delivery information;
  • variants such as size, color, capacity, or configuration;
  • prominent but unambiguous add-to-cart action;
  • specifications and dimensions;
  • usage guidance and compatibility information;
  • reviews and questions;
  • returns, warranty, and support information.

The order of information should match decision needs. A product with complex compatibility requirements requires prominent technical details; a fashion product may require size guidance, material, fit, and multiple views.

3.2 Images, media, and content

Images should show the product in sufficient detail and, where appropriate, in context. Alternative text should communicate the information needed to understand the image, not merely repeat “product image.” Decorative images can have empty alternative text so screen readers skip them. Videos require captions, and important visual information should also be available in text.

Content must be accurate. Artificially generated or enhanced images may create ethical and legal problems if they imply features, colors, scale, or results that the product does not possess.

3.3 Reviews and social proof

Reviews reduce uncertainty but can also mislead. A credible review system should identify verified purchases where applicable, retain negative reviews subject to clear moderation rules, distinguish incentivized reviews, and allow users to evaluate relevance. Aggregate ratings should not conceal a very small sample or a distribution of scores.

4. Cart and Checkout Design

The cart is both a planning space and a commitment checkpoint. It should display product identity, selected variants, quantity controls, price, discounts, delivery costs, taxes where applicable, and the expected total. Quantity changes should provide immediate feedback and preserve the user’s selections.

Checkout should minimize avoidable friction while preserving necessary controls. A common sequence is:

  1. Contact information.
  2. Delivery address and method.
  3. Payment details.
  4. Review and confirmation.
  5. Order confirmation and next steps.

The exact sequence depends on the business model and payment method. Guest checkout should generally be available unless there is a strong, clearly communicated reason to require an account. Account creation can be offered after purchase, when the customer has already received value.

4.1 Error prevention and recovery

Errors should be prevented where possible through input constraints, examples, appropriate keyboard types, address lookup with user confirmation, and clear field labels. Error messages should state what went wrong and how to correct it. A message such as “Invalid input” is less useful than “Enter a valid postal code, for example 10001.” Errors must be associated programmatically with fields so assistive technologies can announce them.

Do not erase valid form data after an error. Preserve entered information, identify the first or most important error, and allow correction without forcing users to restart.

4.2 Total cost and surprise avoidance

Unexpected delivery fees, taxes, service charges, or subscription commitments are major causes of abandonment. The interface should communicate material costs before payment and distinguish one-time charges from recurring charges. Preselected add-ons and hidden insurance can undermine informed consent.

5. Responsive and Mobile-First Design

Responsive design adapts layout, interaction, content, and media to different viewport sizes and input methods. It is not merely shrinking a desktop page.

A mobile-first process begins with essential content and actions, then progressively enhances the layout for larger screens. It encourages prioritization, but mobile designs must not omit information necessary for an informed decision.

Important practices include:

  • flexible layouts rather than fixed-width assumptions;
  • readable text and adequate line spacing;
  • touch targets large enough to activate reliably;
  • controls that work with touch, keyboard, and assistive technology;
  • avoidance of horizontal scrolling for ordinary content;
  • optimized images and deferred loading where appropriate;
  • stable layouts that minimize unexpected movement;
  • visible focus indicators;
  • testing on real devices and variable network conditions.

Performance is part of UX. A visually attractive page that takes too long to become usable may produce abandonment. Performance should be assessed with representative devices, connections, and content rather than only a fast development computer.

6. Accessibility by Design

Accessibility means that people with diverse abilities can perceive, operate, understand, and interact with a product. It benefits users with permanent disabilities, temporary impairments, situational limitations, older users, and users on constrained devices.

The Web Content Accessibility Guidelines (WCAG) organize accessibility around four principles:

  • Perceivable: information is available through more than one sensory channel where necessary.
  • Operable: users can operate controls with available input methods, including keyboard access.
  • Understandable: content and interactions are predictable and comprehensible.
  • Robust: content works with current and future user agents and assistive technologies.

6.1 Practical requirements

Accessible e-commerce interfaces should provide:

  • meaningful page titles and heading hierarchy;
  • keyboard access to all functions;
  • visible and logical focus order;
  • sufficient color contrast, without relying on color alone;
  • labels for form fields and accessible names for controls;
  • text alternatives for informative images;
  • captions and transcripts for relevant media;
  • clear error messages and status announcements;
  • properly marked-up tables, lists, buttons, and links;
  • appropriate handling of dynamic content such as filters and cart updates.

Accessibility should be tested through automated tools, manual keyboard testing, screen-reader testing, zoom and reflow testing, and participation by people with disabilities. Automated testing detects only a portion of accessibility problems.

Legal obligations vary by jurisdiction and sector. Organizations should consult applicable disability-discrimination, consumer-protection, privacy, and digital-service laws. Compliance is not a substitute for inclusive design.

7. Personalization and Ethical Conversion Design

Personalization can use context such as location, previous behavior, purchase history, or stated preferences to improve relevance. Examples include recently viewed products, recommendations, localized delivery information, and remembered preferences.

Personalization should be:

  • relevant rather than intrusive;
  • explainable when it materially affects choices;
  • controllable through preference settings;
  • based on lawful and proportionate data use;
  • tested for bias and unequal outcomes.

Dark patterns are interface practices that steer, pressure, confuse, or trap users—for example, hidden cancellation, disguised advertising, false urgency, or difficult refusal of optional tracking. Such practices may increase short-term metrics while damaging trust and creating regulatory risk. Ethical conversion design improves the user’s ability to make a voluntary, informed decision.

Privacy design should follow data minimization, purpose limitation, secure processing, retention controls, and meaningful consent where required. A recommendation engine should not infer sensitive characteristics unnecessarily or expose personal information through shared devices.

8. Prototyping, Testing, and Conversion Optimization

8.1 From requirements to prototype

A practical design process is iterative:

  1. Research users, tasks, constraints, and business goals.
  2. Define personas or behavior-based segments cautiously.
  3. Map the customer journey and identify points of uncertainty.
  4. Sketch information architecture and task flows.
  5. Create low-fidelity wireframes.
  6. Test structure and language before investing in visual polish.
  7. Build a higher-fidelity prototype.
  8. Conduct usability and accessibility evaluation.
  9. Implement, measure, and improve.

A persona is a research-informed representation of a meaningful user group, not a fictional stereotype. Journey maps should include user goals, actions, questions, emotions, channels, and organizational touchpoints.

8.2 Usability testing

A usability test gives representative participants realistic tasks and observes behavior. A facilitator should avoid teaching the interface during the task. Useful observations include hesitation, errors, workarounds, misunderstood labels, abandonment, and comments indicating incorrect mental models.

A small qualitative test can reveal severe problems, but it should not be treated as a statistically representative estimate of all users. Accessibility testing should include participants who use assistive technologies.

8.3 A/B testing and experimentation

In an A/B test, users are assigned to a control or treatment experience and a predefined outcome is compared. Valid interpretation requires a clearly defined metric, appropriate assignment, adequate sample size, stable exposure, and attention to other changes occurring during the test.

A practical evaluation set includes:

StageExample metricMain question
DiscoverySearch success, product-list click-throughCan users find relevant products?
EvaluationProduct-detail engagement, variant selectionCan users assess the product?
CartAdd-to-cart rate, cart error rateCan users prepare an order?
CheckoutCompletion rate, field error rateCan users complete payment?
After purchaseSupport contacts, returns, repeat purchaseDid the experience create lasting value?

A useful funnel diagnostic is:

Stage conversion rate = (Users reaching the next stage ÷ Users entering the current stage) × 100%

Suppose 10,000 sessions view a product, 1,200 add an item to the cart, and 480 complete payment. The product-to-cart rate is (1,200 ÷ 10,000) × 100% = 12%. The cart-to-purchase rate is (480 ÷ 1,200) × 100% = 40%. The overall product-view-to-purchase rate is (480 ÷ 10,000) × 100% = 4.8%. These figures identify where users leave, but they do not by themselves explain why.

Revenue per visitor can be calculated as:

Revenue per visitor = Total revenue ÷ Number of visitors

This metric is useful only when revenue, visitor definition, attribution window, refunds, and currency treatment are consistently specified. Optimization should consider profit, returns, customer support costs, and customer welfare rather than conversion alone.

9. Applied Case: Illustrative Redesign of GreenBasket

Background

GreenBasket is a fictional online retailer selling household refill products. Its desktop traffic is strong, but mobile users frequently abandon checkout. Customer support reports questions about delivery fees, product compatibility, and subscription cancellation.

Problem

Analytics show that many users reach product pages but fail to add products to the cart. Mobile checkout has a high address-error rate. A review also finds that the delivery charge appears late and that the subscription option is preselected.

Analysis

Research combines session recordings, accessibility review, five moderated usability sessions, and customer-support analysis. The main findings are:

  • product cards do not clearly state package size;
  • search does not recognize common refill synonyms;
  • product pages place compatibility information below extensive promotional content;
  • the checkout form uses weak labels and clears fields after errors;
  • the subscription choice is visually more prominent than the one-time purchase option;
  • delivery cost is shown only after address submission.

Approach and solution

The team restructures categories around customer language, improves synonym handling, adds package-size information to product cards, and places compatibility and delivery information near the purchase controls. It provides a guest checkout, persistent field values, explicit labels, keyboard-accessible error messages, and a clear subscription choice with no preselection. Delivery estimates and charges are shown before final payment confirmation.

A prototype is tested with keyboard users, screen-reader users, mobile users, and customers unfamiliar with the product category. The team then runs a controlled experiment comparing the original and revised checkout while monitoring completion, error rate, refunds, support contacts, and subscription cancellations.

Outcome

The redesigned flow produces fewer form errors and fewer support questions. Purchase completion improves, but the organization also observes that some users select one-time purchases instead of subscriptions. This is not treated as failure: the design has improved informed choice. The business evaluates total contribution margin and retention rather than using subscription uptake as its only success measure.

Learning points

  1. Funnel data identifies locations of difficulty but requires qualitative research for explanation.
  2. Accessibility improvements often improve usability for all customers.
  3. Transparent cost and subscription communication support both trust and sustainable conversion.
  4. Ethical success metrics include customer outcomes, not only immediate revenue.

10. Contemporary Developments and Limitations

Artificial intelligence can support search synonym expansion, product attribute extraction, recommendation, conversational assistance, and automated accessibility checks. It can also generate incorrect product claims, reproduce bias, expose confidential data, or produce inaccessible content. Human review, source traceability, privacy controls, monitoring, and a clear escalation path are essential.

Voice interfaces, visual search, headless commerce, progressive web applications, and composable commerce expand design possibilities. They also increase integration complexity. A visually innovative front end may still fail if inventory, pricing, identity, payment, or fulfillment services provide inconsistent information.

No single metric, design pattern, or accessibility checklist guarantees success. Users differ, contexts change, and commercial outcomes are affected by price, brand, logistics, inventory, and customer service. Design decisions should therefore be treated as hypotheses supported by research and measurement.

Best-Practice Checklist

Before launch, an e-commerce team should verify that:

  • navigation uses understandable categories and communicates location;
  • search supports synonyms, errors, filters, and useful empty states;
  • product pages contain accurate price, availability, variants, delivery, returns, and specifications;
  • cart totals are understandable and complete;
  • checkout supports guest purchase, correction, and error recovery;
  • subscription and optional charges require informed choice;
  • layouts and controls work across screen sizes and input methods;
  • keyboard, screen-reader, zoom, contrast, captions, and reflow tests have been performed;
  • analytics definitions are documented and privacy-compliant;
  • experiments evaluate customer and business outcomes together;
  • AI-generated or personalized content is reviewed for accuracy, fairness, privacy, and accessibility.

Chapter Summary

E-commerce UX is the design of an integrated customer journey from discovery through post-purchase service. Usability reduces unnecessary effort; accessibility ensures that people with diverse abilities can participate; conversion design makes valuable actions clear and trustworthy. Effective information architecture supports navigation, search, filtering, and product comparison. Product pages must communicate value, risk, availability, compatibility, and terms accurately. Carts and checkout should minimize friction, expose total cost, preserve user input, and support error recovery.

Responsive design adapts content and interaction to different devices and contexts. Accessibility requires perceivable, operable, understandable, and robust experiences, supported by automated and human evaluation. Prototyping and usability research help teams discover problems early, while experimentation helps evaluate competing solutions. Metrics such as stage conversion rate and revenue per visitor are useful only when definitions and limitations are understood. Personalization and AI can increase relevance but require privacy, fairness, transparency, human oversight, and resistance to dark patterns. Sustainable conversion is achieved by helping customers make informed decisions, not by coercing them.

Key Terms

UX: The overall perceptions and responses arising from use or anticipated use of a product or service.

Usability: The extent to which specified users achieve goals effectively, efficiently, and satisfactorily.

Accessibility: The design of products usable by people with diverse abilities and assistive technologies.

Conversion: Completion of a defined user or business goal.

Conversion rate: The percentage of eligible visits or users that complete a defined conversion.

Information architecture: Organization and labeling of content, products, and navigation.

Mental model: A user’s expectation of how a system works.

Cognitive load: Mental effort required to understand and operate an interface.

Progressive disclosure: Presenting essential information first and additional detail when needed.

Breadcrumbs: Navigation showing a user’s location within a hierarchy.

Filter: A control that limits results according to selected attributes.

Sorting: Arranging results according to an ordering rule.

Responsive design: Adaptation of layout and interaction to device and context.

Wireframe: A low-detail representation of interface structure.

Prototype: An interactive or static representation used to explore and test a design.

A/B test: Controlled comparison of two interface variants.

Dark pattern: A design practice that manipulates or obstructs informed user choice.

Personalization: Adaptation of content or experience using user or contextual information.

Progressive enhancement: Starting with core functionality and adding capabilities for more capable environments.

Funnel: A sequence of stages through which users progress toward a goal.

Review Questions

Short Answer Questions

  1. Distinguish UX from usability.
  2. Why should category labels use customer language?
  3. Identify four important elements of a product page.
  4. What is the purpose of an accessible error message?
  5. State the four WCAG principles.

Long Answer Questions

  1. Explain how information architecture supports product discovery and comparison.
  2. Discuss the design principles of an effective mobile checkout.
  3. Explain how accessibility can improve both inclusion and commercial performance.
  4. Describe a complete process for prototyping and usability testing an e-commerce feature.
  5. Discuss the ethical risks and governance requirements of personalization and AI recommendations.

Analytical / Application Questions

  1. A store has 20,000 product-page sessions, 2,400 add-to-cart events, and 720 purchases. Calculate the product-to-cart rate, cart-to-purchase rate, and product-view-to-purchase rate. Interpret the largest diagnostic implication.
  2. Audit a fictional checkout that hides delivery charges until payment, requires account creation, clears fields after errors, and preselects insurance. Identify the UX, accessibility, and ethical problems and propose corrections.
  3. Design an experiment for improving search on a large catalog. Define the control, treatment, primary metric, guardrail metrics, sample considerations, and possible threats to validity.

Multiple Choice Questions with Answers

Question 1

Which statement best describes accessibility in e-commerce?

A. Making every page visually identical

B. Ensuring people with diverse abilities can perceive, operate, understand, and use the service

C. Increasing the number of promotional banners

D. Allowing only keyboard users to complete checkout

Correct Answer: B. Ensuring people with diverse abilities can perceive, operate, understand, and use the service

Question 2

What is the main difference between filtering and sorting?

A. Filtering changes order, while sorting removes products

B. Filtering removes products that do not meet criteria, while sorting changes their order

C. They are identical operations

D. Sorting is used only on mobile devices

Correct Answer: B. Filtering removes products that do not meet criteria, while sorting changes their order

Question 3

A store records 5,000 eligible visits and 250 purchases. What is its conversion rate?

A. 2%

B. 5%

C. 20%

D. 25%

Correct Answer: B. 5%

Question 4

Which checkout practice best supports error recovery?

A. Clearing all fields after any error

B. Using the message “Invalid input” for every problem

C. Preserving valid data and explaining how to correct the specific error

D. Removing validation entirely

Correct Answer: C. Preserving valid data and explaining how to correct the specific error

Question 5

Why is guest checkout often recommended?

A. It prevents customers from receiving order information

B. It reduces an unnecessary barrier for customers who do not want an account

C. It eliminates the need for payment security

D. It guarantees repeat purchases

Correct Answer: B. It reduces an unnecessary barrier for customers who do not want an account

Question 6

Which is an example of a dark pattern?

A. Showing the complete order total before payment

B. Providing captions for product videos

C. Making cancellation deliberately difficult while making enrollment easy

D. Using descriptive headings

Correct Answer: C. Making cancellation deliberately difficult while making enrollment easy

Question 7

What does responsive design primarily address?

A. Adapting layout and interaction to different screens and contexts

B. Changing product prices automatically

C. Replacing all text with images

D. Removing accessibility requirements

Correct Answer: A. Adapting layout and interaction to different screens and contexts

Question 8

Which metric measures movement from one funnel stage to the next?

A. Stage conversion rate

B. Color contrast ratio

C. Inventory turnover only

D. Page word count

Correct Answer: A. Stage conversion rate

Question 9

Which statement about automated accessibility testing is most accurate?

A. It detects every accessibility problem

B. It is unnecessary when a page looks attractive

C. It can identify some problems but must be supplemented with manual and user testing

D. It replaces testing with people who use assistive technology

Correct Answer: C. It can identify some problems but must be supplemented with manual and user testing

Question 10

What is a major governance requirement for AI-generated product content?

A. Publishing it without review to maximize speed

B. Human review for accuracy, privacy, bias, and accessibility

C. Hiding that AI was used in every circumstance

D. Using sensitive personal data by default

Correct Answer: B. Human review for accuracy, privacy, bias, and accessibility

E-Commerce
Chapter 5 of 15