Skip to main content
October 13, 2025
Question

Problem: Bring forward shortrcut (cmd+alt+up/down) rotates the object

  • October 13, 2025
  • 70 replies
  • 2306 views

Cmd+alt+up/down recently started to rotate object instead of moving the layer up down.

How to fix/disable it?

This topic has been closed for replies.

70 replies

DavidTC
New Participant
October 15, 2025

Same! Huge mistake...

enesates
New Member
October 15, 2025

I can’t believe they changed this shortcut. They say it’s for accessibility reasons… They even had a developer on camera saying it was an accessibility update! So funny lol.

Take note, friends. When you make a pointless and nonsense update and have no reasonable explanation for it  you can just say it’s for accessibility and move on :)

Jens_Nielsen
Active Member
October 15, 2025

Latest answer from figma

I've checked with the team and this is part of recent accessibility improvements. You can learn more about this release here, and in these links:

 
Previously there were multiple shortcuts which mapped to this action, and we repurposed the less frequently used ones (ctrl+alt+up/down) for rotation. Thank you for your understanding on this.
 
I'll close this as solved for now but should you have any other questions don't hesitate to get in touch. We're always here to help!

 

Still makes no sense, but i guess their minds are made up. guess we just have to rewire muscle memory!

docmine-phil
New Member
October 15, 2025

Guess a lot of my designs will look slightly tilted for the next couple of weeks. I don’t get it — cmd + alt + up/down was probably one of the shortcuts I used most in Figma.

@accessibility improvements team: How am I supposed to use this new shortcut on a (Swiss) German keyboard layout? I tried using cmd + [ but the characters [ ] are bound to alt + 5 / alt + 6.

My conclusion was to use alt + cmd + 5 / alt + cmd + 6, but that doesn’t do anything for me, probably because it triggers some conflict.

How is this shortcut supposed to be accessible for users like me with this specific keyboard layout, without having to switch to a US layout?

 

Jens_Nielsen
Active Member
October 15, 2025

Or here is a CRAZY idea. let us define our own shortcuts in the desktop app! Wild idea, i know!

Grigory88Author
October 15, 2025

Or here is a CRAZY idea. let us define our own shortcuts in the desktop app! Wild idea, i know!

No way, it’s not ACCESSIBLE

Jens_Nielsen
Active Member
October 15, 2025

added answer from Figma:

 

To clarify, we had multiple shortcuts for the same action: bring forth, send back. These were:

  1. The shortcut you were using before ctrl+alt+up/down
  2. The shortcut we've kept cmd+[ and cmd+] 

 
During accessibility improvements we identified that ctrl+alt+up/down was the least used for this action, and favoured cmd+[ and cmd+] for it. In turn, we repurposed ctrl+alt+up/down for rotation, which was part of the accessibility effort.

Sebastian_Graz
New Member
October 15, 2025

Nah revert this “update”

Ian_Palmgren
Active Member
October 15, 2025

Fully support a more accessible Figma. Fully do not support removing/remapping existing shortcuts to new ones, arbitrarily and without warning. Don’t feel like this was thought through enough. 

Tom Reem
Figmate
Figmate
October 15, 2025

Hey everyone — thank you for flagging this and for describing how the shortcut behavior is affecting your workflow. We completely understand how unexpected changes like this can be frustrating, especially when they disrupt familiar design practices.

I’ve shared your reports and feedback with our product team to ensure they’re aware of how these updates are affecting your workflow. Your notes are helpful for us to better understand the issue and evaluate next steps.

We’ll continue monitoring this thread and keep the feedback loop open with the product team. In the meantime, Cmd/Ctrl + ] and Cmd/Ctrl + [ continue to allow you to reorder layers with keyboard shortcuts.

In addition, we’ll keep the Accessibility at Figma article in Figma Learn updated as new information and shortcuts become available. Thanks again for your patience and for taking the time to surface this.