Zapof

Help Us Enhance Your Accessibility App

1. User Information

First Name:

Last Name:

Email:

Phone Number:

Preferred Communication Method:

2. App & Device Details

App Name:

App Version:

Device Type:

Operating System (OS) & Version:

Marketplace Where App Was Downloaded:

3. Accessibility Issue Details

A. Type of Accessibility Challenge

(Check all that apply)

Screen Reader Compatibility (e.g., VoiceOver, TalkBack)

Text Size & Readability (e.g., Dynamic Type, Zoom)

Color Contrast & Visual Adjustments

Keyboard Navigation (e.g., Switch Control, External Keyboard)

Voice Control & Speech Recognition

Captions & Audio Descriptions

Motor/Touch Accessibility (e.g., AssistiveTouch, Gestures)

Other:

B. Description of the Issue

When did the issue first occur?

Steps to Reproduce the Issue: (Please describe what you were doing before the problem occurred)

Expected Behavior: (What should have happened?)

Actual Behavior: (What went wrong?)

Frequency of Issue:

Always

Sometimes

First Time

C. Assistive Technology Used

Name of Assistive Technology:

VoiceOver

JAWS

ZoomText

Other:

Version of Assistive Technology:

Settings/Configurations:

high-contrast mode

reduced motion

custom gestures

Other:

4. Additional Helpful Information

Screenshots/Screen Recordings: (Upload if possible – helps identify visual/UI issues)

File Name

Upload File

A
B
1
 
 
2
 
 

Error Messages Received: (Copy exact text if any appeared)

Have you tried any troubleshooting steps?

restarting the app

reinstalling

checking for updates

Other:

Any other apps where you experience similar issues? (Helps identify conflicts)

5. Feedback & Follow-Up

How urgent is this issue for you?

Critical (Prevents app use)

High (Significantly impacts usability)

Moderate (Inconvenient but manageable)

Low (Minor issue)

Would you like to participate in further testing or feedback sessions?

Submission & Next Steps

  • Once submitted, our support team will review your report and respond within 1-3 business days.
  • For critical accessibility issues, we may reach out sooner for additional details.
 

App Support Form Insights

Please remove this app support form insights section before publishing.


Below is a detailed breakdown and analysis of the Accessibility App Support Form, explaining its structure, purpose, and how each section contributes to effective issue resolution.

1. Purpose of the Form

This form is designed to:
Identify accessibility barriers in apps sold on digital marketplaces (e.g., Apple App Store, Google Play Store).
Collect structured, actionable data to help developers and support teams diagnose and fix issues efficiently.
Improve user experience by ensuring accessibility concerns are addressed promptly.

2. Key Sections & Their Importance

A. User Information (Optional but Helpful)

  • Why it matters:
    • Allows support teams to follow up for clarification or updates.
    • Helps prioritize urgent requests (if contact details are provided).
  • Best Practices:
    • Make email the primary contact method (faster than phone for most accessibility-related issues).
    • Include a preferred communication method to respect user accessibility needs (e.g., some users may prefer text-based support).

B. App & Device Details (Critical for Troubleshooting)

  • Why it matters:
    • Many accessibility issues are device- or OS-specific (e.g., VoiceOver on iOS vs. TalkBack on Android).
    • Helps developers replicate the issue in the same environment.
  • Best Practices:
    • Encourage users to check their app version (outdated apps may have unresolved bugs).
    • Include a note on where to find OS version (e.g., iPhone: Settings > General > About).

C. Accessibility Issue Details (Core of the Form)

i. Type of Accessibility Challenge

  • Why it matters:
    • Categorizes the issue (e.g., screen reader compatibility vs. color contrast).
    • Helps route the ticket to the right team (e.g., UI designers for contrast issues, developers for VoiceOver bugs).
  • Best Practices:
    • Use checkboxes for quick selection.
    • Include an "Other" option for unlisted concerns.

ii. Description of the Issue

  • Why it matters:
    • A clear reproduction path is crucial for debugging.
    • Helps distinguish between user error, app bugs, or device limitations.
  • Best Practices:
    • Ask for expected vs. actual behavior to clarify misunderstandings.
    • Include frequency (e.g., "always" vs. "sometimes") to check for intermittent bugs.

