Accessibility of High-Fidelity Prototyping Tools

Document Title

Accessibility of High-Fidelity Prototyping Tools

Document Information

• Subject Area: Accessibility of high-fidelity prototyping tools and human-computer interaction
• Keywords: high-fidelity prototyping tools, screen readers, accessible design, user experience (UX), human-computer interaction (HCI), graphical user interface (GUI), text alternatives, keyboard navigation, usability, visual impairment

Research Background and Issues

• Problems or Challenges:

  • The majority of high-fidelity prototyping tools lack support for visually impaired designers, and their graphical user interfaces (GUIs) are not screen reader-friendly.
  • Existing research rarely addresses the usability issues faced by visually impaired designers when using these tools.
  • The inaccessibility of prototyping tools often affects the accessibility design of final products, creating a negative chain reaction.

• Significance:

  • Accessible design tools are a prerequisite for enabling visually impaired designers to participate in user interface (UI) and user experience (UX) design work.
  • Improving tool accessibility not only benefits visually impaired users but also enhances the inclusivity of final products for all users.

• Research Motivation and Related Work:

  • The authors observed that while efforts have been made to improve accessibility in web and mobile design, the accessibility and operability of design tools themselves remain underexplored.
  • This paper focuses on how visually impaired designers use screen readers to operate high-fidelity prototyping tools, evaluating the compatibility between tools and screen readers.

Solution

• Proposed Methods or Solutions:

  • The authors selected four widely used high-fidelity prototyping tools (Sketch, Adobe XD, Balsamiq, UXPin) and two mainstream screen readers (VoiceOver and Narrator). They evaluated the accessibility features of the user interfaces using the IBM Accessibility Checklist and WCAG guidelines.
  • The analysis was conducted across multiple dimensions, including GUI element accessibility and key design task operations.
  • The authors defined and quantified the Inaccessible GUI Element Rate (IAER) and proposed targeted improvement recommendations.

• Innovations:

  • Addressing the lack of standardized accessibility evaluation criteria for non-web platforms, the authors combined the IBM Accessibility Checklist with self-developed guidelines, filling a gap in existing research.
  • The proposed evaluation method goes beyond technical compatibility, considering the difficulty of implementing key interactive functions and their accessibility issues.

• Implementation Steps and Key Techniques:

  1. Define the scope of tools and screen readers: Select popular prototyping tools and low-cost, widely used screen readers.
  2. Define GUI components: Canvas, layers, interface elements, and element parameters.
  3. Design basic task workflows: Include typical operations such as creating a canvas, adding buttons, and linking pages.
  4. Evaluation methods:
     • GUI element testing: Assess the accessibility of key GUI controls such as buttons, images, and text boxes.
     • Task testing: Complete key design tasks step-by-step and record accessibility results.
  5. Data analysis: Evaluate the level of support based on guidelines and calculate IAER.

Research Outcomes

• Specific Findings:

  • None of the evaluated tool and screen reader combinations fully met accessibility requirements. The average full support rate for GUI elements was 45.9%, partial support rate was 34.2%, and non-support rate was 19.9%.
  • VoiceOver-Sketch and VoiceOver-Balsamiq were the most compatible combinations.
  • Among GUI element adaptations, Balsamiq's template feature effectively reduced the complexity of operations, while several features in Adobe XD and UXPin were inaccessible to screen readers.

• Comparison with Existing Solutions and Advantages:

  • The authors' research provides systematic quantitative data, pinpointing the distribution and severity of accessibility issues.
  • Problem-oriented improvement recommendations offer clearer optimization directions for tool developers.

• Experimental or Evaluation Results:

  • The study revealed major accessibility issues in most tools, including:
    1. Missing input prompts.
    2. Lack of alternative text for non-text content (e.g., buttons, images).
    3. Poor recognizability of control operations.
    4. Improper focus order.
    5. Unavailable or overly complex keyboard navigation.

• Limitations and Future Directions:

  • Limitations:
    • The tests were conducted by sighted researchers, and blind or experienced screen reader users might identify issues not covered by the study.
    • The research primarily evaluated the accessibility of basic prototyping tasks, leaving complex prototyping designs unassessed.
    • The evaluation was limited to VoiceOver and Narrator screen readers.
  • Future Directions:
    • Invite real blind or low-vision users to participate in accessibility testing to expand and validate current findings.
    • Investigate the accessibility of tool outputs (e.g., exported prototypes).
    • Extend compatibility evaluations to other screen readers, such as JAWS.