Map the landmark roles and heading hierarchy of an exported DOM snapshot, produce a navigable outline, and locate the two structural defects that make a page hard to move around: navigation regions that cannot be told apart, and a heading level that was skipped.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/screen-reader-landmark-map.mjs --snapshot examples/docs-clean.htmlRead the result
(The paragraph is one line in the real output; it is wrapped here. The outline continues for the rest of the document, and the four info findings follow it.)
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.