Post

But some people on X pointed that Apple doesn’t respect this guideline. Or maybe a “Close” behaves differently than a “Cancel”? 🤔 What’s Apple stake on this @mikestern.bsky.social? Could you please specify in the Apple HIG if this is valid for both Close and Cancel? Thanks! x.com/vistar941/st...

Yes, close is to my knowledge trailing in as it is usually the only toolbar button. However, the button in messages is actually labeled as a cancel button when using VoiceOver (makes sense, content gets lost when closing it).

13/5/26, 4:52 pm0 reposts1 like

Axel Le Pennec

@alpennec.com

🤯 I’m more lost than before 😂 We could also put the close at the leading edge, like in macOS (red).

developer.apple.comButtonRole | Apple Developer DocumentationA value that describes the purpose of a button.

There are new roles (close and confirm) along with a new initializer requiring no label at all.That's why there are so many checkmarks and xmarks in 26 Confirm -> save, cancel -> something gets lost, destructive -> delete, close exploreswiftui.com/library/butt... developer.apple.com/documentatio...

bsky.app/profile/typ0...

Florian@typ0genius.com

After yesterday’s example of the new button roles, I want to go a bit in depth as I mixed up a few things. With iOS 26, there are now four button roles: close and confirm (26+), destructive and cancel (15+). #iOSDev #SwiftUI

Axel Le Pennec

@alpennec.com

Yup, but how best to combine the ButtonRole and the ToolbarItemPlacement? Because if you use a close role in a cancellation placement, the button is on the leading edge.