Don't. When you start accessing controls on a different form, you lock the two together and you can no longer modify one without considering the effects on the other - controls are private for a reason, and that reason is to prevent this kind of thing which is decidedly against the principles of OOPs.
Instead, Form2 creates an event (or several events) which it raises when it wants to change Form1, and Form1 handles the events, using Properties on Form2 to access teh revised information.
Perhaps "BurgerSelected", "PriceChanged" or similar would be good?
This sounds complex, but it isn't, not really - and it makes your code a lot more readable and maintainable.
Have a look at this:
Transferring information between two forms, Part 2: Child to Parent[
^] - it includes an example.