Page Explorer
A JAWS 2026 feature, from Vispero
A few years ago, figuring out where a control lived on a page meant tabbing through it blind — top-left, buried in a sidebar, or three tab-stops past a broken landmark, with no way to know the shape of the page before you’d already crawled most of it. Page Explorer, paired with AI, changes that: it can describe an entire page’s layout in detail, in seconds, before you touch a single control.
What it does
Instead of discovering a page one tab-stop at a time, Page Explorer gives a screen reader user an upfront, AI-generated description of how the page is actually laid out — what regions exist, where the main content sits relative to navigation and sidebars, and what controls are grouped together. It turns page orientation from a slow, manual search into something closer to a glance.
Why it matters
Page Explorer can only describe a page well if that page was actually built with real structure underneath it — real landmarks, real semantics, not div soup. It’s a direct, practical payoff for the same engineering discipline behind everything in my projects: build it correctly, and tools like this can do far more with it than anyone writing the page by hand ever could on their own.