5 items
Navigate and interact with web pages through their semantic tree structure. Experience the web the way assistive technology does. 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.13 Improvements & fixes - Name tables from caption, fail disconnected dispatch, drop expectTree dumps - Restore the close-tab button's keyboard focus ring - Flash the accent background on a jumped-to row, not a slide-up - Never widen extraction away from a root that isn't in the document - Mount the panel's live regions before their content arrives - Judge native HTML by native rules, not authored-ARIA rules - Name, contain and hand back focus in the input panel dialog - Reject input that isn't a tree instead of reporting it clean - Keep the panel intact when the view mode changes
Sep 3, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.