How to use the Email Accessibility Checker.
Check the reading order and link purpose with images unavailable. A visually attractive email can still become difficult to understand with assistive technology.
Make the workflow fit your task.
Inspect text order, headings, images and links in the supplied email. Identify information lost when images are unavailable and propose meaningful labels, then check the actual layout with appropriate accessibility tools.
- What you provide
- Email HTML or copy.
- What you get
- Heading, link-label and reading-order issues.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
An HTML email has image-only headings and several linked icons with no accessible names. No rendered layout supplied.
Completed example
Issue 1: headings are available only as images; provide meaningful text headings or an appropriate text alternative. Issue 2: linked icons lack accessible names; name each destination or action. Unverified: contrast, reading order and client-specific rendering. Inspect the actual email before reporting a complete accessibility result.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can accessible wording compensate for an inaccessible email layout?
It helps, but structure, contrast and client rendering also matter. Review the complete email rather than treating copy as the only factor.
Why do linked icons become meaningless without images?
Provide accessible names that describe each destination. The link's purpose should remain understandable when its visual symbol is unavailable.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