Prototype reviews

Illustration: Prototype with wireframes, the one in the right column is pink with a black X in the middle

Get feedback early. Share links to your interactive prototypes with a user and guide them in a moderated session.

What is a Prototype Review and when should I use one?

One of the best ways to fully integrate accessibility into your product cycles is to consider it early and often. A Prototype Review is a video-based session directly with one of Fable’s community members. Meet with an alternative navigation or screen magnification user to get feedback on your prototypes. In these moderated sessions, you’ll walk a user through your interactive prototype, and they’ll provide feedback and help shape your user experience, pre-code.

You should request a Prototype Review if you are looking to get valuable user feedback early on in product cycles, validate design decisions, and reduce development time by addressing accessibility early on.

You should not request a Prototype Review if you are looking for:

  • Screen reader user feedback
  • Your prototype is functional, meaning it is coded
  • An Unmoderated research method

What can I expect?

Get initial thoughts and feedback on prototypes (using tools like Figma, Axure and InVision) from screen magnification or alternative navigation users. You’ll then be able further specify any preferences you may have, such as the specific Assistive Technology.

Screen reader users

For support getting early design feedback from screen reader users, you can leverage bookable support hours to have an experienced researcher guide you through the preparation process of the below. You would use a User Interview request for these approaches.   

  • Wizard of Oz method – with the “Wizard of Oz” method, you describe the design for the tester.  What you describe depends on what they want to explore and they give feedback based on how you say the product will behave. User researchers from Ally Financial have shared an overview of the Wizard of Oz method.
  • Low-fidelity spreadsheet – you can use a simple spreadsheet (Excel, Google Sheets) to get insights on the proposed structure and layout for your web page or mobile screen. Buttons, links and calls-to-action into a spreadsheet. Put them in the order you intend a user to experience them.  A screen reader user can navigate through the spreadsheet and provide effective feedback. 

How do I request a Prototype Review?

Creating a Prototype Review request is easy. Like any request, start by selecting ‘Create’ from the Fable platform. Select an existing Project, or create a new one – every request must be assigned to a ‘Project’. Select ‘Prototype Review’ and you’ll be on your way!

To request a Prototype Review you’ll need information on the the following:

  • Testing audience: Who do you want to meet with? Choose from alternative navigation or screen magnification users. You can then specify additional tech specs like operating system.
  • Meeting details: When and why would you like to meet? This includes date, time and a description of your goals/objectives.
  • Credentials and access: How will your participant access your product? This includes any special instructions or existing environments.
  • Live links: What will your participant be interacting with? This includes proving any URLs you’ll want the participant to review, especially if you want the participant to share their screen. Alternatively, if you don’t have a live link to share, or if the prototype isn’t shareable externally, inform the tester that you will be sharing your screen instead

Don’t have all of this information yet? No problem! You can always exit and save your Prototype Review request as a draft at any point during the process.

Tips for success

All Prototype Reviews are booked for 60 minutes, which can go by surprisingly quick! Below are some suggestions to make the most of your time, and ensure you have a successful Prototype Review. For more tips, be sure to check out the article: 5 tips on conducting a Prototype Review.

  • Prepare your questions beforehand: Make a list of questions and have clear objectives prior to joining the session.

  • Pick task flows that can be completed during one session: AT users (usually) take time and a half more than non-AT users. Make sure you keep that in mind when picking the designs you’ll cover.

  • Communicate with your AT user, early and often: Not able to view the screen share? Need further clarification on a piece of feedback? Don’t hesitate to let them know!