On 18/10/07 (15:20) Chris said: >Well I guess now I really think about it you can't solve it as you could >append an email address to the DOM from an obfuscated javascript >function and that would likely solve the problem but it's not an >accessible solution. For screen readers you need to have the email >address in the HTML code and whether it's encoded or not it's accessible >to harvesters. Therefore theres no solution, so as Patrick said, "Fix >your spam issues at the mail server + mail client end"
Fair enough. One less item on the 'things to clarify' list; thanks everyone. (Of course, I rarely have control over the client's mail server, still less their email client. I suppose that becomes their problem). -- Rick Lecoat ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
