All tools
PERCEIVABLE / ADAPTABLE / NAVIGABLE / ROBUST

Inspect the markup.
Keep the evidence.

Audit email HTML with source-level evidence, bounded automation, manual-review gates, WCAG references, and an exportable remediation queue.

  • No fake score
  • Local parsing
  • Evidence exports
AUTOMATED EVIDENCE STATE / NOT A CONFORMANCE SCORE

Paste email HTML to begin the evidence review.

Paste email HTML to begin.

0source failures0 manual review gates
Source analysis cannot certify an email experience.

Client transformations, CSS support, reading order, zoom, dark mode, animation frames, images of text, assistive technology, and the final MIME message still require rendered and human testing.

Image names0/0

0 explicitly decorative

Link names0/0

Text, aria-label, or linked image alt

Contrast pairs0/0

Explicit resolvable inline pairs only

Document languageMissing

0 visible-text words parsed

EVIDENCE COVERAGE

What the parser could inspect.

Images0

0 named · 0 decorative

Links0

0 with accessible names

Headings0

Order and empty markup inspected

Tables0

Layout and data semantics reviewed

REMEDIATION LEDGER

Filter the evidence, then fix the source.

0

No findings match the current filters.

EXPLICIT COLOR PAIRS

No complete inline pairs were available.

ELEMENTFOREGROUNDBACKGROUNDRATIOTHRESHOLDRESULT

No explicit, opaque inline color/background pairs could be resolved.

MANUAL TEST GATES

Finish where static parsing stops.

01
Reading order

Disable styles and images; confirm the source order preserves meaning and action context.

02
Screen reader and keyboard

Test the received message with representative clients and assistive technology.

03
Zoom, reflow, and spacing

Inspect enlarged text and narrow viewports without clipped content or lost controls.

04
Dark mode and images

Check client color transformations, transparent assets, and information embedded in imagery.

05
Motion and flashing

Review every animated frame and provide pause or safe alternatives where required.

06
Final MIME message

Verify subject, text/plain, HTML, headers, links, and provider transformations together.

ACCESSIBILITY HANDOFF

Export source evidence, criteria, actions, contrast pairs, coverage, and manual test gates.

Automated inspection finds source conditions; conformance depends on the delivered experience.

The checker distinguishes definite source failures, suspicious patterns, and manual-review gates. Passing its automated checks does not establish logical reading order, reliable client rendering, or assistive-technology behavior.

Meaningful images need equivalent purpose; decoration should be ignorable.

Missing alt attributes are different from empty alt attributes. Empty alt can be correct for decoration, but a linked image with no other accessible name creates an unnamed action.

Contrast math is exact only when foreground, background, size, and weight are known.

The parser tests opaque colors it can resolve from inline source and ancestors. Style blocks, gradients, background images, transparency, client overrides, and dark mode require rendered inspection.

Headings, link names, language, and table semantics make relationships programmatic.

A visual treatment is not automatically a semantic heading. Layout tables and data tables serve different purposes. Link purpose must be understandable in context, and interactive roles need accessible names.

Does WCAG require a universal 14px email font size?+

No. WCAG 2.2 does not define a universal 14px body-text minimum. Readability, text resizing, reflow, contrast, and spacing still require testing.

Does every image need descriptive alt text?+

Meaningful images need an equivalent text alternative. Pure decoration can use an empty alt attribute so assistive technology can ignore it.

Why are some findings marked manual review?+

Static source cannot establish purpose, reading order, animation safety, client transformations, or the complete assistive-technology experience.

Does role=presentation make every table accessible?+

No. It can hide layout-table semantics, but data tables need programmatic headers and relationships instead.

Can this certify WCAG conformance?+

No. It supplies bounded source evidence and a manual test plan; it is not a conformance certification or legal opinion.