Getting into the habit of loading up VoiceOver’s Rotor https://support.apple.com/en-gb/guide/voiceover/mchlp2719/mac to check a page’s landmarks, headings, and links. Using semantic markup was a good idea all along.

The main gotchas I’ve found are multiple <main> elements, incorrect heading levels (not a strict <h1> <h2> etc. order), and links with poor text (e.g. “0” for comments, “Browse”, “Download”, etc. without further context). It helps to use aria-describedby to connect form inputs to their errors and hints too.

Use the VoiceOver rotor on Mac

With VoiceOver on your Mac, use the VoiceOver rotor to navigate to specific items in app windows and web pages.

Apple Support
@mudge Not sure how much more efficient this is for your workflow but I’ve previously used a browser extension that highlights all the landmarks on the page when enabled
@fortythieves that sounds useful, do you remember what it was?
@mudge I think it might have been this bookmarklet actually https://accessibility-bookmarklets.org/install.html
Accessibility Bookmarklets

Bookmarklets : Highlight accessibility features of web pages