Marconius 1 points 3y ago
The rotor options will change based on what you are focused on. If you go to Settings > Accessibility > VoiceOver > Rotor, you'll get an editable list of everything you can access in the rotor. I have that set up with only the things I need including text selection and braille screen input.
When you land on a text field, turning the rotor to the left once or twice will bring you to the Edit options. When you are on Edit, swipe vertically to toggle between the action you want to perform; select, select all, paste, look something up in the dictionary, etc. once you've found the action, such as paste, just double-tap the screen with a single finger to activate that action. iOS will then paste whatever you have copied into the text field. You can practice text editing in the Notes app, just create a new note, focus on the note text field, and try typing, selecting, copying, cutting, pasting, etc until you feel comfy with it.
For overall speed, I highly recommend learning braille and using braille screen input. When you are on a text field, the braille screen input option will show up in the rotor, and a 6-key keyboard will show up on the screen. I hold my phone in landscape mode with the screen facing away from my body. That gives my hands and fingers the perfect position to curl around the phone and tap the screen with 6 fingers, typing with braille characters that get interpreted into text. It's how I'm typing this response right now and being able to use contracted grade 2 braille drastically speeds up typing and interaction.
As for apps, just go about it understanding that VoiceOver is putting a cursor on the screen and left and right swipes move that cursor up and down the interface respectively, element by element. A good app will have all buttons, links, text fields, etc. labeled and clearly understandable, while a bad app will have nothing labeled, cursor traps where you suddenly can't move the cursor, all manner of accessibility pitfalls. There is no recourse there apart from contacting the developers and explaining what is going on and hopefully they listen and fix it. I've had good success with that so far, just takes a little persistence.