Hypothesis testHuman Computer InteractionAccessibility and Universal DesignTest

Interaction Equivalency

Also known as: Equivalent Interaction Design, Alternative Input Validation

OriginatorShari Trewin, IBM ResearchYear2013Sources2Related methods3

Interaction Equivalency is an evaluation method for validating that alternative input and output modalities (voice, gesture, eye tracking, switch control) provide functionally equivalent access to system capabilities compared to standard input (keyboard, mouse). Developed by Shari Trewin, this method ensures that assistive and alternative interaction methods do not create barriers or diminish user capability. Rather than retrofitting accessibility as an afterthought, Interaction Equivalency assesses multi-modal design at design time, ensuring users with disabilities can access all functionality with comparable efficiency.

Key highlights

  • Ensures alternative modalities are not second-class; validates functional and experiential equivalency, not just basic access.
  • Identifies specific tasks/modality mismatches, guiding targeted design improvements.
  • Applies to diverse alternative modalities: voice, gesture, eye tracking, switch, others; flexible framework.
  • Promotes inclusive design; if systems are designed for equivalency from the start, all users benefit from clearer, more flexible interfaces.

Intuition

This section is available to Pro members. Upgrade to Pro

How it works

This section is available to Pro members. Upgrade to Pro

When to use it

Use Interaction Equivalency when designing for accessibility or multi-modal input. Assess equivalency during design, not as post-hoc validation. Essential for systems where disabled users are primary users (healthcare, assistive technology, AT research). Do not use as a checkbox (claiming equivalency without data); conduct rigorous testing with users who rely on alternative modalities.

Strengths & limitations

Strengths
  • Ensures alternative modalities are not second-class; validates functional and experiential equivalency, not just basic access.
  • Identifies specific tasks/modality mismatches, guiding targeted design improvements.
  • Applies to diverse alternative modalities: voice, gesture, eye tracking, switch, others; flexible framework.
  • Promotes inclusive design; if systems are designed for equivalency from the start, all users benefit from clearer, more flexible interfaces.
Limitations
  • Requires diverse users for testing: users with disabilities who rely on alternative input. Recruiting and retaining such users can be challenging.
  • Performance metrics (speed, error rate) may not capture qualitative experience; alternative modalities may feel different even if metrics are equivalent.
  • Cognitive and physical demands differ across modalities; equivalency in time may not mean equivalency in effort or fatigue.
  • Technology readiness varies: emerging modalities (advanced gesture, gaze tracking) may not be reliable enough for true equivalency.

Common pitfalls

This section is available to Pro members. Upgrade to Pro

Applications

This section is available to Pro members. Upgrade to Pro

Frequently asked

What counts as 'equivalent' performance across modalities?

Define thresholds a priori: typically, alternative modality should achieve ≥80% of standard modality performance (time, accuracy). Context matters: safety-critical tasks may require >90%; exploratory tasks may tolerate >70%. Document thresholds and reasoning.

How do I find users with disabilities for testing alternative input?

Partner with accessibility organizations, disability advocacy groups, or assistive technology centers. Recruit intentionally; do not rely on designer colleagues. Offer fair compensation and flexible participation. Build ongoing relationships for iterative testing.

Should all tasks be equivalent across all modalities?

No. Some tasks may be inherently better suited to certain modalities (e.g., precise drawing with mouse vs. eye tracking). The goal is that every critical task is equivalent in *at least one* alternative modality, not all modalities. Communicate modality constraints clearly to users.

Sources

  1. 1.
    Trewin, S. (2013). The Interaction Equivalency Principle in assistive technology and universal design. In Universal Access in Human-Computer Interaction (pp. 535–544). Springer.
  2. 2.
    Washington, P., et al. (2015). Gesture and voice based customizable interface for individuals with upper limb motor impairments. In Proceedings of the 41st Graphics Interface Conference (pp. 15–22).

You have read it. What now?

Cite this page

ScholarGate. (2026, June 3). Interaction Equivalency. ScholarGate. https://scholargate.app/human-computer-interaction/interaction-equivalency