Email Checker
Pricing
from $15.00 / 1,000 results
Email Checker
Check email HTML for client compatibility and accessibility through a simple API. The Actor checks unsupported HTML and CSS across Gmail, Outlook, Apple Mail, Yahoo, and other clients. Accessibility API detects accessibility issues such as missing alternative text and document structure problems.
Pricing
from $15.00 / 1,000 results
Rating
0.0
(0)
Developer
Ondrej Skala
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
7 days ago
Last modified
Categories
Share
What does Email Compatibility and Accessibility Checker do?
Email Compatibility and Accessibility Checker analyzes rendered email HTML before you send it. It identifies HTML and CSS features that email clients do not fully support and detects structural accessibility violations. Checks cover Gmail, Outlook, Apple Mail, Yahoo Mail, and many other client variants.
Paste content into the Apify Input tab for a one-off combined check, or use one of three real-time standby endpoints. Apify provides API access, scheduling, integrations, monitoring, and a persistent result dataset without requiring you to operate a separate service.
Why use Email Compatibility and Accessibility Checker?
Email clients support a smaller and less consistent set of web features than modern browsers. At the same time, missing alternative text, unnamed links or buttons, invalid ARIA attributes, and poor document structure can make an email difficult to use with assistive technology. This Actor helps you:
- catch compatibility and accessibility regressions in one API call;
- focus compatibility checks on a specific email-client family;
- inspect exact client variants affected by a feature;
- locate accessibility failures with selectors and remediation guidance;
- retain structured results for CI, reporting, and automation.
This Actor analyzes email markup. It does not validate mailbox addresses, send messages, or guarantee inbox placement.
How to use Email Compatibility and Accessibility Checker
- Open the Actor in Apify Console.
- Paste rendered email HTML into the Input tab.
- Optionally provide standalone CSS and select an email-client preset.
- Start the Actor. HTML input runs both checks; CSS-only input runs compatibility checking.
- Review the Output dataset and follow each diagnostic's message or help link.
For API usage, call the Actor's Standby URL and use the endpoint that matches your workflow. Normal runs process one input and exit immediately; only Apify-managed Standby runs keep the HTTP server alive.
Input
POST /check-compatibility
Runs only email-client compatibility analysis. Provide html, css, or both, plus an optional preset:
{"html": "<!doctype html><html><body><picture><img src=\"hero.png\" alt=\"Hero\"></picture></body></html>","css": ".button { cursor: pointer; }","preset": "gmail"}
Supported presets are all-clients, gmail, outlook, apple-mail, and yahoo.
POST /check-accessibility
Runs only accessibility analysis. It accepts one required field:
{"html": "<!doctype html><html><body><img src=\"hero.png\"></body></html>"}
POST /check
Runs both checks and returns both result sets. html is required because accessibility analysis needs a document. css and preset are optional and affect the compatibility check.
All content fields accept up to 750,000 characters, and the complete HTTP request body must remain below one megabyte.
Output
The combined endpoint returns a summary plus nested results:
{"checkType": "combined","checkedAt": "2026-08-05T12:00:00.000Z","success": false,"errorCount": 4,"warningCount": 0,"violationCount": 3,"violationNodeCount": 3,"incompleteCount": 1,"compatibility": {"checkType": "compatibility","preset": "gmail","clientPatterns": ["gmail.*"],"diagnostics": []},"accessibility": {"checkType": "accessibility","engineVersion": "4.12.1","violations": [{"id": "image-alt","impact": "critical","help": "Images must have alternative text","helpUrl": "https://dequeuniversity.com/rules/axe/4.12/image-alt","nodes": [{ "target": ["img"], "failureSummary": "Fix the missing alternative text" }]}]}}
Every API result is also stored in the default dataset with a checkType of compatibility, accessibility, or combined. Submitted HTML and CSS are not stored, and raw HTML node snippets are removed from accessibility findings. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Data table
| Field | Meaning |
|---|---|
checkType | The check that produced the record. |
success | Whether the selected check found no failing errors or violations. |
errorCount / warningCount | Email-client compatibility totals. |
violationCount | Number of failing accessibility rules. |
violationNodeCount | Number of DOM nodes affected by those rules. |
incompleteCount | Rules that require additional review. |
compatibility / accessibility | Full nested results on combined checks. |
How much does it cost to check email quality?
Cost depends mainly on how long the standby Actor remains running and its assigned memory. Compatibility checks are lightweight. Accessibility checks create an isolated JSDOM document and require more CPU and memory. For occasional work, submit several checks during one run and stop it afterward. Apify's free tier may cover light testing; review current platform pricing before operating an always-on endpoint.
Tips and advanced options
- Use a focused compatibility preset during development, then run
all-clientsbefore release. - Send rendered HTML rather than a component or unrendered template.
- Treat
incompleteaccessibility findings as manual-review tasks. - Accessibility checks run without executing scripts or loading external resources.
- JSDOM has no visual layout engine, so the
color-contrastrule is disabled. Test contrast and responsive layout in real browsers and inboxes. - If compatibility data is unavailable for a detected feature on a specific client, the Actor skips only that client and returns a warning diagnostic instead of failing the check.
- Use a normal Actor run for one-off checks so the run exits after saving its result. Use the Standby URL only when you need a real-time API; Standby consumes compute until Apify's configured idle timeout stops the server.
- Run
bun run test:bunlocally to exercise all three HTTP endpoints against representative compatibility and accessibility failures.
FAQ, disclaimers, and support
Does a passing result guarantee an accessible, compatible email? No. Automated checks find many issues but cannot replace manual assistive-technology and inbox testing.
Is my complete email stored? No. Only sanitized findings and summary data are persisted.
Does the Actor crawl websites? No. Compatibility data and checking engines run locally, so proxy rotation is unnecessary.
Use the Actor's Issues tab to report bugs, request another preset, or ask for help. Custom integrations and tailored email-quality workflows can also be developed on request.
