How to Make Email Signatures WCAG Compliant
July 1, 2025
Every email your company sends ends with the same few lines, and for some recipients those lines are the hardest part of the message to read.
Solution: Build the signature from real text with a contrast ratio of at least 4.5:1, give every image alt text, keep the reading order logical, and make sure text can be enlarged without breaking the layout. Then apply the template centrally, so that no employee can change it by hand and quietly undo the work.
Why WCAG Applies to Email Signatures
The Web Content Accessibility Guidelines (WCAG) are the international standard for making digital content usable by people with disabilities, including people who are blind, have low vision or limited mobility, or are neurodivergent. An email signature is small, but it is still HTML, so a screen reader, a zoom setting, or a high-contrast mode treats it like any other page.
The difference is volume. A website might be reviewed for accessibility once a year, while a signature template repeats on every message a company sends. If it has a problem, that problem reaches every recipient, every time.
WCAG Requirements for Email Signatures at a Glance
Which WCAG Level to Aim For
WCAG has three conformance levels: A, AA, and AAA. Level A covers the basics, AA is the standard most accessibility policies and regulations refer to, and AAA is the strictest and is not required as a general target. The current version is WCAG 2.2, which builds on 2.1.
For an email signature, AA is the right target, and it's reachable. The 4.5:1 contrast ratio in the table above is an AA requirement. Level AAA asks for 7:1, which dark gray text such as #333333 on a white background already exceeds by a wide margin. In other words, a signature built with plain dark text, labeled links, and alt text on its images can meet AA without any design compromise, and often reaches AAA for contrast along the way.
The practical point is to choose the level before the design starts. A signature designed first and checked afterward usually fails on color, because brand palettes are rarely chosen with 4.5:1 in mind.
What an Inaccessible Signature Sounds Like
Picture a signature that was exported from a design tool as a single image: the logo, name, title, phone number, and a "Book a call" button, all flattened into one picture with no alt text. A sighted reader sees a tidy block. A screen reader user hears "image," or the file name, and nothing else. The phone number can't be copied, the button can't be activated, and the name of the person writing is never read out.
A subtler version is a signature built from real text but with a light gray title, small links that all say "click here," and a layout whose markup puts the phone number before the name. Each problem looks minor on screen. Together they mean a recipient with low vision or a screen reader has to work to find out who the email is from and how to reply.
Neither signature was designed to exclude anyone. They fail because accessibility was never part of the brief, which is why it has to be built into the template and not left to whoever builds the next one.
How to Build a WCAG-Compliant Signature
Five things decide whether a signature meets WCAG in practice, not just in appearance. A sixth, testing, shows whether it really does.
HTML structure and semantics
Email layouts still need tables, because they render consistently across clients. The accessibility problem starts when the table is the only structure. Mark layout tables with role="presentation" so a screen reader doesn't announce them as data tables, and use real elements inside the cells: <p> for text blocks, <ul> for lists, and <a> for links with descriptive text rather than "click here".
Color contrast
WCAG's minimum contrast criterion requires 4.5:1 between normal-sized text and its background, and 3:1 for large text. That applies to every line, including the job title, the contact details, and the label on a call-to-action button. Check your actual hex values with WebAIM's contrast checker rather than judging by eye. Also don't rely on color alone to show that something is a link. Underline it.
Alt text for images
Every meaningful image needs an alt attribute: the logo, a headshot, and social icons. Purely decorative images get an empty alt="" so a screen reader skips them. Many email clients block images by default, so alt text is also what a sighted recipient sees when the logo doesn't load.
Predictable reading order
Screen readers move through content in the order it appears in the HTML, not the order it looks on screen. A signature should read as name, title, company, contact details, then links. A layout that looks right can still read out of order if the underlying markup doesn't match.
Text that can be enlarged
Recipients who increase their zoom or font size shouldn't see text clipped or overlapping. Avoid fixed-height cells, and use relative sizing where the client supports it. Support for relative units such as rem is uneven in email, so check Can I email before relying on one.
Testing before it ships
Run the signature HTML through an automated checker such as WAVE or axe DevTools, which flag missing alt text and contrast failures. Then listen to it with a screen reader, for example the free NVDA on Windows or VoiceOver on a Mac. Automated tools can't tell you whether the signature reads in a sensible order, only a person listening can.
Where the Legal Pressure Comes From
It's worth being precise here, because accessibility law is often described more broadly than it applies.
The European Accessibility Act has applied since 28 June 2025 to a defined list of consumer products and services, including e-commerce, consumer banking, e-books, and electronic communications services. Microenterprises that provide services are exempt, and services aimed only at businesses fall outside the scope. The Act doesn't set rules for the format of an email signature as such.
What it does mean is that a company whose customer communication is part of a covered service has good reason to treat its email templates as part of the accessible experience. In the US, Section 508 sets accessibility requirements for federal agencies, which extend to their electronic communications. Whether a particular signature is covered depends on the service, the country, and the company's size, so legal counsel is the right place to confirm it for your case.
The practical argument is simpler than the legal one. An inaccessible signature excludes some of your own customers and colleagues, and fixing it costs little compared with finding out from a complaint.
Why Accessibility Can't Be Left to Each Employee
An accessible signature built once by a designer stays accessible until the next rebrand, the next title change, or the next new hire who copies an old template from someone's drafts. The same baseline has to apply to every version of the signature, internal and external, even when their content differs. None of the five requirements are hard individually. What breaks them is that nothing enforces them, so each new signature is another chance to reintroduce the same contrast or alt text problem that was already fixed once.
The reliable approach is to take the choice out of employees' hands. When one accessible template is applied centrally, through Microsoft 365 or Google Workspace, it is the only version anyone can send, and it stays accessible through a rebrand.
Accessibility Doesn't Stop at the Signature
The same people who read your emails also receive your business cards. A printed card is a fixed object, and a person with low vision may not be able to read its small type at all. A digital card is a web page, so the same WCAG criteria apply to it: contrast, labeled links, a logical reading order, and text that can be enlarged.
That's one reason gSignature is now DBC1. Managing signatures and business cards from one employee record gives you a single place to set how both look and read, so a fix made once, such as a darker color or a clearer link label, reaches the signature and the card together instead of being applied in one place and forgotten in the other.
Whether your signatures are already accessible or still need work, the aim is the same: signatures and cards that every recipient can read, kept that way as people and branding change. See how DBC1 brings them together.