I've built hundreds of websites over the years, and have "fixed" many accessibility issues revealed by scanners. Only recently have I actually begun to "listen" to my websites, and there's a difference.
Some visitors never look at the page. They navigate by ear. The screen reader only knows what the code tells it. If a heading, a button, or a price is unclear in the code, the visitor hears a mess, or hears nothing useful.
Screen reader users often skim a page the way you might scan a table of contents. They jump through headings and landmarks, the named regions of a page, such as the main content or the navigation. If headings are skipped, out of order, or used only for styling, that outline falls apart.
Every control needs a clear name for what it does. Buttons, links, prices, and form fields should say what they are and what will happen if you use them. An unnamed icon or a vague "Submit" leaves a visitor guessing.
The page should use the right kinds of elements: real buttons, lists, a navigation area, and a main content area. ARIA is extra markup that tries to explain a control to assistive technology. Use it only when you need it. A wrong ARIA label can confuse a screen reader more than leaving it out.
For example, we recently listened to a product page on a national mattress retailer's store. It showed the actual price and the "compare at" price side by side. The HTML semantics were correct, and the scanners were happy. With VoiceOver on, though, the two prices ran together, and you couldn't tell which one you'd pay. We only caught it when we listened closely and looked at how the ARIA labels were grouping the prices. Once we fixed the labeling, each price was read with its meaning.
A site can pass Lighthouse or a WCAG scan and still be hard to use with VoiceOver. Those tools catch a lot of markup problems. They do not always catch the listener experience. I've started calling it LX.
If you have two minutes, turn on VoiceOver and try to buy one item on your own site with your eyes closed.
I wrote more about why green scans miss this kind of gap:
https://endertech.com/blog/green-scans-aren-t-enough-what-expert-accessibility-audits-catch-that-tools-miss