iii. Assistive Technology Used

  • Why it matters:
    • Some accessibility tools have unique interactions with apps (e.g., VoiceOver gestures, Switch Control).
    • Version numbers help identify if the issue is tied to an assistive tech update.
  • Best Practices:
    • Provide examples (e.g., "JAWS 2023, VoiceOver on iOS 17").

D. Additional Helpful Information

  • Why it matters:
    • Screenshots/screen recordings can reveal UI problems that users struggle to describe.
    • Knowing troubleshooting steps already tried avoids redundant suggestions.
  • Best Practices:
    • Allow file uploads (if the form supports it).
    • Ask about other apps with similar issues to check for OS-level conflicts.

E. Feedback & Follow-Up

  • Why it matters:
    • Helps prioritize critical vs. minor issues.
    • Identifies users willing to beta-test fixes, improving future updates.
  • Best Practices:
    • Use urgency levels to manage support workload.
    • Offer participation in testing to engage power users.

3. How This Form Improves Support Efficiency

Structured Data → Faster diagnosis (no back-and-forth emails).
Reproducible Steps → Developers can replicate and fix bugs.
Device/OS Context → Avoids "works for me" dismissals.
User-Centric Design → Respects accessibility needs in communication.

4. Potential Enhancements

  • Multilingual Support – If the app has global users.
  • Integration with Analytics – Auto-fill device/app version where possible.
  • Accessible Form Design – Ensure the form itself works with screen readers.

5. Conclusion

This form ensures accessibility issues are logged systematically, reducing resolution time and improving app usability. By capturing detailed technical and user-experience data, support teams can collaborate effectively with developers to implement fixes.

Mandatory Questions Recommendation

Please remove this mandatory questions recommendation before publishing.


To ensure effective troubleshooting, certain fields are required because they provide essential details needed to diagnose and resolve accessibility issues. Below are the mandatory questions and why they are critical:

1. App & Device Details (Mandatory for Technical Diagnosis)

A. App Name

  • Why? Ensures the support team knows which app has the issue (especially if the company has multiple apps).

B. App Version

  • Why?
    • Older versions may have unresolved bugs.
    • Helps verify if the issue persists in the latest update.

C. Device Type (e.g., iPhone 15, Samsung Galaxy S24, iPad Pro)

  • Why?
    • Some accessibility issues are device-specific (e.g., screen size, hardware buttons).
    • Helps testers replicate the problem on the same model.

D. Operating System (OS) & Version

  • Why?
    • Accessibility features vary by OS (e.g., iOS VoiceOver vs. Android TalkBack).
    • A bug might only appear in iOS 17 but not iOS 16.

E. Marketplace Where App Was Downloaded

  • Why?
    • Different stores (Apple App Store vs. Google Play) may have different app builds.
    • Ensures the issue isn’t related to a marketplace-specific bug.

2. Accessibility Issue Details (Mandatory for Issue Identification & Resolution)

A. Type of Accessibility Challenge

  • Why?
    • Directs the ticket to the right team (e.g., UI designers for color contrast, developers for VoiceOver bugs).
    • Helps categorize and prioritize fixes.

B. Description of the Issue

  • Why?
    • Steps to Reproduce: Without this, developers cannot verify the bug.
    • Expected vs. Actual Behavior: Clarifies if it’s a bug, design flaw, or user misunderstanding.
    • Frequency: Helps determine if it’s a consistent bug or a random glitch.

C. Assistive Technology Used (If Applicable)

  • Why?
    • Some issues only occur with specific screen readers (e.g., VoiceOver vs. JAWS).
    • Version numbers help track compatibility (e.g., "TalkBack 14.1 has a known bug").

Why These Fields Are Mandatory?

  1. Without device & app version, the team cannot replicate the issue.
  2. Without issue description, they won’t know what went wrong.
  3. Without assistive tech details, they might miss accessibility-specific bugs.

Optional (But Highly Recommended) Fields:

  • User contact info (for follow-ups).
  • Screenshots/screen recordings (visual proof of the issue).
  • Error messages (if any appeared).

Conclusion

These mandatory fields ensure structured, actionable reports that help developers quickly identify and fix accessibility barriers. Optional fields provide extra context but aren’t required for initial troubleshooting.

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.