AxiomCode
Verifiable intelligence for AI software engineering. Everything starts with a formally grounded code graph.
A free Chrome extension that shows a page’s headings as they are written in the code, flags broken structure, and explains what each finding means.
PluginsJavaScript · CSSGitHub @Wish-You-Were-HereOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Chrome extension that shows a page's heading structure as the code — and a screen reader — has it. Two views, plain-English findings.
Loading the full README. The saved excerpt is shown below.
A small browser extension that shows a page's headings the way the code wrote
them — not the way the design makes them look.
Headings look like headings on screen whether or not they are headings in the
code. The difference only shows when you take the page apart, and that
difference decides whether someone listening to the page can jump between
sections instead of listening to all of it.
Outline headings draws a frame around every heading and writes its level
next to it. The rest of the page is left alone. It uses outline rather than
border, so nothing shifts when you switch it on.Read the full README ↗A small browser extension that shows a page's headings the way the code wrote them — not the way the design makes them look.
Headings look like headings on screen whether or not they are headings in the code. The difference only shows when you take the page apart, and that difference decides whether someone listening to the page can jump between sections instead of listening to all of it.
Outline headings draws a frame around every heading and writes its level
next to it. The rest of the page is left alone. It uses outline rather than
border, so nothing shifts when you switch it on.
Show structure opens a panel with the headings indented by level, each one
tagged with the landmark it sits in — main, nav, footer, header,
sidebar. Click a row to jump to that heading on the page.
Errors — things that are wrong:
h1h1h2 followed by h4)Going up several levels, h4 to h2, is not an error. That is a section
ending.
Worth a look — usually wrong, sometimes deliberate:
h1 whose name comes from an image, which is almost always the logo|, », •)The two are kept apart on purpose. Mixing them is how tools lose people's trust.
It reads the rendered page and reports what is there. It cannot tell you whether a heading describes its section well, and it is not an accessibility audit. A sound heading structure is one requirement out of many.
The extension collects nothing, sends nothing, and stores nothing. It has no
server. activeTab means it can only read the page in the tab where you clicked
the button, and only after you clicked.
chrome://extensionsAlt+Shift+1 outlines the headingsAlt+Shift+2 shows the structureEsc closes the panelRedraw with python3 verktyg/ikoner.py (needs Pillow).
MIT. See LICENSE.
By Wish You Were Here, a product and design studio in Gothenburg, Sweden.