Semantic Navigator

Most accessibility problems don't look like problems — until you remove the visual layer. Real screen reader testing catches them, but the cost is real: install NVDA or VoiceOver, learn another keyboard model, parse audio output. Most teams put it off, then ship bugs they would have caught earlier with a faster loop. Semantic Navigator is that faster loop. It opens any page as its accessibility tree in a Chrome side panel and lets you complete real tasks through the tree alone — click, fill, submit, expand menus. If you can complete the task through the tree, your users probably can too. If you can't, that's the bug. In the panel: - DOM, A11y, and TAB views — raw structure, accessibility tree, or tab order. - Screen curtain — blacks out the viewport while the tree stays interactive. Fastest way to test a flow with no visual fallback. - Cross-iframe merging — embedded widgets, payment forms, third-party flows all stitch into the parent tree at the correct depth. - Keyboard bar + element picker — drive real keyboard input from the panel, or click any element on the page to jump to its tree row. Not a replacement for NVDA, JAWS, or VoiceOver. Semantic Navigator exposes the same raw material — the semantic tree — so structural bugs (missing names, broken tab order, incorrect roles) are findable in your dev workflow. Then test with real AT before you ship. Open source, MIT licensed. The same engine powers a Storybook addon, a React inline panel, and a testing library. See https://real-a11y.dev. Runs entirely in your browser — no analytics, no accounts. What's new in 0.1.15 • Privacy: a text area's default text no longer appears in the tree, the tab sequence, the live-announcement log or the input panel. On a one-time-code or card-number field, that text can be the secret itself. • The tree matches Chrome's own reading of a page more closely: state values, roles, checkbox and drop-down states, expanded/collapsed badges, popover buttons, multi-row selects and suggestion inputs. • Unnamed forms are no longer listed as landmarks. • Image map areas are back on Chrome 153, and decorative clip-path crops are no longer treated as hidden. • Fixed: forms with a field named after a DOM property, such as nodeType or parentElement, no longer disappear from the tree or freeze the tab.