G201 and links in emails #4620
Unanswered
cverges-medallia
asked this question in
Q&A
Replies: 2 comments 1 reply
-
|
Emails are arguably not "web content" as such. So the thinking behind G201 doesn't necessarily apply in this non-web context |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think email could be web content if viewed as an emended resource on a web page - just as PDFs can be web content. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Regarding “G201: Giving users advanced warning when opening a new window”, I’m trying to understand implications on email content design.
Email clients/readers will, by their nature, open links in a separate browser/window/tab. This behavior is determined more by the app’s settings than the email content itself. Placing text with each link warning to this app-specific behavior also seems repetitive and distracting. (Note that images and icons in emails and repetitive text become problematic for spam filters.)
So is it the responsibility of the email reader app to manage how to alert the user? Or does the content author sending the emails bear responsibility/the burden for guessing how a third party app will behave relative to their message?
Beta Was this translation helpful? Give feedback.
All reactions