LAUNCHED: Option to disable keyboard shortcuts in prototype

[Chris_Calabrese]

Issue
When performing user testing, the prototypes can look and function so real that users have tried typing into static fields. This can lead to problems if a user types a shortcut (ie “C” for comment) and a Figma login window pops up, or “R” and they are sent to the beginning of the flow.

The main use cases I have for prototypes are:

1. General/Client Presentation
Users: Only me

• This case is covered well by the existing functions. The shortcuts help the presenter navigate. However, a Table of Contents (TOC) is badly needed. Many prototypes are not linear so the forward and back button navigation is not very useful.

2. Client Handoff
Users: multiple people who may have a wide range of interacting Figma prototypes

• Improvements:
  • showing users shortcuts and a TOC upfront and letting them hide it if they want
  • sometimes, especially in the early stages of design, designs need written explanations, so a way for designers to leave annotations in the prototype would be very useful

3. Setting up User Testing
Users: Me and colleagues (sometimes client)

• Currently setting up a prototype in Figma requires manually going through each page of the prototype and validating that:

  • The appropriate CTAs are linked and navigate to the correct pages
  • all links have the proper transitions between pages

• Improvements:

  • As an MVP, a check list of frame names that displays a sublist of each prototype connection and details.
  • Clicking on a frame name would focus the view to the appropriate page in the Figma file. Clicking on a sublist item’s details would display the interaction options for that item. For example:
  

3. User Testing
Users: Moderator and Participant

• The participant needs to feel like they are actually using the interface and to an extent, freely navigate though the prototype. While this is happening the moderator needs to be able to quickly set participants up for the next scenario they are testing.

• Improvements:

  • A TOC would come in handy to easily direct participants to their next task
  • option to disable prototype shortcuts

[Paul_Van_Tuyl]

I just ran a user test through usertesting.com, and the user accidentally tapped the arrow key on their keyboard. This moved them to the wrong place in the test and they started to give low-rating feedback that essentially means I need to remove their test from results of the test.

Please give us the ability to disable keyboard navigation in addition to hotspots.

[Melanie_Arakaki]

I need to run unmoderated tests and like many people, I also found in previous tests that users mess up with the prototype by accidentally pressing R, C, or the arrow keys. Not having the ability to disable these shortcuts is a nightmare for our process.

[Robin_Peter]

I have exactly the same problem. And I am very surprised why it still persists. It is technically not difficult to disable the arrow keys when in presentation mode, so why don’t they just do it if it apparently annoys a good number of their users!

[Augusto_Bendezu]

Disable shortcuts are much needed for testing purposes, especially if you’re testing a keyboard controlled app where navigational keys have other function than going to the next/prev page.

[Fri_Rasyidi]

Very true!

We’re testing the keyboard interaction and after painstakingly making the prototype for days… we’re pretty surprised to see that at the end of the day, pressing Enter moves you from screen to screen; rendering our efforts useless.

[jelvin]

+1 to this!

[Fabrice]

Good idea! I would even push further and consider supporting key strokes as user interactions. For instance, “on SPACE-KEY, open overlay…”

[BaptisteE]

+1
That’s a major issue we experience in our team presentations and with research participants. It’s particularly painful in TV app prototypes that uses arrows navigation.

[Paul_Van_Tuyl]

Looks like disabling keyboard shortcuts is now a feature! Interactive components: less wiring, more inspiring

[ksn]

It is! If anyone is looking for instructions how to do this, this page should help

[Celestine]

Hi, I try to create a prototype to test a scenario with keyboard navigation only for visual impaired users. But if I ‘disable’ this functionality, my prototype will also not work with the keystrokes I’ve assigned for the flow Any suggestions here?

[Charlene_Hew]

Please, this is still an issue. For those needing an alternative, I made this workaround that will show a toast message when ANY key is pressed. But I wish there were a built in solution for this.

Press Any Key | Figma Community

[Celine_Figma]

Hey all,

With the launch of some new Figma Prototyping updates, we are pleased to inform you that you can now disable shortcuts: Turning off “Enable Figma Shortcuts” now disables all shortcuts on a prototype (not just the navigation shortcuts)! Learn more here

[Michelle_M]

Is it possible to have the Figma shortcuts turned off when the prototype is being shared through a link? This setting is not included as part of the link shared prototype so another person who opens the Figma prototype still has the Figma shortcuts enabled (without knowing). This is causing lots of frustrations in unmoderated user testing with participants who do not use Figma.