The comments and threads on Github just keep coming as well.
Then, this was published yesterday: AMP for email is a terrible idea.
There is a real opportunity here to get aligned and finally publish real specs on email standards via the W3C HTML for Email CG.
The solution from @Nicholas will keep the item a link but remove the affordance properties. This is not the goal in this particular context. This instance of the email address is specifically NOT to send an email to it, but to add it to contacts.
Don’t focus on style. Focus on format detection. It is a poor practice and experience to disable format detection using the meta tag. Instead, you can simply insert an HTML entity into the display name to prevent format detection and creation of the mailto link. Use a zero-width non-joiner: either or
Then, a good practice is to enhance this request with a link to a .VCF file for desktop email clients – to make it easier for users to create the contact.
Hello across the pond from MRM//McCann Detroit!
In addition to other great comments, consider this: most email is opened on a mobile device. All contact information (when properly formatted) will be detected by format detection (unless specifically disabled with a meta tag). Users expect this feature. Simply add a compelling reason / value proposition for the user to engage and create the contact.
I agree with the last suggestion. User control seems appropriate in this case. In addition to ambient light, the user has control over their brightness setting as well as their use of Night Shift. Interestingly, none of the factors of screen luminance or ambient light from environment are addressed in WCAG, but are more general considerations of accessibility.
I would love to see whatever you come up with.
Thinking outside for a moment, it is possible to create extensions for certain email clients. Perhaps their APIs extend to the UI view of the list / envelope / inbox. This would be an extremely limited audience, but theoretically possible.
To build upon what @Nicholas said, I assume the rest of the email also looks something like this. In which case, I emphatically agree there is opportunity to refactor some code, but also many other considerations – particularly accessibility.
This starts out strong with
on your parent
. But then nothing inside that table is accessible.
If you want to enhance your product, and your process, try posting an entire email and asking the community for a peer review. We can all improve at this when we all help each other.