I stumbled upon this article and firstly, I learned yet another an important lesson about making presumptions about screen reader users:
It wasn’t my first time seeing someone blind use assistive technology for web navigation, but this experience stood out. Instead of relying on semantic elements like landmarks, headings, lists, or links, the speaker primarily used the browser’s find-in-page functionality to navigate.
It makes total sense that a screen reader user would use that capability, especially as frustratingly, semantic HTML is not exactly guaranteed on modern sites.
Christian used this finding to improve how they were delivering visually hidden text, switching to hidden="until-found". Smart!
I think this can — in the longer term at least — replace visually hidden utilities like this one I like to use. Wide ranging support will be here before you know it too because this is an Interop 2025 thing 🎉
Check it out