Page Repair

Beta · store submission in progress

A browser extension that repairs the page you are actually on, naming the unlabeled buttons screen readers get stuck on, putting broken heading levels back in order, and adding the landmarks that make "skip to content" work.

It runs only when you press the button. Then it tells you exactly what it changed.

What it fixes

  • Names the unlabeled controls

    Screen readers announce "button, button, button" on controls the site never labeled. Page Repair gives them accessible names, so you hear "Search" instead.

  • Repairs heading structure

    Skipped and out-of-order heading levels break heading navigation, one of the primary ways screen-reader users move through a page. Page Repair puts the levels back in order.

  • Adds missing landmarks

    Without a main region there is nothing to jump to. Page Repair adds the missing landmarks so "skip to content" actually works.

Heading and landmark repairs are computed on your device in milliseconds. Only genuinely ambiguous unlabeled controls are sent for labeling, and only a small slice of the surrounding HTML, never the whole page.

This is not an accessibility overlay

The disability community rejects overlay widgets, and it is right to. An overlay is installed by a site owner, runs on every visitor, claims to have "fixed" the site, and frequently makes things worse, while giving the owner a reason not to do the real work.

Not building one is a written rule across everything we make. Page Repair is the one thing that comes close, so the line matters: it acts for one person, on their own device, when they ask, and it never lets a site claim credit for it.

  • It only runs when you ask

    Never on page load, never on its own. It uses the browser’s activeTab permission, so it cannot see a page at all until you invoke it on that page.

  • It patches, it does not rewrite

    The site’s own JavaScript, visuals, and interactivity keep working. Nothing is stripped, regenerated, or replaced with a substitute interface.

  • It is fully reversible

    Alt+Shift+U removes every repair and restores the page’s original attributes. If a fix is wrong, you are one keystroke from undoing it.

  • It works for you, not for the site owner

    Repairs happen on your device, for your session. Page Repair never tells a site it is now accessible, and it never contacts anyone on your behalf.

A wrong label is worse than no label

When a control is too ambiguous to name locally, Page Repair asks a language model, then gates the answer on how confident it is. High-confidence labels are applied. Medium-confidence labels are applied with an "auto-labeled, unverified" note announced after the name, kept out of the accessible name itself so braille output and voice control keep working. Low-confidence guesses are thrown away.

It also never speaks uninvited and never moves your focus. One polite announcement, immediately after you invoked the repair, telling you what actually changed, not what it attempted.

And when a page is beyond repair, it helps you say so: one command copies a plain-language accessibility report, with WCAG references, to your clipboard for you to send to the site owner. The extension never sends it for you.

What gets sent, and when

  • Nothing, until you invoke it. The extension cannot see a page before you press the button on that page.
  • Heading and landmark repairs never leave your device. They are computed locally.
  • Only ambiguous controls are sent for labeling: a small slice of surrounding HTML, not the page, and not its contents.
  • Your settings stay local. Your API key or credit token is stored on your device and never synced by us.

Want the beta?

Page Repair is in beta while we finish the store submission. If you use a screen reader, or you test for people who do, we would like your hands on it.

Get the beta See all apps