UX Enhancer
Local-first

Frontend quality, in context

A linter for the frontend you can actually see.

Inspect any rendered webpage for accessibility issues, semantic HTML problems, visual inconsistencies, and frontend-quality risks.

Get UX Enhancer View privacy practices

Version 0.1 · Chrome 114+ · Runs locally

Scan report● Complete
12findings
3high priority
1.8sscan time
High
Interactive element has no namebutton.checkout-action
01
Review
Heading order skips a levelh2 → h4
02
Note
Similar colors differ slightly#A9BAFF / #AAB9FF
03
Rendered DOM analyzed locally
Built for inspection, not certification.No backendNo telemetryNo remote codeNo accounts
What it checks

A practical second set of eyes.

Find issues while the interface is rendered, where code rules alone cannot see the whole picture.

A11Y

Accessibility analysis

Run packaged axe-core locally against the rendered page—no scan data leaves your browser.

HTML

Semantic HTML checks

Review evidence-backed issues in document structure, landmarks, headings, and interactive elements.

VIS

Visual consistency

Surface spacing, typography, and presentation patterns that deserve a closer human look.

DOM

Element highlighting

Jump from a finding to the affected element without hunting through the page.

FIND

Search + severity filters

Focus the report by keyword and severity so the highest-value work stays visible.

DIFF

Rescan comparison

Fix the page, rescan, and see how the current result differs from the previous pass.

JSON

Sanitized JSON export

Export findings on demand without raw element observations for safer collaboration.

NOTE

Explicit limitations

Know which page areas could not be inspected and where manual review still matters.

How it works

Scan. Inspect. Fix. Repeat.

UX Enhancer stays close to the page you are building, inside Chrome’s side panel.

  1. 01Open a webpage.
  2. 02Open the UX Enhancer side panel.
  3. 03Click Analyze page.
  4. 04Review findings and highlight affected elements.
  5. 05Fix the page and rescan.
Read the signal carefully

Automation finds risks. People make the call.

Automated testing cannot prove complete WCAG conformance. Results may require manual review.

Closed shadow roots, inaccessible cross-origin frames, canvas content, arbitrary JavaScript listener state, and unrendered virtualized content may not be inspected.

Read troubleshooting guidance